Either Serbo-Croatian should be deprecated in all cases (i.e. in ISO 639-1
and ISO 639-2), or the deprecation should be deprecated in all cases (i.e.
it is not deprecated).
As Serbo-Croat existed, and is well documented, even though it may be no
longer the flavour of the month in some places, both the 2-letter code and
the 3-letter code should be retained for it.
Any other solution is plain illgical.
John
> I think that a good solution is to keep the alpha-3 ID in part 3
> ("un-deprecated") and to retain the deprecated note in the alpha-2 table.
> There certainly is a need to identify Serbo-Croatian, both for historical
> reasons and as a macrolanguage. What we would be saying then is that
> Serbo-Croatian can be encoded, but only/preferably with an alpha-3 ID.
>
> Håvard
>
>> -----Original Message-----
>> From: ISO 639 Joint Advisory Committee
>> [mailto:[log in to unmask]] On Behalf Of Peter Constable
>> Sent: 22. september 2004 18:54
>> To: [log in to unmask]
>> Subject: Re: Serbo-Croatian language
>>
>>
>> > From: ISO 639 Joint Advisory Committee [mailto:[log in to unmask]] On
>> > Behalf Of Håvard Hjulstad
>>
>> > It is correct that the entry "Serbo-Croatian" and its alpha-2
>> > identifier "sh" was deprecated by the JAC in 2000-02.
>>
>> With regard to this item, I included a macrolanguage
>> "Serbo-Croatian" in the code table for ISO 639-3 precisely
>> because an ID existed in 639-1 so that the statement "items
>> in the alpha-2 code are a subset of those in the alpha-3
>> code" could be, in fact, true. I had not noticed that "sh"
>> was deprecated, though, and so didn't mark the alpha-3 as deprecated.
>>
>> Of course, the alpha-3 can be marked as deprecated when the
>> part-3 table gets published. Or, if people really prefer,
>> this item can be dropped (though I think it's better to leave it).
>>
>>
>> Peter
>>
>> Peter Constable
>> Globalization Infrastructure and Font Technologies
>> Microsoft Windows Division
|