Hi Moheb,

On Sun, Apr 23, 2006 at 15:23:33 +0200, Moheb Mekhaiel wrote:

> I was trying to get my hunspell dic for Coptic
> to work under oo. I am not sure, if I have to
> do a complete localization as described in
> l10n.openoffice.org/i18n_framework/LocaleData.html

For spell-checking purposes only no locale data at all has to be
defined. The only requirements are an assigned LanguageID with
corresponding ISO code mappings and an entry in the language listbox.

> but I suppose that I have to define at least the
> <UnicodeScript> tag?

The UnicodeScript element in locale data is only needed for the LC_INDEX
element's context it appears in. It is used only internally to provide
hints to the index key mapping algorithm of which Unicode ranges
characters may appear in an index to calculate their weights.

> Anyhow I have noticed that the
> Unicode Segment for Coptic (new in Unicode 4.1.0) is
> not listed in the file:
> offapi/com/sun/star/i18n/UnicodeScript.idl

Unfortunately we'd have to address at least two problems for this..

First, OOo uses ICU for Unicode handling such as glyph layout, collation
and breakiterators. Currently ICU version 2.6 is used, which knows up to
Unicode 4.0, so just defining another constant wouldn't help much, if
there were any problems related to missing Unicode support. An upgrade
to ICU 3.4, which handles Unicode 4.1 is planned for OOo2.0.4.

Second, the css.i18n.UnicodeScript enum was somewhat ill-defined in this
API context, because enums aren't allowed to be extended beyond the last
value for compatibility reasons. For example, Java components would
throw an exception if they encountered new values that weren't in the
set when the Java code was compiled. For this, new constants would have
to be defined and an optional interface for the CharacterClassification
service to be used with these new values, additionally to the
XCharacterClassification::getScript() method.

However, did you try to use your dictionary without modifications to the
code base, perhaps by "misusing" an already existing locale? What were
the i18n related problems, if any, you encountered using it?

  Eike

P.S.: As you're not subscribed to the mailing list you were posting to,
you will miss replies that are directed to the list only. When answering,
please reply only to the list (Reply-To header is set), not to my
personal account. Thanks.

-- 
 PGP/OpenPGP/GnuPG encrypted mail preferred in all private communication.
 Key ID: 0x293C05FD - 997A 4C60 CE41 0149 0DB3  9E96 2F1A D073 293C 05FD

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to