On 27 January 2006 14:43, Eike Rathke wrote: > > > > 3. gregorian:MonthsOfYear.Month.MonthID // may ... > > Well, I'd still say current ooo setting is marginally better, w/r to ... > If that is the case, then please add it to your CLDR bug report. ... > 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.
Okay, thanks for the proposition. I'll look into references ASAP. ... > > #1387 CurrencySymbol // BYR > > "руб." or "бел.руб." ... > 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. In fact, I think such record is of almost no meaning outside the several countries where such cultural artifacts exist traditionally. Abbreviation doesn't equal symbol, after all. Perhaps, we should leave ISO code there? Safe choice? Otherwise, I think the primary setting should be "бел. руб.", to avoid ambiguity. > What about #1395, decimal places of the currency? CLDR states that there > are only integer amounts, OOo includes 2 decimals. Well, trivial currency data here doesn't include decimal places, indeed. OTOH, decimal places (kopecks) are still fairly commonly used, e.g., in tariffs. Bit of over-eagerness on part of CLDR here? > Thanks for the detailed answers. It seems that be_BY is quite > a difficult locale.. Oh, not really. As plain as any. :) -regards --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
