headers
Doug Ewell | 1 Feb 01:00
Favicon

Re: ISO 639-3 changes, part ? (Was ISO 639-3 changes, part 1)

CE Whitehead wrote:

> For your first registration record, Doug wrote:
>
>    "This registration tracks a change made to ISO 639-3 effective
>    2010-01-20, adding the code element 'shd' for Kundal Shahi."
>
> whereas I should write:
> =>  ??
>
>    "This registration tracks a change made to ISO 639-3 effective
>    2010-01-20, retiring{/deprecating} the code element 'drh' for 
> Darkhat {in favor of 'khk'}."
>
> Correct?  (The informattion in brackets is for an alternative version, 
> if you prefer that; otherwise I will omit it and use the word 
> 'retiring'.)

The exact wording for point 6 is not critical.  The important part is to 
say that we are tracking a change in the ISO standard, as opposed to 
doing something on our own like creating a new variant.  It's probably 
not necessary to include the information about 'khk' since that is 
apparent from the data.

> Also I assume I need "Added," "Deprecated, and "Preferred-value" 
> fields in the registration form as these are relevant.
> (And maybe a "Comments" field (as for 'heploc')?? Or no maybe not?)

Do not insert an Added field in the registration form.  It is not called 
for in Figure 5 of RFC 5646, which is found within Section 3.5.  You do
(Continue reading)

Permalink | Reply | 0 comments |
headers
Phillips, Addison | 1 Feb 05:52
Picon
Favicon

RE: ISO 639-3 changes, part 1

There is no rule otherwise. Any individual change has its own minimum timeline. The only reason to batch
them for IANA would be to reduce churn.

Addison Phillips
Globalization Architect -- Lab126

Internationalization is not a feature.
It is an architecture.

> -----Original Message-----
> From: ietf-languages-bounces <at> alvestrand.no [mailto:ietf-languages-
> bounces <at> alvestrand.no] On Behalf Of John Cowan
> Sent: Friday, January 29, 2010 11:13 PM
> To: Doug Ewell
> Cc: ietf-languages <at> iana.org
> Subject: Re: ISO 639-3 changes, part 1
> 
> Doug Ewell scripsit:
> 
> > The date 2010-03-01 in these records is an approximation, based
> on how
> > long it might take to get through these and 70+ other changes.
> 
> Why can't these be sent to IANA by themselves as soon as the errors
> are
> corrected and the time has expired?  I see no reason why all the
> changes
> should be collected together before IANA gets any of them -- a
> pipeline
> process seems more sensible to me.
(Continue reading)

Permalink | Reply | 0 comments |
headers
CE Whitehead | 1 Feb 17:51
Picon

ISO 639-3 changes, part ? (Was ISO 639-3 changes, part 1)

Hi.

Doug Ewell doug at ewellic.org
Mon Feb 1 01:00:30 CET 2010

> Do not insert an Added field in the registration form.  It is not called
> for in Figure 5 of RFC 5646, which is found within Section 3.5.

Oops.  (I went too many places looking for examples and still did not get that somehow.
I had a ton of sleep last night so should not make more mistakes today hopefully.)
> You do need to have this field in the proposed record, though.
Yes, I see that.
> For subtags whose code elements are being retired from ISO 639-3, you
> need a Deprecated field.  You will also need a Preferred-Value field
> (note capitalization), but only if there is *exactly one* subtag that is
> preferred. . . .
This is know. 

> btb' is different; any one of seven other subtags might be the
> correct choice.  A subtag cannot have more than one Preferred-Value, and
> cannot have a so-called "multi-part" Preferred-Value; this is an
> iron-clad rule.  In this case, the information would have to be
> expressed as a Comments field, such as:
> Comments: see beb, bum, bxp, eto, ewo, fan, mct
Thanks for refreshing me on this. (The case of Serbo-Croatian 'sh' now comes back.)
> . . .
> But please hold off on Lushootseed for the moment.
I thought I was supposed to do all the first group of retired changes (I've already done 'lut', 'lushootseed', 
but have put in inside of  brackets for now; let me know when you want it).

> For changes like these that track the core standards, whoever translates the ISO data
> into BCP 47-compatible formats is the "author."  In this case, that's
> you.
(O.k. thought I was doing minor clerical work here, following your directives.
And anyway, I am finally getting shy, now that I got to do all this, but o.k.)

> Do not add Comments fields that simply duplicate the information in the
> Preferred-Value field.
That was sort of what I suspected; sorry.
(It would have been almost easier for you to just copy and paste these than to train me would not it have?)
Best,
C. E. Whitehead
cewcathar <at> hotmail.com

_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Permalink | Reply | 1 comment |
headers
CE Whitehead | 1 Feb 18:17
Picon

ISO 639-3 changes, part 2 ?



Hi, I hope these records will all be o.k.  (As far as I know I am not going to be online this afternoon from 3 till after 9
because of another commitment.  But I'll be on after 9 and/or tomorrow; I'd be on a tiny bit more if I trusted wireless . . . )
(Let me know when you all are ready for 'Lushootseed'--4th from bottom--and I will send these again without the brackets around that registration entry; not sure why Doug wanted me to hold off; I'll also put the right part # in the subject heading--maybe these are part 2???)
-----
LANGUAGE SUBTAG MODIFICATION
File-Date: 2010-03-01
%%
Type: language
Subtag: drh
Description: Darkhat
Added: 2009-07-29
Deprecated: 2010-03-01
Preferred-Value: khk
%%
---
 
LANGUAGE SUBTAG REGISTRATION FORM
1. Name of requester: C. E. Whitehead
2. E-mail address of requester: cewcathar at hotmail.com
3. Record Requested:
   Type: language
   Subtag: drh
   Description: Darkhat
   Preferred-Value: khk
   Deprecated: 2010-03-01
   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 639-3 effective
   2010-01-20, retiring the code element, 'drh', for Darkhat.
   For more information on the ISO 639-3 change, refer to
   http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2009_Summary.pdf

-----
LANGUAGE SUBTAG MODIFICATION
File-Date: 2010-03-01
%%
Type: language
Subtag: tnf
Description: Tangshewi
Added: 2009-07-29
Deprecated: 2010-03-01
Preferred-Value: prs
%%
---
 
LANGUAGE SUBTAG REGISTRATION FORM
1. Name of requester: C. E. Whitehead
2. E-mail address of requester: cewcathar at hotmail.com
3. Record Requested:
   Type: language
   Subtag: tnf
   Description: Tangshewi
   Preferred-Value: prs
   Deprecated: 2010-03-01
   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 639-3 effective
   2010-01-20, retiring the code element, 'tnf', for Tangshewi.
   For more information on the ISO 639-3 change, refer to
   http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2009_Summary.pdf

-----
LANGUAGE SUBTAG MODIFICATION
File-Date: 2010-03-01
%%
Type: language
Subtag: drw
Description: Darwazi
Added: 2009-07-29
Deprecated: 2010-03-01
Preferred-Value: prs
%%
---
 
LANGUAGE SUBTAG REGISTRATION FORM
1. Name of requester: C. E. Whitehead
2. E-mail address of requester: cewcathar at hotmail.com
3. Record Requested:
   Type: language
   Subtag: drw
   Description: Darwazi
   Preferred-Value: prs
   Deprecated: 2010-03-01
   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 639-3 effective
   2010-01-20, retiring the code element, 'drw', for Darwazi.
   For more information on the ISO 639-3 change, refer to
   http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2009_Summary.pdf

-----
LANGUAGE SUBTAG MODIFICATION
File-Date: 2010-03-01
%%
Type: language
Subtag: btb
Description: Beti
Added: 2009-07-29
Deprecated: 2010-03-01
Preferred-Value:
Comments: see beb, bum, bxp, eto, ewo, fan, mct
%%
---
 
LANGUAGE SUBTAG REGISTRATION FORM
1. Name of requester: C. E. Whitehead
2. E-mail address of requester: cewcathar at hotmail.com
3. Record Requested:
   Type: language
   Subtag: btb
   Description: Beti
   Preferred-Value:
   Deprecated: 2010-03-01
   Comments: see beb, bum, bxp, eto, ewo, fan, mct
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 639-3 effective
   2010-01-20, retiring the code element, 'btb', for Beti.
   For more information on the ISO 639-3 change, refer to
   http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2009_Summary.pdf

-----
LANGUAGE SUBTAG MODIFICATION
File-Date: 2010-03-01
%%
Type: language
Subtag: cmk
Description: Chimakum
Added: 2009-07-29
Deprecated: 2010-03-01
Preferred-Value: xch
%%
---

LANGUAGE SUBTAG REGISTRATION FORM
1. Name of requester: C. E. Whitehead
2. E-mail address of requester: cewcathar at hotmail.com
3. Record Requested:
   Type: language
   Subtag: cmk
   Description: Chimakum
   Preferred-Value: xch
   Deprecated: 2010-03-01
   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 639-3 effective
   2010-01-20, retiring the code element, 'cmk', for Chimakum.
   For more information on the ISO 639-3 change, refer to
   http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2009_Summary.pdf 

-----
LANGUAGE SUBTAG MODIFICATION
File-Date: 2010-03-01
%%
Type: language
Subtag: cjr
Description: Chorotega
Added: 2009-07-29
Deprecated: 2010-03-01
Preferred-Value: mom
%%
---

LANGUAGE SUBTAG REGISTRATION FORM
1. Name of requester: C. E. Whitehead
2. E-mail address of requester: cewcathar at hotmail.com
3. Record Requested:
   Type: language
   Subtag: cjr
   Description: Chorotega
   Preferred-Value: mom
   Deprecated: 2010-03-01
   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 639-3 effective
   2010-01-20, retiring the code element, 'cjr', for Chorotega.
   For more information on the ISO 639-3 change, refer to
   http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2009_Summary.pdf

{ Below is the subtag you asked me to wait before doing; it's here
but if there's a glitch . . . I'll send this again when it's fixed } 
{ -----
LANGUAGE SUBTAG MODIFICATION
File-Date: 2010-03-01
%%
Type: language
Subtag: lut
Description: Lushootseed
Added: 2009-07-29
Deprecated: 2010-03-01
Preferred-Value:
Comments:  see ska, slh, sno

%%
---

LANGUAGE SUBTAG REGISTRATION FORM
1. Name of requester: C. E. Whitehead
2. E-mail address of requester: cewcathar at hotmail.com
3. Record Requested:
   Type: language
   Subtag: lut
   Description: Lushootseed
   Preferred-Value:
   Deprecated: 2010-03-01
   Comments:  see ska, slh, sno

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 639-3 effective
   2010-01-20, retiring the code element, 'lut', for Lushootseed.
   For more information on the ISO 639-3 change, refer to
   http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2009_Summary.pdf
}
-----
LANGUAGE SUBTAG MODIFICATION
File-Date: 2010-03-01
%%
Type: language
Subtag: gav
Description: Gabutamon
Added: 2009-07-29
Deprecated: 2010-03-01
Preferred-Value: dev

%%
---

LANGUAGE SUBTAG REGISTRATION FORM
1. Name of requester: C. E. Whitehead
2. E-mail address of requester: cewcathar at hotmail.com
3. Record Requested:
   Type: language
   Subtag: gav
   Description: Gabutamon
   Preferred-Value: dev
   Deprecated: 2010-03-01

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 639-3 effective
   2010-01-20, retiring the code element, 'gav', for Gabutamon.
   For more information on the ISO 639-3 change, refer to
   http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2009_Summary.pdf

-----
LANGUAGE SUBTAG MODIFICATION
File-Date: 2010-03-01
%%
Type: language
Subtag: mst
Description: Cataelano Mandaya
Added: 2009-07-29
Deprecated: 2010-03-01
Preferred-Value: mry

%%
---

LANGUAGE SUBTAG REGISTRATION FORM
1. Name of requester: C. E. Whitehead
2. E-mail address of requester: cewcathar at hotmail.com
3. Record Requested:
   Type: language
   Subtag: mst
   Description: Cataelano Mandaya
   Preferred-Value: mry
   Deprecated: 2010-03-01

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 639-3 effective
   2010-01-20, retiring the code element, 'mst', for Cataelano Mandaya.
   For more information on the ISO 639-3 change, refer to
   http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2009_Summary.pdf

-----
LANGUAGE SUBTAG MODIFICATION
File-Date: 2010-03-01
%%
Type: language
Subtag: mrt
Description: Sangab Mandaya
Added: 2009-07-29
Deprecated: 2010-03-01
Preferred-Value: mry

%%
---

LANGUAGE SUBTAG REGISTRATION FORM
1. Name of requester: C. E. Whitehead
2. E-mail address of requester: cewcathar at hotmail.com
3. Record Requested:
   Type: language
   Subtag: mrt
   Description: Sangab Mandaya
   Preferred-Value: mry
   Deprecated: 2010-03-01

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 639-3 effective
   2010-01-20, retiring the code element, 'mrt', for Sangab Mandaya.
   For more information on the ISO 639-3 change, refer to
   http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2009_Summary.pdf
 
--
C. E. Whitehead
cewcathar <at> hotmail.com
* * *
 

 

_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Permalink | Reply | 4 comments |
headers
Kent Karlsson | 1 Feb 19:52
Picon

Re: ISO 639-3 changes, part 2

See comments below.

    /kent k

Den 2010-02-01 18.17, skrev "CE Whitehead" <cewcathar <at> hotmail.com>:

> Re: ISO 639-3 changes, part 2 ?

(I don't like your over-use of question marks... It's bad style even for an
email.)

> 
> 
> Hi, I hope these records will all be o.k.  (As far as I know I am not going to
> be online this afternoon from 3 till after 9
> because of another commitment.  But I'll be on after 9 and/or tomorrow; I'd be
> on a tiny bit more if I trusted wireless . . . )
> (Let me know when you all are ready for 'Lushootseed'--4th from bottom--and I
> will send these again without the brackets around that registration entry; not
> sure why Doug wanted me to hold off; I'll also put the right part # in the
> subject heading--maybe these are part 2???)

(I don't like your over-use of question marks... It's bad style even for an
email.)

> -----
> LANGUAGE SUBTAG MODIFICATION
> File-Date: 2010-03-01
> %%
> Type: language
> Subtag: drh
> Description: Darkhat
> Added: 2009-07-29
> Deprecated: 2010-03-01
> Preferred-Value: khk
> %%
> ---
>  
> LANGUAGE SUBTAG REGISTRATION FORM
> 1. Name of requester: C. E. Whitehead
> 2. E-mail address of requester: cewcathar at hotmail.com
> 3. Record Requested:
>    Type: language
>    Subtag: drh
>    Description: Darkhat
>    Preferred-Value: khk
>    Deprecated: 2010-03-01

Please give the fields (lines) in the same order; just be be consistent.
Pick the order of fields used in the registry. It does not formally matter,
but it makes it easier to proof-read.

>    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 639-3 effective
>    2010-01-20, retiring the code element, 'drh', for Darkhat.

I think the information that "Merge[d] with Halh Mongolian [khk]"
(from the RA's "change request summary") should be picked up here.

>    For more information on the ISO 639-3 change, refer to
>    http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2009_Summary.pdf
> 
> -----
> LANGUAGE SUBTAG MODIFICATION
> File-Date: 2010-03-01
> %%
> Type: language
> Subtag: tnf
> Description: Tangshewi
> Added: 2009-07-29
> Deprecated: 2010-03-01
> Preferred-Value: prs
> %%
> ---
>  
> LANGUAGE SUBTAG REGISTRATION FORM
> 1. Name of requester: C. E. Whitehead
> 2. E-mail address of requester: cewcathar at hotmail.com
> 3. Record Requested:
>    Type: language
>    Subtag: tnf
>    Description: Tangshewi
>    Preferred-Value: prs
>    Deprecated: 2010-03-01
>    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 639-3 effective
>    2010-01-20, retiring the code element, 'tnf', for Tangshewi.

As above, say something about the merge here. ("merge[d] with [prs]
Dari"...)

>    For more information on the ISO 639-3 change, refer to
>    http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2009_Summary.pdf
> 
> -----
> LANGUAGE SUBTAG MODIFICATION
> File-Date: 2010-03-01
> %%
> Type: language
> Subtag: drw
> Description: Darwazi
> Added: 2009-07-29
> Deprecated: 2010-03-01
> Preferred-Value: prs
> %%
> ---
>  
> LANGUAGE SUBTAG REGISTRATION FORM
> 1. Name of requester: C. E. Whitehead
> 2. E-mail address of requester: cewcathar at hotmail.com
> 3. Record Requested:
>    Type: language
>    Subtag: drw
>    Description: Darwazi
>    Preferred-Value: prs
>    Deprecated: 2010-03-01
>    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 639-3 effective
>    2010-01-20, retiring the code element, 'drw', for Darwazi.

As above, say something about the merge here. ("merge[d] with [prs]
Dari"...)

>    For more information on the ISO 639-3 change, refer to
>    http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2009_Summary.pdf
> 
> -----
> LANGUAGE SUBTAG MODIFICATION
> File-Date: 2010-03-01
> %%
> Type: language
> Subtag: btb
> Description: Beti

This is for "Beti (Cameroon)", not to be confused with "Beti (Côte
d'Ivoire)".

> Added: 2009-07-29
> Deprecated: 2010-03-01

I'm not so sure this one should be plainly "deprecated". Since "btb",
Beti (Cameroon) [languages], has been determined to be a "group"/collection,
"btb" should be regarded as a "collective code". Here I find it troublesome
that 639-5 registrations are handled by a different RA, which in addition
seems unresponsive to changes of this kind.

> Preferred-Value: 

There should be no preferred-value line here. This, and the comments above,
applies also to the "registration form" just below.

> Comments: see beb, bum, bxp, eto, ewo, fan, mct
> %%
> ---
>  
> LANGUAGE SUBTAG REGISTRATION FORM
> 1. Name of requester: C. E. Whitehead
> 2. E-mail address of requester: cewcathar at hotmail.com
> 3. Record Requested:
>    Type: language
>    Subtag: btb
>    Description: Beti
>    Preferred-Value:
>    Deprecated: 2010-03-01
>    Comments: see beb, bum, bxp, eto, ewo, fan, mct
> 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 639-3 effective
>    2010-01-20, retiring the code element, 'btb', for Beti.
>    For more information on the ISO 639-3 change, refer to
>    http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2009_Summary.pdf
> 
> -----
> LANGUAGE SUBTAG MODIFICATION
> File-Date: 2010-03-01
> %%
> Type: language
> Subtag: cmk
> Description: Chimakum
> Added: 2009-07-29
> Deprecated: 2010-03-01
> Preferred-Value: xch
> %%
> ---
> 
> LANGUAGE SUBTAG REGISTRATION FORM
> 1. Name of requester: C. E. Whitehead
> 2. E-mail address of requester: cewcathar at hotmail.com
> 3. Record Requested:
>    Type: language
>    Subtag: cmk
>    Description: Chimakum
>    Preferred-Value: xch
>    Deprecated: 2010-03-01
>    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 639-3 effective
>    2010-01-20, retiring the code element, 'cmk', for Chimakum.

The following should be picked up from the "change request summary":
"Duplicate of [xch]"; or better formulated "This code is a duplicate for
[xch], Chemakum". (Personally, I think they should have picked the other
code to deprecate, but oh well...)

>    For more information on the ISO 639-3 change, refer to
>    http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2009_Summary.pdf
> 
> -----
> LANGUAGE SUBTAG MODIFICATION
> File-Date: 2010-03-01
> %%
> Type: language
> Subtag: cjr
> Description: Chorotega
> Added: 2009-07-29
> Deprecated: 2010-03-01
> Preferred-Value: mom
> %%
> ---
> 
> LANGUAGE SUBTAG REGISTRATION FORM
> 1. Name of requester: C. E. Whitehead
> 2. E-mail address of requester: cewcathar at hotmail.com
> 3. Record Requested:
>    Type: language
>    Subtag: cjr
>    Description: Chorotega
>    Preferred-Value: mom
>    Deprecated: 2010-03-01
>    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 639-3 effective
>    2010-01-20, retiring the code element, 'cjr', for Chorotega.

Again, some reformulation (for better flow) of "Merge[d] with [mom]"
(Monimbo) should be included here.

>    For more information on the ISO 639-3 change, refer to
>    http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2009_Summary.pdf
> 
> { Below is the subtag you asked me to wait before doing; it's here
> but if there's a glitch . . . I'll send this again when it's fixed }
> { -----

I don't like your over-use of parentheticals in your emails...

> LANGUAGE SUBTAG MODIFICATION
> File-Date: 2010-03-01
> %%
> Type: language
> Subtag: lut
> Description: Lushootseed
> Added: 2009-07-29
> Deprecated: 2010-03-01

Again, I'm not so sure this one should be plainly "deprecated". Since "lut",
Lushootseed, has been determined to be a "group"/collection, "lut" should
be regarded as a "collective code".

> Preferred-Value: 

There should be no preferred-value line here. This, and the comments above,
applies also to the "registration form" just below.

> Comments:  see ska, slh, sno
> 
> %%
> ---
> 
> LANGUAGE SUBTAG REGISTRATION FORM
> 1. Name of requester: C. E. Whitehead
> 2. E-mail address of requester: cewcathar at hotmail.com
> 3. Record Requested:
>    Type: language
>    Subtag: lut
>    Description: Lushootseed
>    Preferred-Value:
>    Deprecated: 2010-03-01
>    Comments:  see ska, slh, sno
> 
> 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 639-3 effective
>    2010-01-20, retiring the code element, 'lut', for Lushootseed.
>    For more information on the ISO 639-3 change, refer to
>    http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2009_Summary.pdf
> }
> -----
> LANGUAGE SUBTAG MODIFICATION
> File-Date: 2010-03-01
> %%
> Type: language
> Subtag: gav
> Description: Gabutamon
> Added: 2009-07-29
> Deprecated: 2010-03-01
> Preferred-Value: dev
> 
> %%
> ---
> 
> LANGUAGE SUBTAG REGISTRATION FORM
> 1. Name of requester: C. E. Whitehead
> 2. E-mail address of requester: cewcathar at hotmail.com
> 3. Record Requested:
>    Type: language
>    Subtag: gav
>    Description: Gabutamon
>    Preferred-Value: dev
>    Deprecated: 2010-03-01
> 
> 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 639-3 effective
>    2010-01-20, retiring the code element, 'gav', for Gabutamon.

Include the info "Merge[d] into/with [dev] Domung". (But use a common
phrasing for all of the merges.)

>    For more information on the ISO 639-3 change, refer to
>    http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2009_Summary.pdf
> 
> -----
> LANGUAGE SUBTAG MODIFICATION
> File-Date: 2010-03-01
> %%
> Type: language
> Subtag: mst
> Description: Cataelano Mandaya
> Added: 2009-07-29
> Deprecated: 2010-03-01
> Preferred-Value: mry
> 
> %%
> ---
> 
> LANGUAGE SUBTAG REGISTRATION FORM
> 1. Name of requester: C. E. Whitehead
> 2. E-mail address of requester: cewcathar at hotmail.com
> 3. Record Requested:
>    Type: language
>    Subtag: mst
>    Description: Cataelano Mandaya
>    Preferred-Value: mry
>    Deprecated: 2010-03-01
> 
> 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 639-3 effective
>    2010-01-20, retiring the code element, 'mst', for Cataelano Mandaya.

Include the info "merged with Mandaya [mry]" here.

>    For more information on the ISO 639-3 change, refer to
>    http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2009_Summary.pdf
> 
> -----
> LANGUAGE SUBTAG MODIFICATION
> File-Date: 2010-03-01
> %%
> Type: language
> Subtag: mrt

-> 'myt'. 'mrt' is for "Marghi Central", ("Central Marghi"...)

> Description: Sangab Mandaya
> Added: 2009-07-29
> Deprecated: 2010-03-01
> Preferred-Value: mry
> 
> %%
> ---
> 
> LANGUAGE SUBTAG REGISTRATION FORM
> 1. Name of requester: C. E. Whitehead
> 2. E-mail address of requester: cewcathar at hotmail.com
> 3. Record Requested:
>    Type: language
>    Subtag: mrt

-> 'myt'. 'mrt' is for "Marghi Central", or rather "Central Marghi"; somehow
"Marghi Central" and "Marghi South" did not get their names uninverted.

>    Description: Sangab Mandaya
>    Preferred-Value: mry
>    Deprecated: 2010-03-01
> 
> 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 639-3 effective
>    2010-01-20, retiring the code element, 'mrt', for Sangab Mandaya.

Include the info "merged with Mandaya [mry]" here.

>    For more information on the ISO 639-3 change, refer to
>    http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2009_Summary.pdf
>  
> --
> C. E. Whitehead
> cewcathar <at> hotmail.com
> * * *
Permalink | Reply | 3 comments |
headers
Doug Ewell | 2 Feb 03:48
Favicon

Re: ISO 639-3 changes, part ? (Was ISO 639-3 changes, part 1)

CE Whitehead wrote:

>> But please hold off on Lushootseed for the moment.
>
> I thought I was supposed to do all the first group of retired changes 
> (I've already done 'lut', 'lushootseed', but have put in inside of 
> brackets for now; let me know when you want it).

ISO 639-3/RA has informed me that they have pulled back the Lushootseed 
retirement.  This will be reflected on the official Web site on Tuesday. 
We have no work to do regarding this language at present.

>> Do not add Comments fields that simply duplicate the information in 
>> the Preferred-Value field.
>
> That was sort of what I suspected; sorry.
> (It would have been almost easier for you to just copy and paste these 
> than to train me would not it have?)

Maybe, but I decided to try an experiment in having someone else do 
these.  (No, I don't have any imminent plans to relinquish the Official 
Doug role.  It's more of an experiment.)

--
Doug Ewell  |  Thornton, Colorado, USA  |  http://www.ewellic.org
RFC 5645, 4645, UTN #14  |  ietf-languages @ http://is.gd/2kf0s ­

_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Permalink | Reply | 0 comments |
headers
Doug Ewell | 2 Feb 04:24
Favicon

Re: ISO 639-3 changes, part 2

Kent Karlsson <kent dot karlsson14 at comhem dot se> wrote:

>> Deprecated: 2010-03-01
>> Preferred-Value: khk
>> ...
>>    Preferred-Value: khk
>>    Deprecated: 2010-03-01
>
> Please give the fields (lines) in the same order; just be be 
> consistent. Pick the order of fields used in the registry. It does not 
> formally matter, but it makes it easier to proof-read.

I agree 100% with Kent here.  The usual order is Deprecated, then 
Preferred-Value.

>>    This registration tracks a change made to ISO 639-3 effective
>>    2010-01-20, retiring the code element, 'drh', for Darkhat.
>
> I think the information that "Merge[d] with Halh Mongolian [khk]" 
> (from the RA's "change request summary") should be picked up here.

I had previously told CE that "it's probably not necessary" to include 
this information, since the record already shows that 'khk' is the 
Preferred-Value.  It's also not harmful, though, and in the last 24 
hours I've swung a bit toward Kent's viewpoint.  It's certainly not 
critical one way or the other.

>> Description: Beti
>
> This is for "Beti (Cameroon)", not to be confused with "Beti (Côte 
> d'Ivoire)".

Kent is right.  This is currently listed in 639-3, the Registry, and the 
Summary report as "Beti (Cameroon)", and needs to remain unaltered here.

>> Added: 2009-07-29
>> Deprecated: 2010-03-01
>
> I'm not so sure this one should be plainly "deprecated". Since "btb", 
> Beti (Cameroon) [languages], has been determined to be a 
> "group"/collection, "btb" should be regarded as a "collective code". 
> Here I find it troublesome that 639-5 registrations are handled by a 
> different RA, which in addition seems unresponsive to changes of this 
> kind.

This is *completely* wrong.  We are required ("MUST") to deprecate 
subtags whose code elements have been withdrawn in the core standard. 
See Section 3.4, item 14.

It is not our place to decide whether 639-5 will or should pick this up 
as a collection code element.  If and when they do, we can un-deprecate 
'btb' and add the "Scope: collection" field.  Remember that under RFC 
5646 we now have the ability to un-deprecate a subtag, which was not 
allowed under 4646.

The 639-3 comment that "Beti is a group name, not an individual language 
name" gives us no authority whatsoever to exempt this subtag from the 
requirements in Section 3.4.

>> Preferred-Value:
>
> There should be no preferred-value line here. This, and the comments 
> above, applies also to the "registration form" just below.

Correct.  If there is no Preferred-Value (or other attribute), then the 
line simply doesn't appear in the Registry.

>>    This registration tracks a change made to ISO 639-3 effective
>>    2010-01-20, retiring the code element, 'cmk', for Chimakum.
>
> The following should be picked up from the "change request summary": 
> "Duplicate of [xch]"; or better formulated "This code is a duplicate 
> for [xch], Chemakum". (Personally, I think they should have picked the 
> other code to deprecate, but oh well...)

A valid opinion, but one which has no bearing on what we do here.  The 
RA withdrew 'cmk' and that's that.

>> Description: Lushootseed
>> Added: 2009-07-29
>> Deprecated: 2010-03-01
>
> Again, I'm not so sure this one should be plainly "deprecated". Since 
> "lut", Lushootseed, has been determined to be a "group"/collection, 
> "lut" should be regarded as a "collective code".

Again, these comments from 639-3 do not guide what we do here.  639-3 
doesn't decide what is or isn't a collection, 639-5 does, and on their 
own schedule.

However, as I wrote in another message, we need to disregard the 639-3 
action on Lushootseed altogether, since it is being rescinded.

>> Type: language
>> Subtag: mrt
>
> -> 'myt'. 'mrt' is for "Marghi Central", ("Central Marghi"...)

I suspect this was a typo, the sort that creeps in easily in this sort 
of work, and that's why I recommend careful copying and pasting of such 
things in preference to typing, and why double- and triple-checking is 
paramount.

I don't think Kent mentioned this, but CE also included a blank line 
before the final "%%" in some records.  This is not critical in 
registration forms, but MUST NOT appear in records.  There must also be 
only one space between the ":" and the field value, but this error was 
only made in the Lushootseed record which we are not going to process.

--
Doug Ewell  |  Thornton, Colorado, USA  |  http://www.ewellic.org
RFC 5645, 4645, UTN #14  |  ietf-languages @ http://is.gd/2kf0s ­ 

_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Permalink | Reply | 0 comments |
headers
CE Whitehead | 2 Feb 06:15
Picon

RE: ISO 639-3 changes, part 2

Hi.  I have gotten Kent's and Doug's corrections/comments and hope to have the corrected records in early tomorrow if not tonight; most corrections are done!

Doug Ewell doug at ewellic.org
Tue Feb 2 04:24:29 CET 2010
 
Kent Karlsson <kent dot karlsson14 at comhem dot se> wrote:
 
>> Deprecated: 2010-03-01
>> Preferred-Value: khk
>> ...
>>    Preferred-Value: khk
>>    Deprecated: 2010-03-01
>
> Please give the fields (lines) in the same order; just be be
> consistent. Pick the order of fields used in the registry. It does not
> formally matter, but it makes it easier to proof-read.
 
> I agree 100% with Kent here.  The usual order is Deprecated, then
> Preferred-Value.
 
O.k. I switched the order around a bit; Idid not think I was supposed to but some forms had it differently . . .including the one in RFC 5646 3.5 -- and that's why I switched in the end; sorry!  After Doug's message last time I went through and copied everything from RFC 5646 that I could find there (http://tools.ietf.org/html/rfc5646#section-3.5).  (Maybe we should correct the registration form example there. . . or does the order really matter?) What I could not find in rfc 5646 I copied from elsewhere.  (it was troubling yes; the order of fields was not always the same . . . )
 
>>>    This registration tracks a change made to ISO 639-3 effective
>>>    2010-01-20, retiring the code element, 'drh', for Darkhat.
>>
>> I think the information that "Merge[d] with Halh Mongolian [khk]"
>> (from the RA's "change request summary") should be picked up here.
 
>I had previously told CE that "it's probably not necessary" to include
>this information, since the record already shows that 'khk' is the
>Preferred-Value.  It's also not harmful, though, and in the last 24
>hours I've swung a bit toward Kent's viewpoint.  It's certainly not
>critical one way or the other.
I agree with Kent too and will copy him on this.
>>> Description: Beti
>>
>> This is for "Beti (Cameroon)", not to be confused with "Beti (Côte
>> d'Ivoire)".
 
>Kent is right.  This is currently listed in 639-3, the Registry, and the
>Summary report as "Beti (Cameroon)", and needs to remain unaltered here.
Oops!  Corrected.
>> Added: 2009-07-29
>> Deprecated: 2010-03-01
>
>> I'm not so sure this one should be plainly "deprecated". Since "btb",
>> Beti (Cameroon) [languages], has been determined to be a
>> "group"/collection, "btb" should be regarded as a "collective code".
>> Here I find it troublesome that 639-5 registrations are handled by a
>> different RA, which in addition seems unresponsive to changes of this
>> kind.
 
>This is *completely* wrong.  We are required ("MUST") to deprecate
>subtags whose code elements have been withdrawn in the core standard.
>See Section 3.4, item 14.
 
>It is not our place to decide whether 639-5 will or should pick this up
>as a collection code element.  If and when they do, we can un-deprecate
>'btb' and add the "Scope: collection" field.  Remember that under RFC
>5646 we now have the ability to un-deprecate a subtag, which was not
>allowed under 4646.
Thanks.
 
>The 639-3 comment that "Beti is a group name, not an individual language
>name" gives us no authority whatsoever to exempt this subtag from the
>requirements in Section 3.4.
This was my impression.  Thanks Doug for clarifying this.
>> Preferred-Value:
>
>> There should be no preferred-value line here. This, and the comments
>> above, applies also to the "registration form" just below.
 
>Correct.  If there is no Preferred-Value (or other attribute), then the
>line simply doesn't appear in the Registry.
I'll remove the 'Preferred-Value' field here then.
 
 
>> Description: Lushootseed
>> Added: 2009-07-29
>> Deprecated: 2010-03-01
>
>> Again, I'm not so sure this one should be plainly "deprecated". Since
>> "lut", Lushootseed, has been determined to be a "group"/collection,
>> "lut" should be regarded as a "collective code".
 
>Again, these comments from 639-3 do not guide what we do here.  639-3
>doesn't decide what is or isn't a collection, 639-5 does, and on their
>own schedule.
 
>However, as I wrote in another message, we need to disregard the 639-3
>action on Lushootseed altogether, since it is being rescinded.
O.k. I'll remove the change request record!
>> Type: language
>> Subtag: mrt
>
>> -> 'myt'. 'mrt' is for "Marghi Central", ("Central Marghi"...)
 
> I suspect this was a typo,
 
Corrected; I thought I checked everything twice.
 
 
> I don't think Kent mentioned this, but CE also included a blank line
> before the final "%%" in some records.  This is not critical in
> registration forms, but MUST NOT appear in records.  There must also be
> only one space between the ":" and the field value, but this error was
> only made in the Lushootseed record which we are not going to process.
Thanks for catching these.
>--
>Doug Ewell  |  Thornton, Colorado, USA  |  http://www.ewellic.org
>RFC 5645, 4645, UTN #14  |  ietf-languages <at> http://is.gd/2kf0s ­
 
* * *
Kent Karlsson kent.karlsson14 at comhem.se
Mon Feb 1 19:52:27 CET 2010
 
 
>See comments below.
 
>    /kent k
 
 
>Den 2010-02-01 18.17, skrev "CE Whitehead" <cewcathar at hotmail.com>:
 
> Re: ISO 639-3 changes, part 2 ?
 
>(I don't like your over-use of question marks... It's bad style even for an
 
>email.)
 
Hmm.  When I'm sure of myself I don't use them; they indicate where I need a response.
But o.k.; will try to cut down on those in my emails to this list. 
 
 
Again, I'll email the corrections A.S.A.P. tonight or tomorrow.
 
Best,
 
C. E. Whitehead
cewcathar <at> hotmail.com

_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Permalink | Reply | 2 comments |
headers
Doug Ewell | 2 Feb 15:23
Favicon

Re: ISO 639-3 changes, part 2

CE Whitehead wrote:

>> I agree 100% with Kent here.  The usual order is Deprecated, then 
>> Preferred-Value.
>
> O.k. I switched the order around a bit; Idid not think I was supposed 
> to but some forms had it differently . . .including the one in RFC 
> 5646 3.5 -- and that's why I switched in the end; sorry!

You are right that Figure 5 in Section 3.5 puts Preferred-Value ahead of 
Description.  I wish I had noticed that sometime during the long 
development period.

In any case, Kent is right that the order of fields within a record is 
not normative, but I do prefer to keep them in the order in which they 
appear in Section 3.1.2.

I also noticed that Figure 5 not only includes a placeholder for 
Comments, but for lots of other fields as well that might not be used 
for a given registration.  Since I haven't been gratuitously plugging in 
empty Suppress-Script and Macrolanguage fields in forms, I'll stop 
reflexively adding blank Comments fields as well.  That probably led to 
CE's confusion in thinking that blank fields might be appropriate for 
the records too.

--
Doug Ewell  |  Thornton, Colorado, USA  |  http://www.ewellic.org
RFC 5645, 4645, UTN #14  |  ietf-languages @ http://is.gd/2kf0s ­

_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Permalink | Reply | 1 comment |
headers
CE Whitehead | 2 Feb 20:12
Picon

RE: ISO 639-3 changes, part 2

 
Hi!  I hope my records/forms will  now be all o.k.  (It's the second time I've sent these revised changes; I don't know what happened to my second email last night; I assumed you all wanted these right off.  One question: since Doug has been using quotation marks in the "other relevant information" field, is it still o.k. to have brackets as well in that field?  Also, should I, as Doug says, take out the blank comments fields from my registration forms--forms which I copied of course, partly from Doug, partly from the forms for 'heploc,' and partly from the form in section 3.5 of rfc 5646.)
 
-----
LANGUAGE SUBTAG MODIFICATION
File-Date: 2010-03-01
%%
Type: language
Subtag: drh
Description: Darkhat
Added: 2009-07-29
Deprecated: 2010-03-01
Preferred-Value: khk
%%
---
 
LANGUAGE SUBTAG REGISTRATION FORM
1. Name of requester: C. E. Whitehead
2. E-mail address of requester: cewcathar at hotmail.com
3. Record Requested:
   Type: language
   Subtag: drh
   Description: Darkhat
   Deprecated: 2010-03-01
   Preferred-Value: khk
   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 639-3 effective
   2010-01-20, retiring the code element, 'drh', for Darkhat.  Merged with Halh Mongolian [khk].
   For more information on the ISO 639-3 change, refer to
   http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2009_Summary.pdf

-----
LANGUAGE SUBTAG MODIFICATION
File-Date: 2010-03-01
%%
Type: language
Subtag: tnf
Description: Tangshewi
Added: 2009-07-29
Deprecated: 2010-03-01
Preferred-Value: prs
%%
---
 
LANGUAGE SUBTAG REGISTRATION FORM
1. Name of requester: C. E. Whitehead
2. E-mail address of requester: cewcathar at hotmail.com
3. Record Requested:
   Type: language
   Subtag: tnf
   Description: Tangshewi
   Deprecated: 2010-03-01
   Preferred-Value: prs
   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 639-3 effective
   2010-01-20, retiring the code element, 'tnf', for Tangshewi.  Merged with Dari [prs].
   For more information on the ISO 639-3 change, refer to
   http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2009_Summary.pdf

-----
LANGUAGE SUBTAG MODIFICATION
File-Date: 2010-03-01
%%
Type: language
Subtag: drw
Description: Darwazi
Added: 2009-07-29
Deprecated: 2010-03-01
Preferred-Value: prs
%%
---
 
LANGUAGE SUBTAG REGISTRATION FORM
1. Name of requester: C. E. Whitehead
2. E-mail address of requester: cewcathar at hotmail.com
3. Record Requested:
   Type: language
   Subtag: drw
   Description:
   Deprecated: 2010-03-01
   Preferred-Value: prs
   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 639-3 effective
   2010-01-20, retiring the code element, 'drw', for Darwazi.  Merged with Dari [prs].
   For more information on the ISO 639-3 change, refer to
   http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2009_Summary.pdf

-----
LANGUAGE SUBTAG MODIFICATION
File-Date: 2010-03-01
%%
Type: language
Subtag: btb
Description: Beti (Cameroon)
Added: 2009-07-29
Deprecated: 2010-03-01
Comments: see beb, bum, bxp, eto, ewo, fan, mct
%%
---
 
LANGUAGE SUBTAG REGISTRATION FORM
1. Name of requester: C. E. Whitehead
2. E-mail address of requester: cewcathar at hotmail.com
3. Record Requested:
   Type: language
   Subtag: btb
   Description: Beti (Cameroon)
   Deprecated: 2010-03-01
   Comments: see beb, bum, bxp, eto, ewo, fan, mct
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 639-3 effective
   2010-01-20, retiring the code element, 'btb', for Beti (Cameroon).  
   Beti is a group name.  Member languages already have code elements.
   For more information on the ISO 639-3 change, refer to
   http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2009_Summary.pdf

-----
LANGUAGE SUBTAG MODIFICATION
File-Date: 2010-03-01
%%
Type: language
Subtag: cmk
Description: Chimakum
Added: 2009-07-29
Deprecated: 2010-03-01
Preferred-Value: xch
%%
---

LANGUAGE SUBTAG REGISTRATION FORM
1. Name of requester: C. E. Whitehead
2. E-mail address of requester: cewcathar at hotmail.com
3. Record Requested:
   Type: language
   Subtag: cmk
   Description: Chimakum
   Deprecated: 2010-03-01
   Preferred-Value: xch
   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 639-3 effective
   2010-01-20, retiring the code element, 'cmk', for Chimakum. 
   The code [cmk] is a duplicate for [xch].
   For more information on the ISO 639-3 change, refer to
   http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2009_Summary.pdf 

-----
LANGUAGE SUBTAG MODIFICATION
File-Date: 2010-03-01
%%
Type: language
Subtag: cjr
Description: Chorotega
Added: 2009-07-29
Deprecated: 2010-03-01
Preferred-Value: mom
%%
---

LANGUAGE SUBTAG REGISTRATION FORM
1. Name of requester: C. E. Whitehead
2. E-mail address of requester: cewcathar at hotmail.com
3. Record Requested:
   Type: language
   Subtag: cjr
   Description: Chorotega
   Deprecated: 2010-03-01
   Preferred-Value: mom
   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 639-3 effective
   2010-01-20, retiring the code element, 'cjr', for Chorotega.  Merged with Monimbo [mom].
   For more information on the ISO 639-3 change, refer to
   http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2009_Summary.pdf
 
-----
LANGUAGE SUBTAG MODIFICATION
File-Date: 2010-03-01
%%
Type: language
Subtag: gav
Description: Gabutamon
Added: 2009-07-29
Deprecated: 2010-03-01
Preferred-Value: dev
%%
---

LANGUAGE SUBTAG REGISTRATION FORM
1. Name of requester: C. E. Whitehead
2. E-mail address of requester: cewcathar at hotmail.com
3. Record Requested:
   Type: language
   Subtag: gav
   Description: Gabutamon
   Deprecated: 2010-03-01
   Preferred-Value: dev
 
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 639-3 effective
   2010-01-20, retiring the code element, 'gav', for Gabutamon.  Merged with Domung [dev].
   For more information on the ISO 639-3 change, refer to
   http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2009_Summary.pdf

-----
LANGUAGE SUBTAG MODIFICATION
File-Date: 2010-03-01
%%
Type: language
Subtag: mst
Description: Cataelano Mandaya
Added: 2009-07-29
Deprecated: 2010-03-01
Preferred-Value: mry
%%
---

LANGUAGE SUBTAG REGISTRATION FORM
1. Name of requester: C. E. Whitehead
2. E-mail address of requester: cewcathar at hotmail.com
3. Record Requested:
   Type: language
   Subtag: mst
   Description: Cataelano Mandaya
   Deprecated: 2010-03-01
   Preferred-Value: mry
 
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 639-3 effective
   2010-01-20, retiring the code element, 'mst', for Cataelano Mandaya.  Merged with Mandaya [mry].
   For more information on the ISO 639-3 change, refer to
   http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2009_Summary.pdf

-----
LANGUAGE SUBTAG MODIFICATION
File-Date: 2010-03-01
%%
Type: language
Subtag: myt
Description: Sangab Mandaya
Added: 2009-07-29
Deprecated: 2010-03-01
Preferred-Value: mry
%%
---

LANGUAGE SUBTAG REGISTRATION FORM
1. Name of requester: C. E. Whitehead
2. E-mail address of requester: cewcathar at hotmail.com
3. Record Requested:
   Type: language
   Subtag: myt
   Description: Sangab Mandaya
   Deprecated: 2010-03-01
   Preferred-Value: mry
 
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 639-3 effective
   2010-01-20, retiring the code element, 'mrt', for Sangab Mandaya.  Merged with Mandaya [mry].
   For more information on the ISO 639-3 change, refer to
   http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2009_Summary.pdf
 
--
C. E. Whitehead
cewcathar <at> hotmail.com
* * *
 
_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Permalink | Reply | 0 comments |

Gmane