Doug Ewell | 1 Jul 04:43
Favicon

Re: Anomaly in upcoming registry

Lang Gérard <gerard dot lang at insee dot fr> wrote:

> 11-ISO 639-5 (2008-05-15) includes the entry "sla", that an alpha-3 
> ISO 639-5 code element to represent the family language name "Slavic 
> languages (remainder group)", that is under the hierarchy of the 
> alpha-3 ISO 639-5 code element "ine" to represent the family language 
> name "Indo-European (remainder group)."

"Remainder group" is an ISO 639-5 term for an ISO 639-2 concept, viz. 
"Indo-European (Other)", and these were all effectively converted to 
full language groups on 2009-03-03 by changing the reference names. 
Check the change page at 
http://www.loc.gov/standards/iso639-2/php/code_changes.php .

ISO 639-5/RA should consider updating their information to match that 
maintained by ISO 639-2/RA, especially since it's the same RA.

--
Doug Ewell  *  Thornton, Colorado, USA  *  RFC 4645  *  UTN #14
http://www.ewellic.org
http://www1.ietf.org/html.charters/ltru-charter.html
http://www.alvestrand.no/mailman/listinfo/ietf-languages  ˆ 

_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Lang Gérard | 1 Jul 08:45
Picon
Favicon

RE: Anomaly in upcoming registry

Dear Doug,

Thank you very much for this complement.
 In fact, my initial description of ISO 639-5 collective language names was not completely accurate
because, stictly speaking, "(remainder group)" [or "(group)"] is not really included in the collective
name languages as defined inside ISO 639-5, it is an information linking ISO 639-5 with ISO 639-2 that is
given inside all ISO 639-5 tables, and that should be maintained when ISO 639-2 is modified regarding such
linking information
So that my text should be completed by the adjunction of a new point:

"12-On 2009-03-03, ISO 639/RA-JAC changed the language names concerning 42 alpha-3 collective language
ISO 639-2 code elements,  so that:
-"ine/ine" that was an initial code element of ISO 639-2 (1998) changed its collective language name from
"Indo-European (Others)/ indo-européennes, autres langues" to
"Indo-European, languages/ indo-européennes, langues";
-"sla/sla" that was an initial code element of ISO 639-2 (1998) changed its collective language name from
"Slavic (Other)/ slaves, autres langues" to "Slavic languages/ slaves, langues".

When ISO 639-2 changes modify informations having interest for the linking information column inside ISO
639-5, this column should be accordingly maintained."

Bien cordialement.
Gérard LANG  

-----Message d'origine-----
De : ietf-languages-bounces <at> alvestrand.no [mailto:ietf-languages-bounces <at> alvestrand.no] De la
part de Doug Ewell
Envoyé : mercredi 1 juillet 2009 04:43
À : ietf-languages <at> iana.org
Objet : Re: Anomaly in upcoming registry
(Continue reading)

Doug Ewell | 1 Jul 14:09
Favicon

Re: Anomaly in upcoming registry

Lang Gérard <gerard dot lang at insee dot fr> wrote:

> So that my text should be completed by the adjunction of a new point:
>
> "12-On 2009-03-03, ISO 639/RA-JAC changed the language names 
> concerning 42 alpha-3 collective language ISO 639-2 code elements,  so 
> that:
> -"ine/ine" that was an initial code element of ISO 639-2 (1998) 
> changed its collective language name from "Indo-European (Others)/ 
> indo-europennes, autres langues" to "Indo-European, languages/ 
> indo-europennes, langues";
> -"sla/sla" that was an initial code element of ISO 639-2 (1998) 
> changed its collective language name from "Slavic (Other)/ slaves, 
> autres langues" to "Slavic languages/ slaves, langues".

But I don't see what this has to do with whether "sh" and/or "hbs" 
should be withdrawn from any part of ISO 639, or deprecated in the 
Registry.

--
Doug Ewell  *  Thornton, Colorado, USA  *  RFC 4645  *  UTN #14
http://www.ewellic.org
http://www1.ietf.org/html.charters/ltru-charter.html
http://www.alvestrand.no/mailman/listinfo/ietf-languages  ˆ

_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
(Continue reading)

Rebecca S Guenther | 1 Jul 16:09
Picon

Re: Anomaly in upcoming registry

Yes, we do need to make the changes to the language names in 639-5. The
problem is that we have 2 different systems running and one is newer and
more experimental. We hope to do this soon.

Rebecca

Rebecca S. Guenther                                                    

 Senior Networking and Standards Specialist                  
 Network Development and MARC Standards Office     
 Library of Congress   
 101 Independence Ave. SE                                       
 Washington, DC 20540                                                  

 Washington, DC 20540-4402                                          
 (202) 707-5092 (voice)    (202) 707-0115 (FAX)           
 rgue <at> loc.gov

>>> "Doug Ewell" <doug <at> ewellic.org> 6/30/2009 10:43 PM >>>
Lang Gérard <gerard dot lang at insee dot fr> wrote:

> 11-ISO 639-5 (2008-05-15) includes the entry "sla", that an alpha-3 
> ISO 639-5 code element to represent the family language name "Slavic

> languages (remainder group)", that is under the hierarchy of the 
> alpha-3 ISO 639-5 code element "ine" to represent the family language

> name "Indo-European (remainder group)."

"Remainder group" is an ISO 639-5 term for an ISO 639-2 concept, viz. 
(Continue reading)

CE Whitehead | 2 Jul 01:13
Picon

Anomaly in upcoming registry

Gerard Lang's info. is good info. (I quote from his older posting here but I've seen both).

Gerard's info. does not make me turn one way or the other however--so I agree with Doug on this point.
 
I see that:
 
(1), if [sh] is 'un-retired' (or whatever) we have two macro-language codes for Serbian, Croatian, and Bosnian. 
 
(2), If it is not 'un-retired' we have one code and one deprecated code.
 
(Forgive me for making up the word 'un-retired.')
 
Indeed I do not see that it matters what we do here.  (Are we just doing this to do something in this case?)
 

--C. E. Whitehead
cewcathar <at> hotmail.com
 
Lang Gérard gerard.lang at insee.fr
Tue Jun 30 17:31:03 CEST 2009



> I completely agree with this position. In fact, the situation concerning sh and connex code elements inside ISO 639 is more than exceptional. > 1-ISO recommendation R 639 (November 1967) includes the code element "Sh" as symbol for the language (name) "Serbo-Croat/Serbo-croate", having indexes "861/862", that is part of the slavonic language family, inside the UDC (Universal Decimal Codification) and combination "Sh/YU/" with the country (name) symbol concerning Yugoslavia. > 2-ISO 639 standard (1988-04-01) includes, amonge of its 136 initial alpha-2 code elements, the alpha-2 code element "sh" for the representation of the language name "Srpskohrvatski/serbo-croate/Serbo-Croatian", as well as "hr" for the language name "Hrvatski/croate/Croatian" and "sr" for the language name "Srpski/serbe/Serbian".. There is no entry concerning the language name "Bosnian" > 3-ISO 639-2 (1998-10-22), whose introduction writes "The languages (names) listed in ISO 639-1are a subset of the languages (names) listed in this part of ISO 639; every language code (element) in the two letters code set has a corresponding language code (element) in the alpha-3 list, but not necessarily vice-versa.", includes an alpha-3 (binary) entry "scr/hrv" for the language name "Croatian/croate", and also another (binary) alpha-3 entry "scc/srp" for the language name "Serbian/serbe", but does not include any alpha-3 code element for an entry language name "Serbo-Croatian/serbo-croate", so that the promiss given inside ISO 639-2 introduction is not fulfilled concerning the ISO 639(-1) alpha-2 code element "sh" that has no alpha-3 ISO 639-2 counterpart. There is no entry concerning the language name "Bosnian". > 4-Between 1992 and 1993, four (Croatia, Slovenia, Bosnia-Herzegovina and Macedonia) of the six Republics that were formerly united inside the Socialist Federal Republic of Yugoslavia acquired independance, became Member States of the United Nations and received alpha-2 ISO 3166-1 code elements. > 5-On 2000-02-18, ISO 639/RA-JAC decided to deprecate the ISO 639(-1) alpha-2 code element "sh" "because there were separate language code (elements) for each language (name) represented (Serbian, Croatian and then Bosnian was added.). > 6-On the same day, ISO 639/RA-JAC decided the addition of a new alpha-2 code element "bo" inside ISO 639 and of a new alpha-3 code element "bos" inside ISO 639-2 to represent the language name "Bosnian/ bosniaque" (along with the addition of 24 others entries inside ISO 639-2 on the same day; but among them only "Sign languages" received only an alpha-3 ISO 639-2 code element "sgn" and no alpha-2 ISO 639-1 code element). > 7-Nevertheless, ISO 639-1 (2002-07-18) reintegrated the alpha-2 code element "sh" representing the language name "srpskohrvatski (jezik)/ serbo-croate/ Serbo-Croatian)" as an entry, along with the three others code elements "bs", "hr" and "sr" for representing respectively the three language names "bosanski (jezik)/ bosniaque/ Bosnian", "hrvatski jezik/ croate/ Croatian" and "srpski (jezik)/ serbe/ Serbian". > 8-On 2005-YY-XX, after this reintegration inside ISO 639-1, the language name "Serbo-Croat" was never included as a new entry inside ISO 639-2, and in 2005 (no more precise datation given) the ISO 639/RA-JAC decided to "reaffirm the deprecated status of "sh" inside ISO 639-1 > 9-ISO 639-3 (2007-02-05) includes the following entries "bos" (Bosnian), "hbs" (Serbo-Croatian, explicitely linked to "sh" [deprecated]), "hrv" (Croatian), "srp" (Serbian), as well as "mkd" (Macedonian, with also "mk" [and CDU index 866 inside the slavic language family]already inside ISO 639: 1988) and "slv" (Slovenian, with also CDU index 863 inside the slavic language family] already inside ISO 639: 1988; moreover, the language name "Slovenian" has the symbol "Sn" and the combination "Sn/YU" inside ISO R 639 (1967). > 10-On 2008-04-07, the Croatian National and University Library, the Croatian Standard Institute, the National Library of Serbia and the Institute for Standardization of Serbia jointly wrote a letter to the ISO 639-2 Registration Authority and to the ISO Central Secretary to explain that the alpha-3 ISO 6392/B code elements "scr" and "scc", that were abreviations for "Serbo-Croatian written in Roman alphabet" and "Serbo-Croatian written in cyrillic alphabet" should no more be used and that the corresponding alpha-3 ISO 639-2/T code elements "hrv" and "srp" should replace them to represent respectively the Serbian and Croatian language names inside ISO 639-2. On 2008-06-28, ISO 639/RA-JAC accepted this claim and decided to deprecate "scc" and "scr" respectively in favor of "hrv" and "srp". > 11-ISO 639-5 (2008-05-15) includes the entry "sla", that an alpha-3 ISO 639-5 code element to represent the family language name "Slavic languages (remainder group)", that is under the hierarchy of the alpha-3 ISO 639-5 code element "ine" to represent the family language name "Indo-European (remainder group)." Bien cordialement. Gérard LANG

_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Mark Davis ⌛ | 2 Jul 02:15

Re: Anomaly in upcoming registry


Mark


On Wed, Jul 1, 2009 at 16:13, CE Whitehead <cewcathar <at> hotmail.com> wrote:
Gerard Lang's info. is good info. (I quote from his older posting here but I've seen both).

Gerard's info. does not make me turn one way or the other however--so I agree with Doug on this point.
 
I see that:
 
(1), if [sh] is 'un-retired' (or whatever) we have two macro-language codes for Serbian, Croatian, and Bosnian. 

No, we won't. 'hbs' is valid and non-deprecated in 639-3, but it wasn't added to the registry because it has a two-letter equivalent, 'sh'. So the issue is whether to undeprecate 'sh' or not.


 
(2), If it is not 'un-retired' we have one code and one deprecated code.

Again, no.
 

 
(Forgive me for making up the word 'un-retired.')
 
Indeed I do not see that it matters what we do here.  (Are we just doing this to do something in this case?)
 

--C. E. Whitehead
cewcathar <at> hotmail.com
 
Lang Gérard gerard.lang at insee.fr
Tue Jun 30 17:31:03 CEST 2009



> I completely agree with this position. In fact, the situation concerning sh and connex code elements inside ISO 639 is more than exceptional. > 1-ISO recommendation R 639 (November 1967) includes the code element "Sh" as symbol for the language (name) "Serbo-Croat/Serbo-croate", having indexes "861/862", that is part of the slavonic language family, inside the UDC (Universal Decimal Codification) and combination "Sh/YU/" with the country (name) symbol concerning Yugoslavia. > 2-ISO 639 standard (1988-04-01) includes, amonge of its 136 initial alpha-2 code elements, the alpha-2 code element "sh" for the representation of the language name "Srpskohrvatski/serbo-croate/Serbo-Croatian", as well as "hr" for the language name "Hrvatski/croate/Croatian" and "sr" for the language name "Srpski/serbe/Serbian".. There is no entry concerning the language name "Bosnian" > 3-ISO 639-2 (1998-10-22), whose introduction writes "The languages (names) listed in ISO 639-1are a subset of the languages (names) listed in this part of ISO 639; every language code (element) in the two letters code set has a corresponding language code (element) in the alpha-3 list, but not necessarily vice-versa.", includes an alpha-3 (binary) entry "scr/hrv" for the language name "Croatian/croate", and also another (binary) alpha-3 entry "scc/srp" for the language name "Serbian/serbe", but does not include any alpha-3 code element for an entry language name "Serbo-Croatian/serbo-croate", so that the promiss given inside ISO 639-2 introduction is not fulfilled concerning the ISO 639(-1) alpha-2 code element "sh" that has no alpha-3 ISO 639-2 counterpart. There is no entry concerning the language name "Bosnian". > 4-Between 1992 and 1993, four (Croatia, Slovenia, Bosnia-Herzegovina and Macedonia) of the six Republics that were formerly united inside the Socialist Federal Republic of Yugoslavia acquired independance, became Member States of the United Nations and received alpha-2 ISO 3166-1 code elements. > 5-On 2000-02-18, ISO 639/RA-JAC decided to deprecate the ISO 639(-1) alpha-2 code element "sh" "because there were separate language code (elements) for each language (name) represented (Serbian, Croatian and then Bosnian was added.). > 6-On the same day, ISO 639/RA-JAC decided the addition of a new alpha-2 code element "bo" inside ISO 639 and of a new alpha-3 code element "bos" inside ISO 639-2 to represent the language name "Bosnian/ bosniaque" (along with the addition of 24 others entries inside ISO 639-2 on the same day; but among them only "Sign languages" received only an alpha-3 ISO 639-2 code element "sgn" and no alpha-2 ISO 639-1 code element). > 7-Nevertheless, ISO 639-1 (2002-07-18) reintegrated the alpha-2 code element "sh" representing the language name "srpskohrvatski (jezik)/ serbo-croate/ Serbo-Croatian)" as an entry, along with the three others code elements "bs", "hr" and "sr" for representing respectively the three language names "bosanski (jezik)/ bosniaque/ Bosnian", "hrvatski jezik/ croate/ Croatian" and "srpski (jezik)/ serbe/ Serbian". > 8-On 2005-YY-XX, after this reintegration inside ISO 639-1, the language name "Serbo-Croat" was never included as a new entry inside ISO 639-2, and in 2005 (no more precise datation given) the ISO 639/RA-JAC decided to "reaffirm the deprecated status of "sh" inside ISO 639-1 > 9-ISO 639-3 (2007-02-05) includes the following entries "bos" (Bosnian), "hbs" (Serbo-Croatian, explicitely linked to "sh" [deprecated]), "hrv" (Croatian), "srp" (Serbian), as well as "mkd" (Macedonian, with also "mk" [and CDU index 866 inside the slavic language family]already inside ISO 639: 1988) and "slv" (Slovenian, with also CDU index 863 inside the slavic language family] already inside ISO 639: 1988; moreover, the language name "Slovenian" has the symbol "Sn" and the combination "Sn/YU" inside ISO R 639 (1967). > 10-On 2008-04-07, the Croatian National and University Library, the Croatian Standard Institute, the National Library of Serbia and the Institute for Standardization of Serbia jointly wrote a letter to the ISO 639-2 Registration Authority and to the ISO Central Secretary to explain that the alpha-3 ISO 6392/B code elements "scr" and "scc", that were abreviations for "Serbo-Croatian written in Roman alphabet" and "Serbo-Croatian written in cyrillic alphabet" should no more be used and that the corresponding alpha-3 ISO 639-2/T code elements "hrv" and "srp" should replace them to represent respectively the Serbian and Croatian language names inside ISO 639-2. On 2008-06-28, ISO 639/RA-JAC accepted this claim and decided to deprecate "scc" and "scr" respectively in favor of "hrv" and "srp". > 11-ISO 639-5 (2008-05-15) includes the entry "sla", that an alpha-3 ISO 639-5 code element to represent the family language name "Slavic languages (remainder group)", that is under the hierarchy of the alpha-3 ISO 639-5 code element "ine" to represent the family language name "Indo-European (remainder group)." Bien cordialement. Gérard LANG


_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages


_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Doug Ewell | 4 Jul 20:55
Favicon

Proposed new records and reg forms for ISO 15924 changes

On June 1, a batch of 15 changes for ISO 15924 ("Codes for the 
representation of names of scripts") was approved by the RA.  Most of 
these changes deal only with adding Property Value Alias values to 
existing script code elements.  These values are used by Unicode and are 
not relevant to the Language Subtag Registry.

Two new code elements were added for the scripts Bamum ("Bamu") and Old 
South Arabian ("Sarb").  Additionally, the code element "Orkh" had its 
English Name field changed from "Orkhon" to "Old Turkic, Orkhon Runic." 
These changes do need to be reflected in the Registry.

Below are the proposed new records and registration forms for these 
three changes.  After a two-week review period, they will be submitted 
to IANA.  Please note that RFC 4646, Section 3.3 requires changes to be 
made to the Registry to reflect relevant changes to the core standards. 
One could conceivably argue that we should keep the existing Description 
field "Orkhon" as well as adding the new names, but other than that, 
there should be little debate.

For more information on the ISO 15924 changes, see:

http://www.unicode.org/iso15924/codechanges.html
http://www.unicode.org/iso15924/iso15924-text.html

===

LANGUAGE SUBTAG MODIFICATION
File-Date: 2009-07-04
%%
Type: script
Subtag: Bamu
Description: Bamum
Added: 2009-07-18
%%

===

LANGUAGE SUBTAG REGISTRATION FORM

1. Name of requester: Doug Ewell
2. E-mail address of requester: doug at ewellic.org
3. Record Requested:

   Type: script
   Subtag: Bamu
   Description: Bamum
   Comments:

4. Intended meaning of the subtag:

5. Reference to published description
   of the language (book or article):

6. Any other relevant information:

   This registration tracks an addition made to ISO 15924 effective
   2009-06-01.

===

LANGUAGE SUBTAG MODIFICATION
File-Date: 2009-07-04
%%
Type: script
Subtag: Orkh
Description: Old Turkic
Description: Orkhon Runic
Added: 2009-07-18
%%

===

LANGUAGE SUBTAG REGISTRATION FORM

1. Name of requester: Doug Ewell
2. E-mail address of requester: doug at ewellic.org
3. Record Requested:

   Type: script
   Subtag: Orkh
   Description: Old Turkic
   Description: Orkhon Runic
   Comments:

4. Intended meaning of the subtag:

5. Reference to published description
   of the language (book or article):

6. Any other relevant information:

   This registration tracks a change made to ISO 15924 effective
   2009-06-01, changing the English name of this script from
   "Orkhon".

===

LANGUAGE SUBTAG MODIFICATION
File-Date: 2009-07-04
%%
Type: script
Subtag: Sarb
Description: Old South Arabian
Added: 2009-07-18
%%

===

LANGUAGE SUBTAG REGISTRATION FORM

1. Name of requester: Doug Ewell
2. E-mail address of requester: doug at ewellic.org
3. Record Requested:

   Type: script
   Subtag: Sarb
   Description: Old South Arabian
   Comments:

4. Intended meaning of the subtag:

5. Reference to published description
   of the language (book or article):

6. Any other relevant information:

   This registration tracks an addition made to ISO 15924 effective
   2009-06-01.

--
Doug Ewell  *  Thornton, Colorado, USA  *  RFC 4645  *  UTN #14
http://www.ewellic.org
http://www1.ietf.org/html.charters/ltru-charter.html
http://www.alvestrand.no/mailman/listinfo/ietf-languages  ˆ

_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Mark Davis ⌛ | 4 Jul 21:07

Re: Proposed new records and reg forms for ISO 15924 changes

I suggest that we hold off on these until the new, revised iana registry is in place. There is no immediate need for them, and it complicates the process.

Mark


On Sat, Jul 4, 2009 at 11:55, Doug Ewell <doug <at> ewellic.org> wrote:
On June 1, a batch of 15 changes for ISO 15924 ("Codes for the
representation of names of scripts") was approved by the RA.  Most of
these changes deal only with adding Property Value Alias values to
existing script code elements.  These values are used by Unicode and are
not relevant to the Language Subtag Registry.

Two new code elements were added for the scripts Bamum ("Bamu") and Old
South Arabian ("Sarb").  Additionally, the code element "Orkh" had its
English Name field changed from "Orkhon" to "Old Turkic, Orkhon Runic."
These changes do need to be reflected in the Registry.

Below are the proposed new records and registration forms for these
three changes.  After a two-week review period, they will be submitted
to IANA.  Please note that RFC 4646, Section 3.3 requires changes to be
made to the Registry to reflect relevant changes to the core standards.
One could conceivably argue that we should keep the existing Description
field "Orkhon" as well as adding the new names, but other than that,
there should be little debate.

For more information on the ISO 15924 changes, see:

http://www.unicode.org/iso15924/codechanges.html
http://www.unicode.org/iso15924/iso15924-text.html


===

LANGUAGE SUBTAG MODIFICATION
File-Date: 2009-07-04
%%
Type: script
Subtag: Bamu
Description: Bamum
Added: 2009-07-18
%%

===

LANGUAGE SUBTAG REGISTRATION FORM

1. Name of requester: Doug Ewell
2. E-mail address of requester: doug at ewellic.org
3. Record Requested:

  Type: script
  Subtag: Bamu
  Description: Bamum
  Comments:

4. Intended meaning of the subtag:

5. Reference to published description
  of the language (book or article):

6. Any other relevant information:

  This registration tracks an addition made to ISO 15924 effective
  2009-06-01.

===

LANGUAGE SUBTAG MODIFICATION
File-Date: 2009-07-04
%%
Type: script
Subtag: Orkh
Description: Old Turkic
Description: Orkhon Runic
Added: 2009-07-18
%%

===

LANGUAGE SUBTAG REGISTRATION FORM

1. Name of requester: Doug Ewell
2. E-mail address of requester: doug at ewellic.org
3. Record Requested:

  Type: script
  Subtag: Orkh
  Description: Old Turkic
  Description: Orkhon Runic
  Comments:

4. Intended meaning of the subtag:

5. Reference to published description
  of the language (book or article):

6. Any other relevant information:

  This registration tracks a change made to ISO 15924 effective
  2009-06-01, changing the English name of this script from
  "Orkhon".

===

LANGUAGE SUBTAG MODIFICATION
File-Date: 2009-07-04
%%
Type: script
Subtag: Sarb
Description: Old South Arabian
Added: 2009-07-18
%%

===

LANGUAGE SUBTAG REGISTRATION FORM

1. Name of requester: Doug Ewell
2. E-mail address of requester: doug at ewellic.org
3. Record Requested:

  Type: script
  Subtag: Sarb
  Description: Old South Arabian
  Comments:

4. Intended meaning of the subtag:

5. Reference to published description
  of the language (book or article):

6. Any other relevant information:

  This registration tracks an addition made to ISO 15924 effective
  2009-06-01.


--
Doug Ewell  *  Thornton, Colorado, USA  *  RFC 4645  *  UTN #14
http://www.ewellic.org
http://www1.ietf.org/html.charters/ltru-charter.html
http://www.alvestrand.no/mailman/listinfo/ietf-languages  ˆ

_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages

_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
John Cowan | 4 Jul 21:08

Re: Proposed new records and reg forms for ISO 15924 changes

Doug Ewell scripsit:

> Below are the proposed new records and registration forms for these 
> three changes.  After a two-week review period, they will be submitted 
> to IANA.  

Presumably this will have to be redone after IANA refreshes the registry
from 4645bis (which has been approved, although not yet published).
Should we sit on it for a while?

--

-- 
John Cowan  cowan <at> ccil.org  http://ccil.org/~cowan
If I have seen farther than others, it is because I was standing on
the shoulders of giants.
        --Isaac Newton
Michael Everson | 4 Jul 21:21
Favicon
Gravatar

Re: Proposed new records and reg forms for ISO 15924 changes

On 4 Jul 2009, at 20:07, Mark Davis ⌛ wrote:

> I suggest that we hold off on these until the new, revised iana  
> registry is in place. There is no immediate need for them, and it  
> complicates the process.

I don't believe in vapourware. I think that if the new registry is not  
in place before a fortnight, then we should proceed as normal and add  
these registrations.

Michael Everson * http://www.evertype.com/

_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages

Gmane