Hi KAD-KORVIGELLO�,

On Thu, Sep 08, 2005 at 16:07:52 +0200, KAD-KORVIGELLO� AN DROUIZIG wrote:

> I am currently filling the JCA and will send it to Eric tomorrow
> morning; I'll send the br_FR.xml file to the list as well

No, not to the list, please create a new issue, assign it to me ('er')
and attach the locale data file to the issue. Please don't forget to
state your real name in the issue so I can look it up in the list of
copyright approvals after your JCA arrived. Be sure the locale data
fulfills the requirements lined out in
i18npool/source/localedata/data/locale.dtd HEAD revision, is validated,
verified to work, best in SRC680_m121 or later, and passes the tests
mentioned.

> (BTW, as far as I know, this file is not needed to allow any Language
> User Interface, it only defines local data for calendar, etc...).

Yes, locale data is not necessarily needed for UI localization. However,
there may be UI elements that will use locale data if available, such as
date displays and decimal and group separators in numeric fields.
Furthermore, having locale data available enables a locale to be set as
default document language under menu
Tools.Options.LanguageSettings.Languages.

> In fact the worst issue for us would be to miss the 2.0 announcement
> in the World Press or in the Web... this would be so bad so close to
> the final milestone, wouldn't it... So why wait ?  :O

Because somewhen we have to freeze UI strings and addition of new
locales for a release. We now seem to have arrived at this somewhen.
Also bear in mind that adding a completely new locale involves work to
be done by several people, developers, release engineers, QA. It is also
quite normal that new localizations are added after the first major
release, OOo2.0.1 will not be very far away in the future.

  Eike

-- 
 OOo/SO Calc core developer. Number formatter bedevilled 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