Hi Yury, On Fri, Jan 27, 2006 at 12:38:53 +0200, Yury Tarasievich wrote:
> Done. CLDR bug #962 (audit issues #1378 and #1379). Thank you. > > > 3. gregorian:MonthsOfYear.Month.MonthID // may > > > Formally, both variants are permissible. Bit of ambiguity here. Let it > > > be? > > > > If it really doesn't matter, I'd align to CLDR then. > > Well, I'd still say current ooo setting is marginally better, w/r to cultural > tradition. It isn't too uncommon for CLDR to err somewhat in such matters, > after all. If that is the case, then please add it to your CLDR bug report. Our goal isn't only to have correct OOo data, but also to get correct CLDR data. In future we want to be able to semi-automatically update OOo's locale data with CLDR content. Differences prevent us from doing so. To get changes in to the CLDR easier it helps to provide some evidence like official government websites or references to books. Even cultural tradition may be documented somewhere, for example in dissertations. If CLDR doesn't accept it, it was at least worth the try. If there aren't any official rules, I doubt there's justification to keep the old data. Btw, when reporting CLDR bugs it may be helpful to include an URL of the item as a pointer to our audit document, such as http://l10n.openoffice.org/nonav/i18n_framework/cldr/LocaleDataAudit_OOo202.html#1378 > > What about the other month name differences that seem to > > differ in capitalization? Also both permissible? > ... > > > 4. gregorian:DaysOfWeek.Day.DayID // tue > > > Irrelevant, as there is no standard here on such abbreviations. > > > > Same here, capitalization differences of other day names? > > *All* capitalisation-only differences in be_BY section of this audit are just > a matter of different presentations. Speaking *strictest*, Belarusian grammar > doesn't regard names of days and months as proper nouns, so CLDR is possibly > bit more correct here, disregarding that names are often capitalised in > definitions like this, with no consideration for grammars' rules. > > Your decision, I think. I'll align that to CLDR then. > > I assume OOo's BYR CurrencySymbol р. instead of BYR is correct? Please > > include that in your CLDR bug report then. > > Well, after re-checking with CLDR tables and ooo locales, what ought to be > here is (numbers of audit issues): > > #1383 CurrencyID // BYR > "BYR" > (as per ISO 4217 and per National Bank regulation) Already marked to be aligned. > #1387 CurrencySymbol // BYR > "руб." or "бел.руб." > (there really is no such symbol at the moment, but the above abbreviations > are > the ones commonly used for that purpose. I have no idea whether these are > acceptable w/r to string length, however. If not, then previous choice of > "р." would be acceptable, too.) The string length doesn't matter technically, it should be a choice of usage if there is no national standard. I guess few people write long terms for the currency symbol when pricing goods, for example. Don't know though how the CLDR regards this. Maybe because as long as there is no standard they use the ISO code instead. > #1391 CurrencyName // BYR > "беларускі рубель" > (if name is to be in national language, then CLDR is right here) Also marked to be aligned. What about #1395, decimal places of the currency? CLDR states that there are only integer amounts, OOo includes 2 decimals. Thanks for the detailed answers. It seems that be_BY is quite a difficult locale.. Eike -- 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]
