To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=76153
------- Additional comments from [EMAIL PROTECTED] Thu Apr 19 19:25:07 +0000 2007 ------- Hi moyogo, > I'll send the JCA form asap. Good. Btw, what is your full name, so I can look it up in the list of approved assignments? > 1. The ThousandSeparator is ' ' non-breaking space. Thanks for noticing the > empty one. The format codes have to be adapted to use it. I'll do that. > 2. The ListSeparator is ' ; '. The separator should be one character only, I'll remove the surrounding blanks. > 3. I set the negative currency form to > <FormatCode>[CURRENCY] # ##0,00;[RED]-[CURRENCY] # ##0,00</FormatCode> Also the codes not having [RED] negatives probably should be adapted, I'll do. > 4. The CurrencySymbol is now "F", althought "Fc" is often encountered. Which means that also the LC_FORMAT replaceTo attribute should use 'F', will do. Btw, I assigned the MS-LangID 0x0639 to ln-CD, so it reads now replaceTo="[$F-639]". > 5. The IndexKey is now A-E Ɛ F-O Ɔ P-Z Fine. > Regarding the collation : > > the alphabetical order is the most common one I have encountered. > The morphological order (ln_morph) is recommended by some linguists so it > should > be available. > But I think the alphabetical order (ln_charset) should be the default, > unless there’s an official order that is set by decree or such, which hasn’t > happened. Since we don't have a "Morphological" collation algorithm yet, not even in the user interface, would that be a proper name? The alphabetical order usually is called "Alphanumeric". Note that most languages don't use a "Character Set" order, but have alphanumeric instead. The morphological order also resembles somewhat that of the hu_HU locale where a "charset" collation is used. As I'm absolutely not familiar with Lingala, could the alphabetical order be called "Alphanumeric" (and the collation data file be named ln_alphanumeric.txt) and the morpholigical order be called "Character Set" (and the file be named ln_charset.txt) instead? That way we wouldn't need an additional algorithm name and UI entry. The IndexKey element then should follow whatever we decide here and we may as well need two elements. I noticed the percent format codes have a blank between digits and the % character. This is usually not the case and the percent character immediately follows the number, like in 0% . Intended? Btw, the Locale element had the attribute allowUpdateFromCLDR="yes", which should only be set if normative locale data is available in the CLDR and the locale data may be updated semi-automatically. As we didn't do a comparison yet I defined that to "no". Eike --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
