Re: Khotanese (was: ISO 639-2
Language Code Change Request)
I had received some information from Joan Spanne at
SIL that "sakan" was
the French, but it would be good for you to check your sources if
possible to make sure. I had added this to the change notice a week or
so ago at:
http://www.loc.gov/standards/iso639-2/php/code_changes.php
Rebecca
>>> Sonja Huard <[log in to unmask]> 10/31/08 3:58 AM >>>
I just realized that I need a French form for this one. Is it "sakan"?
Objet
Re: Khotanese (was: ISO 639-2 Language Code Change Request)
I just realized that I need a French form for this one. Is it "sakan"?
I
think we should also add Khotanese-Sakan (and then we would need
a
French
form for that as well)?
>>> Rebecca S Guenther <[log in to unmask]> 10/21/08 10:26 AM
>>>
I am ready to change this information in 639-2; now there is the
question
of 639-3. Christian responded that since the case was clear we could
bypass the normal process. I am not sure if we really need to ballot
this
one, since it is a change in 639-3. Perhaps we can use the process we
have
used for alternative name requests which are clear-- if anyone objects
to
this action in both 639-2 and 639-3, please address your concerns to
the
list by the end of this week, 24 Oct. 2008. At that time 639-3 could
consider it approved.
I think the name addition is clear enough, but I have an associated
procedural question with regard to the Part 3 duplicate code element
[xsk]
that now also ought to be retired. As I said, it never should have
gotten
into the code set, as it does essentially duplicate [kho]. Submission
of
new change proposals handled through our yearly cycle closed last month
(Sept. 1), so I can't put this one through our normal change review
process in 2008. I don't think it should wait for 2009. I also think
the
needed action is clear. Is there an action the JAC can take (or can I
take
it directly as the RA?) to correct this, that is, to retire [xsk] as a
duplicate without going through the usual 639-3 process?
Thanks for your input on this.
You might also want to check on some of the pending changes at
http://www.sil.org/iso639-3/chg_requests.asp
Some of them are more interesting than others. 2008-043 is the change
Subject
Fwd: ISO 639-2 Language Code Change Request
This request is from Joan.
It has apparently already been examined by SIL for 639-3.
If there aren't any objections, I will add it as an alternate name.
English name of Language: Khotanese
French name of Language: khotanais
iso_639_2_b: kho
iso_639_2_t: kho
change_requested: Add the name \"Sakan\". There is an
existing code
element for Sakan in ISO 639-3, [xsk], but it should (will) be retired,
as
essentially a duplicate of [kho]. This should have been identified and
dealt with when the draft ISO 639-3 code tables were generated, but we
missed it. Linguist List expresses a preference for the name \"Sakan\"
and
so we are requesting this name be added in 639-2. This is the text of
the
description that LinguistList has currently for [xsk]:
http://linguistlist.org/forms/langs/LLDescription.cfm?code=xsk
Language Name : Sakan
Alternate Name(s) : Khotanese Khotanese-Sakan
Once Spoken in : Uzbekistan Turkmenistan Afghanistan
Kazakhstan
Tajikistan China Kyrgyzstan
Language Code : xsk (Former code: XSK )
Status : Extinct
Family : Indo-European
Subgroup : Eastern Iranian
Subgrouping Code : IEIBA
Brief Description : This Middle Iranian language, is found in large
numbers of documents, ranging from letters to Buddhist texts, most of
which were found in the medieval kingdom of Khotan, centered around the
modern city of Hetian in Chinese Turkestan. It is written in a variant
of
the Brāhmī script. An ancient language of Central Asia.
100
BC -
1000 AD.
Submitter's name: Joan Spanne
Submitter's email : [log in to unmask]
Submitter's status : RA for ISO 639-3.
Avant d'imprimer, pensez à l'environnement.
Consider the environment before printing this mail. =