Hi, FYI, effective after integration of CWS localedata4, see http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=2395&Path=SRC680%2Flocaledata4
Type "required" because if you happen to have private locale data in your build environment this might now even fail to build ;-) In case you plan to submit new locale data I strongly urge you to run the tests as described in i18npool/source/localedata/data/locale.dtd as of version in or after CWS localedata4. Thanks Eike ----- Forwarded message from [EMAIL PROTECTED] ----- Date: Wed, 27 Apr 2005 20:39:51 +0200 (MEST) Subject: [interface-announce] required/CWS localedata4 : Locale data checks during build time and runtime From: [EMAIL PROTECTED] Delivered-To: mailing list [email protected] +------------------------------------------------------------------------+ | Type | required | |-------------------+----------------------------------------------------| | Title | Locale data checks during build time and runtime | |-------------------+----------------------------------------------------| | Posted by | [EMAIL PROTECTED] | |-------------------+----------------------------------------------------| | Affected | ,i18npool | |-------------------+----------------------------------------------------| | Effective from | CWS localedata4 | +------------------------------------------------------------------------+ Summary Runtime checks of locale data enabled if environment variable OOO_ENABLE_LOCALE_DATA_CHECKS is set to "Yes" or "1". Very basic build time checks implemented. Description The non-product builds always implemented several checks that validate locale data during runtime, especiallly number format codes that can't really be evaluated by other means than the number formatter itself. As almost no one except Hamburg release engineering does non-product builds, the checks are now also included in a product build but only activated by setting some environment variable. This will hopefully prevent defect locale data being submitted, which in the past was quite often the case. Setting the environment variable OOO_ENABLE_LOCALE_DATA_CHECKS to 'Y' or 'Yes' (or any other string starting with 'Y') or '1' before starting the application outputs messages to stderr if checks fail and also works in a product build. In a non-product build the checks are still always enabled. Additionally introduced some very basic checks during build time, which if failed will break the build. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ----- End forwarded message ----- -- 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]
