[Ltru] Serbo-Croatian Deprecations and Variants

Another practical question to consider in the new era.... I know Peter and 
I discussed this in the past, but I'm not sure if we raised the question 
to the rest of the group and it hasn't come up since 639-3 was published.

What should I do with films that have been categorized as Serbo-Croatian 
in the past? The language isn't suddenly different because the political 
climate changed since the films were first made. The distinction between 
Serbian and Croatian is not particularly significant in audio works, so we 
may not find it useful (from a business perspective) to do the research to 
make guesses as to whether any given film is more Serbian or Croatian. I 
am not talking about textual forms of the language -- only audio uses.

If I wish to maintain classifications previously made against this 
deprecated language that is now back in business in 639-3, would I extend 
the deprecated 639-1 prefix and include the 639-3 code; use one of the 
deprecated 639-2 codes; or just use the new 639-3 code alone? Which of 
these options is most "wise"?

I'm only considering this question in terms of spoken content and I 
realize we don't have the answer for this yet. But I figure answers start 
with questions (despite my studio's affiliation with "Jeopardy").

Regards,

Karen Broome

Karen_Broome@spe.sony.com 
08/03/2007 01:40 PM

To
LTRU Working Group <ltru@ietf.org>
cc

Subject
[Ltru] Question on variants

All, 

I need to update some tagging in a language list here at Sony Pictures. My 
current language requirement for Chinese languages is: 

Audio Languages: Used for dubbing and original language content. 

* Chinese (No other variant information known) = zh 
* Chinese (Mandarin, PRC) = zh-cmn-CN 
* Chinese (Mandarin, Taiwanese variant) = zh-cmn-TW 
* Chinese (Cantonese) = zh-yue 
* Chinese (Taiwanese) = zh-min-nan 

Text Languages: Used for localization of language other than the original 
language as well as captions and subtitles. Subtitles may also occur in an 
original version that features more than one language. 

* Chinese (No other variant information known) = zh 
* Chinese (Mandarin, Traditional) = zh-cmn-Hant 
* Chinese (Mandarin, Simplified) = zh-cmn-Hans 
* Chinese (Cantonese) = zh-yue 
* Chinese (Taiwanese) = zh-min-nan 

I'm not sure if we closed the discussion on whether "zh-cmn" or "cmn" will 
be preferred in RFC 4646bis. Of these tags, which are most likely to be 
deprecated in the new regime? It's unclear to me how I should code 
Mandarin, Cantonese, and Taiwanese if I want the best chance of being 
compatible with the preferred tagging to be determined by this committee 
at a later date. I thought this business scenario might help the 
discussion, if this issue is not resolved yet. I looked through the 
archive and it doesn't look like this issue is closed. To me, the "zh" in 
these tags (especially written language categories) seems helpful. 

Regards, 

Karen Broome
Metadata Systems Designer
Sony Pictures Entertainment
310.244.4384 _______________________________________________
Ltru mailing list
Ltru@ietf.org
https://www1.ietf.org/mailman/listinfo/ltru