On Friday 25 November 2005 21:59, Eike Rathke wrote:
> Hi Hristo,
>
> On Thu, Nov 24, 2005 at 10:36:13 +0200, Hristo Simenov Hristov wrote:
> > I tryed with latin letter and with NULL but still do not appear in
> > Options tab.
>
> I've a suspicion. Please enable CJK and/or CTL support under
> Tools.Options.LanguageSettings.Languages and try again. If that works,
> the culprit would be most certainly in
> sw/source/ui/misc/numberingtypelistbox.cxx at line 135, there is
> a condition
>
> if(0 != (nTypeFlags&INSERT_NUM_EXTENDED_TYPES) &&
> (aLangOpt.IsCJKFontEnabled() || aLangOpt.IsCTLFontEnabled()))
>
> wherein it calls
>
> Sequence<sal_Int16> aTypes =
> pImpl->xInfo->getSupportedNumberingTypes( );
>
> I assume the "&& (aLangOpt.IsCJKFontEnabled() ||
> aLangOpt.IsCTLFontEnabled())" above is wrong, and could be safely removed,
> as the
> getSupportedNumberingTypes() checks the CJK/CTL configuration thing
> itself and returns only the matching types. The condition was probably
> added before getSupportedNumberingTypes() checked the configuration
> itself, it prevents CJK/CTL symbols being displayed as squares if the
> fonts aren't available. Your type is of LANG_ALL and should be returned
> anyway, if the method was called at all.. however, the problem of
> Cyrillic glyphs not available in the font may persist in installations
> different from yours.
>
> If all this holds true please contact the Writer folks on the [EMAIL
> PROTECTED]
> mailing list.
Well, I set LANG_CJK instead LANG_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())?
> > I changed the names of the tables to table_bgCyrillicUpperLetter and
> > table_bgCyrillicLowerLetter. I left the bg because still not know is this
> > table will surve to other Cyrillic languages.
>
> 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},
> > 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?
regards
--
-------------------------------------------------------------
Hristo Simeonov Hristov
Leader of OpenOffice.org - Bulgarian
GnuPG key 0xD0D895EB: 0282 D8D0 90D3 963F E57E B0A7 2670 88D9 D0D8 95EB
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
