[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Working on a locale to allow the use of ijekavian variant?



Hi All,

I am sorry for stepping into discussion so late, but I just want to say
that this localization naming proposal seems most natural approach. And
it is something that we discussed on DebConf.

So I give it:
 +1

BTW, for recoding from Cyrillic to Latin alphabet, I found that is most
simple to use `recode-sr-latin` from gettext package. Only a minor
changes in po headers are needed after it.

On 14.08.2011. 12:57, Christian PERRIER wrote:
>
> Final proposal:
>
> Translation files:
> Serbian, ijekavian variant, cyrillic: sr@ijekavian
> Serbian, ijekavian variant, latin: sr@ijekavianlatin
> Serbian, ekavian variant, cyrillic: sr
> Serbian, ekavian variant, latin: sr@latin
>   (the latter two are already used)
>
> Locales:
> Serbian, ekavian variant, cyrillic, Serbia: sr_RS  (already exists)
> Serbian, ekavian variant, latin, Serbia: sr_RS@latin  (already exists)
> Serbian, ijekavian variant, cyrillic, Bosnia and Herzegovina: sr_BA@ijakevian  (to be written)
> Serbian, ijekavian variant, latin, Bosnia and Herzegovina: sr_BA@ijakevianlatin  (to be written)
> Bosnian, latin, Bosnia and Herzegovina: bs_BA (already exists)
>

Best,
Janos

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: