LISTSERV mailing list manager LISTSERV 16.0

Help for ISOJAC Archives


ISOJAC Archives

ISOJAC Archives


[email protected]


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

ISOJAC Home

ISOJAC Home

ISOJAC  February 2001

ISOJAC February 2001

Subject:

Re: Document TC37/SC2/WG1 N69 - Language coding

From:

Håvard Hjulstad <[log in to unmask]>

Reply-To:

ISO 639 Joint Advisory Committee <[log in to unmask]>

Date:

Thu, 15 Feb 2001 14:20:44 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (111 lines)

Is ISO 639-2 a "code" or a "list of codes"?

You only need to go as far as to the title: "Codes for the representation of
names of languages - Part 1: Alpha-3 code". The last word says it all in my
book: 639-2 is ONE CODE. (The first plural is there because 639 as a set
consists of two such codes.)

Cf also 3166 (from ISO/TC46):
ISO 3166-1:1997 Codes for the representation of names of countries and their
subdivisions -- Part 1: Country codes
ISO 3166-2:1998 Codes for the representation of names of countries and their
subdivisions -- Part 2: Country subdivision code
ISO 3166-3:1999 Codes for the representation of names of countries and their
subdivisions -- Part 3: Code for formerly used names of countries

The whole series is plural: codes. Part 1 includes both a numerical code and
an alphabetical code (or actually two alphabetical codes). Parts 2 and 3 is
one code each.

ISO/TC37/SC2 has (throughout the process) received comments to the effect
that the terminology should be changed, and that it should be retained.
ISO/TC37/SC2 (who is responsible for ISO 639-1 (all text except the code
tables)) has considered all input and arguments. TC37/SC2 did find it
problematic that the terminology is different. TC37 has also seeked advice
from ISO CS in this matter, but has not received very clear answers.

I don't think that our end users will find this "problem" very big. They
will be mostly interesed in the code tables.

Best regards,
Håvard

-------------------------
Håvard Hjulstad    mailto:[log in to unmask]
  Rådet for teknisk terminologi (RTT)
  (Norwegian Council for Technical Terminology)
  Postboks 660 Skøyen
  NO-0214  Oslo, Norway
  tel: +47-22049225, dir: +47-22049259
  faks: +47-22434224
  http://www.rtt.org/
-------------------------

-----Original Message-----
From: ISO 639 Joint Advisory Committee [mailto:[log in to unmask]]On Behalf
Of Rebecca S. Guenther
Sent: 13. februar 2001 21:41
To: [log in to unmask]
Subject: Re: Document TC37/SC2/WG1 N69 - Language coding


I have a few comments on your document.

Ireland's comment about harmonizing the definitions of "code" between the
two parts. Convenor's response is:
"Terms and definitions in 639-2 should be harmonized with 639-1, which
build on ISO 639:1988.  ISO 639-1 will keep its current terminology."

In the various revisions of 639-2 during its development as a CD (twice),
then a DIS, etc. this issue came up. In fact there was much discussion
about it and some disagreement. This was mainly concerning whether to call
these elements we were standardizing as "codes", "code elements",
"identifiers", "symbols" or something else.  A decision was made at the
meeting of the TC46/SC4-TC37/SC2 Joint Working Group on Language Codes in
Berlin in May 1993 (I took the notes there). A compromise was reached that
the document itself would be called a "code list" and the individual
language codes "code elements". It was acknowledged that this decision may
have an impact on ISO 639-1 (this was explicitly stated). It was also
acknowledged that "code element" was difficult to translate and give
meaning to. It was later determined in the ISO meeting week that the term
"code" has been widely used and could be adopted for the individual
elements.

Further discussion and consensus was reached at the 1995 meeting of the
JWG in Ottawa where the definitions of "code" and "language code" were
finalized. As a result of this we used the term "language code" in 3.2. of
the standard and the definition was finalized. This is what was balloted and
approved. TC 37 representatives were at both JWG meetings where this was
worked out.

Rebecca

On Thu, 8 Feb 2001, [iso-8859-1] Håvard Hjulstad wrote:

> Dear colleagues,
>
> Please find enclosed document ISO/TC37/SC2/WG1 N69 as a Word document and
as
> an HTML document.
>
> The document is the first response to the request at the previous meeting
of
> TC37/SC2 to look into further projects relating to language coding.
COMMENTS
> ARE MOST WELCOME, as I will submit more concrete proposals later.
>
> Best regards,
> Håvard Hjulstad
>
> -------------------------
> Håvard Hjulstad    mailto:[log in to unmask]
>   Rådet for teknisk terminologi (RTT)
>   (Norwegian Council for Technical Terminology)
>   Postboks 660 Skøyen
>   NO-0214  Oslo, Norway
>   tel: +47-22049225, dir: +47-22049259
>   faks: +47-22434224
>   http://www.rtt.org/
> -------------------------
>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

April 2021
January 2021
November 2020
June 2020
May 2019
February 2019
September 2018
April 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
May 2016
April 2016
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
October 2013
September 2013
August 2013
July 2013
May 2013
April 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
September 2000
August 2000
July 2000
June 2000
May 2000
April 2000
March 2000
February 2000
January 2000

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager