Re: Serbian (sr) language translation team: maintainer unresponsive

[Charles Voelger <cvoelger dweasel com>]

On Lun, 2003-04-07 at 16:44, Danilo Segan wrote:
> On the other hand, it might be wiser to choose sr_lat, and sr (if one 
> wants to keep "sr" as latin, though anyone's preference shouldn't impact 
> the choice of the script), especially so because Serbian language comes 
> in two "dialects" (ekavian, and yekavian). Each of these dialects could 
> be written using any of cyrillic or latin, so we might have something like:
> sr@yek - Serbian yekavian
> sr_lat@yek - Serbian latin yekavian
> sr - Serbian ekavian
> sr_lat - Serbian latin ekavian

I am no expert, but I belive sr_lat is not the correct way to go.  As I
am to understand it the correct form should be:

ll_CC@xxxxx

with 'll' the lower case language code,
and 'CC' the uppercase country code,
asn "xxxxx" any modifier, 

everything after the language code is optional. you would probably want
to do:

sr
sr@latin
sr@yek
sr@yek_latin

and not molest the standard ll_CC format with "_lat" which is
non-standard.  everything after the @ can be what you choose, hence the
european languages that have the old for and a "@euro" form, which
include the euro character set.

I may be wrong, but this is how I understand the system should work.
maybe you could instead use a language code for yekavian seberian, if
there is no ISO two-letter code it offers me the oppurtunity to ask any
one who may know, what should one do in a situation where the language
doesn't have an ISO code? 


-- 
Charles Voelger <cvoelger@dweasel.com>