Hi "Reshat, On Thu, Aug 31, 2006 at 17:43:10 -1000, "Reshat Sabiq (Re�?at)" wrote:
> > [... implementation ...] according to the > > upcoming RFC 3066bis. This will most certainly not happen in the very > > near future. > Is there any timeline for this kind of thing. Maybe 3 years, 5 years? Not yet. Personally I'd like to have it implemented as soon as RFC 3066bis will be finalized. However, a schedule of 2-4 years may be realistic. > I think mozilla is trying to live w/ what's conventional now, Mozilla kind of has an easy going, as they're not concerned with document exchange or long-living addons. > Could we then do the following for the time being: > 1. register projects for: > crh > tt-TR Sure, why not. > 2. see what can be done in terms of accommodating iqtelif under tt-RU > in the future. If it's only for UI localization and private use, one could also come up with fake locales to support different localizations, ISO 639 does have a reserved range for private use. However, these should not be written to documents => not selectable by the user or assigned as text attribute for spell-checking for example, so it's questionable whether it would be useful at all. > > What is the (a) most widely used script and (b) official form? The > > official one is Cyrillic, as far as I have understood the matter, so > > probably efforts should go into that direction. > De-juro i think it's called it's Cyrillic, but that's quite a bit out > of touch w/ reality, especially in digital environment. I wouldn't be > able to commit to associating tt w/ Cyrillic, simply because that's > not what's used in digital env. most of the time. Printed media, and > TV i suppose this would be true for, but language codes are > meaningless there at this time. What do governmental departments use in digital processing? I guess it's Cyrillic? If so, and you want a wide-spread use of OOo, you probably should support Cyrillic first. Eike -- OOo/SO Calc core developer. Number formatter stricken i18n transpositionizer. GnuPG key 0x293C05FD: 997A 4C60 CE41 0149 0DB3 9E96 2F1A D073 293C 05FD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
