Hi Hristo,
On Wed, Nov 30, 2005 at 09:42:43 +0200, Hristo Simenov Hristov wrote:
> > I've a suspicion. Please enable CJK and/or CTL support under
> > Tools.Options.LanguageSettings.Languages and try again.
> Well, I set LANG_CJK instead LANG_ALL.
Which shouldn't be necessary, and even restricts your numbering to being
diplayed only if CJK is enabled. LANG_ALL should do as long as
getSupportedNumberingTypes() is called at all.
> Here is the hole line:
> {style::NumberingType::CHARS_BG_CYRILLIC_UPPER_LETTER, NULL, LANG_CJK},
> and it works. So, what I have to do now? To try to remove the condition
> (aLangOpt.IsCJKFontEnabled() || aLangOpt.IsCTLFontEnabled())?
Yes, that would be the clean way. I just created
http://qa.openoffice.org/issues/show_bug.cgi?id=58666
for this and set your issue dependant on that one.
> > If this is not a general Cyrillic numbering and there will be more than
> > one Cyrillic numbering, it must be assured that the
> > makeNumberingIdentifier() method will create distinct strings, as those
> > identfiers are used to distinguish the numbering types.
> I can't undestand this :(
> Did you mean to put something instead of NULL here:
> {style::NumberingType::CHARS_BG_CYRILLIC_UPPER_LETTER, NULL, LANG_CJK},
Yes. I'll create examples using Latin script, since I don't know
Cyrillic ;) Let's assume we have two alphabetic numberings:
1. A,B,C,D,E,F,G,...
2. A,B,C,D,K,L,M,...
these two only differ somewhere in the middle. If the identifier string
was "A,B,C" for both, they're not distinguishable. Instead, one should
be "A,B,C" and the other "A,B,...,K" or similar, whatever would be
convenient and shows a clear intention to the user. These identifiers
are also used in the file format and matched when loading documents, so
it is important that they are thoroughly selected, meaningful, and once
finalized never be changed again.
> > > Also it appears that when it used capital letter
> > > numbering only the first one is capital, the rest have to be a small one.
> > > So I had to add a new method which I called lcl_formatChars2.
> >
> > Please create a matching aSupportedTypes.cSymbol string then, using
> > UTF-8 encoding as I mentioned in my previous mail.
> I presume that you mean if I put something in Cyrillic instead of NULL?
Yes, with the same precautions as above.
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]
