Hi Nathanael,

On Thu, Aug 31, 2006 at 07:31:34 -0400, Nathanael Jones wrote:

> Hello, I need to add several locales to OpenOffice, and I was
> wondering what the schedule is for inclusion in upcoming versions of
> the stable branch,

With the train model, you just jump on the next waggon.. we include new
locales in every release as soon as they're ready and as time permits.

> and what process is required. I understand that an .xml file for each
> locale will need to be created, but not much else.

Most times that's true. Only in rare cases it is necessary to introduce
new code to handle specific features.

For each locale to be submitted create a separate issue and attach the
locale data file. Please validate the .xml file first, for instructions
see i18npool/source/localedata/data/locale.dtd where you'll also find
additional valuable information. If the file doesn't even validate I may
simply reject it if it isn't just a simple error like a typo or such.

It helps a lot if you at least test compile the locale data in a build
environment to see if there are any data errors that can't be spotted by
validation. It helps even more if you also tested the locale data by
adding it to i18npool/source/localedata/locale.cxx and the necessary
exports to one of the i18npool/source/localedata/data/localedata_*.map
files, build and shove the resulting library under an existing OOo
installation and follow the guidelines mentioned in
i18npool/source/localedata/data/locale.dtd

Please don't forget to submit a signed JCA, see
http://contributing.openoffice.org/programming.html#jca


> Also, is there an equivalent to Alt-X in Open Office (that converts
> a previously typed hexadecimal into a character)? 

No, but you may use menu Insert.SpecialCharacter

> Here are some of the locales we are needing:

One preposition: please always use a 2 character code of ISO 639-1 if
available, then refer to ISO 639-2 3 character codes, and only if none
is available use ISO/DIS 639-3, thanks.

> Bemba              ISO/DIS 639-3: bem

'bem' is also ISO 639-2.

> Cebuano           ISO/DIS 639-3: ceb

'ceb' is also ISO 639-2.

> Chichewa          ISO/DIS 639-3: nya

This should be ISO 639-1 'ny' instead.

> Tumbuka           ISO/FDIS 639-3: tum

'tum' is also ISO 639-2.

> Danish              ISO/DIS 639-3: dan

This is ISO 639-1 'da' and already available as da-DK

> Éwé                  ISO/DIS 639-3: ee

This should be ISO 639-1 'ee' instead.

> Kirundi (Rundi) ISO/FDIS 639-3: run

This should be ISO 639-1 'rn' instead.

> Lingala              ISO/FDIS 639-3: lin

This should be ISO 639-1 'ln' instead.

> Luganda           ISO/DIS 639-3: lug

This should be ISO 639-1 'lg' instead.

> Tagalog            ISO/FDIS 639-3: tgl

This should be ISO 639-1 'tl' instead.

> Shona               ISO/FDIS 639-3: sna

This should be ISO 639-1 'sn' instead.

> North Sotho      ISO/FDIS 639-3: nso

This is ISO 639-2 'nso' and already available as nso-ZA

> Other languages that we work with:

You'll find most of them already available.

  Eike

P.S.: As you're not subscribed to the mailing list you were posting to,
you will miss replies that are directed to the list only. When answering,
please reply only to the list (Reply-To header is set), not to my
personal account. Thanks.

-- 
 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]

Reply via email to