[l10n-dev] Much too many TODOs in locale data audit
Hi, I updated http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html as far as I could. The outcome is a bunch of orange cells in the Solution columns with far too many TODOs. As a result, only a few locales will get aligned to the CLDR in this round. I urge every localization team to take a look at the data and discuss the TODO items on the [EMAIL PROTECTED] list. I hope to be able to do the next round for OOo2.0.1, and unsolved TODO: clarify items by then will simply be ignored and data aligned to CLDR. So please, take your chance now and state whether the CLDR needs different data for your locale of choice, and don't forget to give some reference, online or book, that we can include in bug reports against the CLDR, otherwise there might be difficulties to get changes in. Thank you. I'll attach a file to this mail showing the results in a condensed form. It is plain text, despite the extension, but in case you use the Vim editor and have the vimoutliner package installed you'll get some colors and have folds and percentage calculation and such. Eike -- OOo/SO Calc core developer. Number formatter bedevilled I18N transpositionizer. GnuPG key 0x293C05FD: 997A 4C60 CE41 0149 0DB3 9E96 2F1A D073 293C 05FD [_] 0% ToDo-List of Locale Data Alignment OOo with CLDR : according to : http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html [_] 0% Locales currently (OOo2.0) not to be aligned to CLDR [_] 0% Main players [_] 0% Big10 + pt_BR [_] 0% en [_] en_BZ (TODO: clarify) [_] en_CA (TODO: clarify) [_] en_GB (TODO: clarify) [_] en_IE (TODO: clarify) [_] en_PH (TODO: file CLDR bug) [_] 0% de [_] de_AT (TODO: clarify) [_] de_CH (TODO: hold it) [_] de_LI (TODO: hold it) [_] 0% fr [_] fr_BE (TODO: clarify) [_] fr_CA (TODO: clarify) [_] fr_CH (TODO: hold it) [_] fr_FR (TODO: clarify) [_] fr_LU (TODO: clarify) [_] fr_MC (TODO: clarify) [_] 0% es [_] es_UY (CLDR Bug 580) [_] es_BO (TODO: clarify) [_] es_CL (TODO: clarify) [_] es_CO (TODO: clarify) [_] es_CR (TODO: file CLDR bug) [_] es_DO (TODO: file CLDR bug) [_] es_EC (TODO: clarify; file CLDR bug) [_] es_ES (TODO: clarify) [_] es_GT (TODO: file CLDR bug) [_] es_HN (TODO: file CLDR bug) [_] es_MX (TODO: file CLDR bug) [_] es_NI (TODO: file CLDR bug) [_] es_PA (TODO: file CLDR bug) [_] es_PE (TODO: clarify; file CLDR bug) [_] es_PR (TODO: file CLDR bug) [_] es_PY (TODO: file CLDR bug) [_] es_SV (TODO: file CLDR bug) [_] es_UY (TODO: clarify; file CLDR bug) [_] 0% it [_] it_CH (TODO: hold it) [_] it_IT (TODO: clarify) [_] 0% sv [_] sv_FI (TODO: clarify; file CLDR bug) [_] sv_SE (TODO: clarify) [_] 0% ja [_] 0% ja_JPRED! not automatically alignable, only partial manual update [_] (TODO: align some items to CLDR) [_] (TODO: clarify) [_] 0% ko [_] 0% ko_KRRED! not automatically alignable, only
Re: [l10n-dev] Much too many TODOs in locale data audit
On Wednesday 13 April 2005 18:31, Eike Rathke wrote: Hi, I updated http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.htm l as far as I could. The outcome is a bunch of orange cells in the Solution columns with far too many TODOs. As a result, only a few locales will get aligned to the CLDR in this round. I urge every localization team to take a look at the data and discuss the TODO items on the [EMAIL PROTECTED] list. I hope to be able to do the next round for OOo2.0.1, and unsolved TODO: clarify items by then will simply be ignored and data aligned to CLDR. So please, take your chance now and state whether the CLDR needs different data for your locale of choice, and don't forget to give some reference, online or book, that we can include in bug reports against the CLDR, otherwise there might be difficulties to get changes in. Thank you. I'll attach a file to this mail showing the results in a condensed form. It is plain text, despite the extension, but in case you use the Vim editor and have the vimoutliner package installed you'll get some colors and have folds and percentage calculation and such. So, what can I do? Acording to this: http://www.jtcsv.com/cgibin/locale-bugs?findid=459 I think that it is fixed. Regards. -- - Hristo Simeonov Hristov Leader of OpenOffice.org - Bulgaria pgplLbmQKpmVg.pgp Description: PGP signature
Re: [l10n-dev] Much too many TODOs in locale data audit
if you have already provided feedback (as you have Hristo) then nothing further is required I believe. I assume there are no TODO: clarify items for your locale (the site seems to be unreachable at the moment) Peter Hristo Simenov Hristov wrote: On Wednesday 13 April 2005 18:31, Eike Rathke wrote: Hi, I updated http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.htm l as far as I could. The outcome is a bunch of orange cells in the Solution columns with far too many TODOs. As a result, only a few locales will get aligned to the CLDR in this round. I urge every localization team to take a look at the data and discuss the TODO items on the [EMAIL PROTECTED] list. I hope to be able to do the next round for OOo2.0.1, and unsolved TODO: clarify items by then will simply be ignored and data aligned to CLDR. So please, take your chance now and state whether the CLDR needs different data for your locale of choice, and don't forget to give some reference, online or book, that we can include in bug reports against the CLDR, otherwise there might be difficulties to get changes in. Thank you. I'll attach a file to this mail showing the results in a condensed form. It is plain text, despite the extension, but in case you use the Vim editor and have the vimoutliner package installed you'll get some colors and have folds and percentage calculation and such. So, what can I do? Acording to this: http://www.jtcsv.com/cgibin/locale-bugs?findid=459 I think that it is fixed. Regards. -- Peter Nugent, Software Engineer, Sun Microsystems Ireland Ltd, Hamilton House, East Point Business Park, Dublin 3, Ireland. Tel +353.1.8199522 Email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Much too many TODOs in locale data audit
Eike Can you provide the exact list of locales to be aligned to CLDR for 2.0 ? thx Peter Eike Rathke wrote: Hi, I updated http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html as far as I could. The outcome is a bunch of orange cells in the Solution columns with far too many TODOs. As a result, only a few locales will get aligned to the CLDR in this round. I urge every localization team to take a look at the data and discuss the TODO items on the [EMAIL PROTECTED] list. I hope to be able to do the next round for OOo2.0.1, and unsolved TODO: clarify items by then will simply be ignored and data aligned to CLDR. So please, take your chance now and state whether the CLDR needs different data for your locale of choice, and don't forget to give some reference, online or book, that we can include in bug reports against the CLDR, otherwise there might be difficulties to get changes in. Thank you. I'll attach a file to this mail showing the results in a condensed form. It is plain text, despite the extension, but in case you use the Vim editor and have the vimoutliner package installed you'll get some colors and have folds and percentage calculation and such. Eike [_] 0% ToDo-List of Locale Data Alignment OOo with CLDR : according to : http://l10n.openoffice.org/i18n_framework/cldr/LocaleDataAudit_OOo_CLDR.html [_] 0% Locales currently (OOo2.0) not to be aligned to CLDR [_] 0% Main players [_] 0% Big10 + pt_BR [_] 0% en [_] en_BZ (TODO: clarify) [_] en_CA (TODO: clarify) [_] en_GB (TODO: clarify) [_] en_IE (TODO: clarify) [_] en_PH (TODO: file CLDR bug) [_] 0% de [_] de_AT (TODO: clarify) [_] de_CH (TODO: hold it) [_] de_LI (TODO: hold it) [_] 0% fr [_] fr_BE (TODO: clarify) [_] fr_CA (TODO: clarify) [_] fr_CH (TODO: hold it) [_] fr_FR (TODO: clarify) [_] fr_LU (TODO: clarify) [_] fr_MC (TODO: clarify) [_] 0% es [_] es_UY (CLDR Bug 580) [_] es_BO (TODO: clarify) [_] es_CL (TODO: clarify) [_] es_CO (TODO: clarify) [_] es_CR (TODO: file CLDR bug) [_] es_DO (TODO: file CLDR bug) [_] es_EC (TODO: clarify; file CLDR bug) [_] es_ES (TODO: clarify) [_] es_GT (TODO: file CLDR bug) [_] es_HN (TODO: file CLDR bug) [_] es_MX (TODO: file CLDR bug) [_] es_NI (TODO: file CLDR bug) [_] es_PA (TODO: file CLDR bug) [_] es_PE (TODO: clarify; file CLDR bug) [_] es_PR (TODO: file CLDR bug) [_] es_PY (TODO: file CLDR bug) [_] es_SV (TODO: file CLDR bug) [_] es_UY (TODO: clarify; file CLDR bug) [_] 0% it [_] it_CH (TODO: hold it) [_] it_IT (TODO: clarify) [_] 0% sv [_] sv_FI (TODO: clarify; file CLDR bug) [_] sv_SE (TODO: clarify) [_] 0% ja [_] 0% ja_JPRED! not automatically alignable, only partial manual update [_] (TODO: align some items to CLDR) [_] (TODO: clarify) [_] 0% ko [_] 0% ko_KRRED! not automatically
Re: [l10n-dev] Much too many TODOs in locale data audit
Hi Hristo, On Wed, Apr 13, 2005 at 18:56:19 +0300, Hristo Simenov Hristov wrote: So, what can I do? Acording to this: http://www.jtcsv.com/cgibin/locale-bugs?findid=459 I think that it is fixed. That's for the bg_BG locale, which in the audit document has no TODO item, so nothing to do ;-) In this case the difference that had to be aligned to CLDR was fixed with issue 38813, and data is already aligned. The CLDR bug fixed will result in the next set of CLDR data published (scheduled for May) contain those fixes, and then OOo and CLDR will have identical data. If you have authorative answers for other locales' TODOs please don't hesitate to share your knowledge with us :-) 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]
Re: [l10n-dev] Much too many TODOs in locale data audit
Hi Peter, On Wed, Apr 13, 2005 at 17:51:51 +0100, Peter Nugent wrote: Can you provide the exact list of locales to be aligned to CLDR for 2.0 ? That's at the bottom of the cldr.otl I attached, you also quoted it ;-) [_] 0% Locales to be aligned [_] ar_EG [_] ar_LB [_] ar_SA [_] ar_TN [_] cy_GB [_] da_DK [_] de_DE [_] de_LU [_] en_AU [_] en_JM [_] en_NZ [_] en_TT [_] en_US [_] en_ZA [_] en_ZW [_] es_AR [_] fi_FI [_] id_ID [_] is_IS 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]
