Hi Jonathon, On Thursday, 2006-10-26 13:01:30 -0700, Jonathon Blake wrote:
> What would be the best way to get Braille, Moon, and ASl included as > optional writing systems in OOo/SO? [Braille would include Braille 0, > Braille 1, Braille 1.5, Braille 2, Braille 2.5, Braille 3, Nemeth > Code ] If I understand correctly, technically spoken these are script types of existing languages. The problem with script types is that currently they are not supported by OOo, the few existing exemptions are made up of workarounds, nor does the ODF file format provide mechanisms for storing them. This will hopefully be solved in the next version of the standard. The new RFC 4646 does provide a script subtag field, but as the current ODF standard does not define a fo:script attribute and in its fo:language and fo:country attributes refers XSL 1.0 which in turn refers RFC 3066, the standard has to be enhanced first. > * Submit a request for Braille as an language of its own, with one > request for each grade. [Or more likely, two requests for each grade > --- that allows for multi-lingual content in Braille.] This could be a possibility, using RFC 3066 x-... private tags. However, there would be no connection to the underlying "real" language then, which I consider a major drawback. > * Submit a request for Braille for each language. [More specifically, > for each of those grades, for every language.] Using script subtags this would be the correct solution. Alas, not supported.. > * Submit a request for Moon as a langauge of its own; > * Submit a request for Moon as English (UK) (Moon) > > * Submti a request for ASL as a language of its own; > * Submit a request for ASL as English (US) (ASL); Also Moon and ASL look like script types to me, if I'm not mislead. > I'm not that concerned about Moon and ASL. [That is only two > additions to the drop down list.] > > Braille, is the big issue here. If all grades are included, for every > language which can be written in Braille, the size of the drop down > list goes up by roughly five thousand. OTOH, creating twelve or so > entries just for Braille, means that the locale data will be incorrect > more often than note. Yes, locale data would be a problem then. Note that in case OOo supported scripts, each locale, at least for the language dependent parts, would also need Braille locale data then. Quite an amount of new locales. Eike -- OOo/SO Calc core developer. Number formatter stricken i18n transpositionizer. OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't send personal mail to this [EMAIL PROTECTED] account, which I use for mailing lists only and don't read from outside Sun, use the [EMAIL PROTECTED] account instead if really needed. Thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
