The problem with ICU is that it's a rather large library, and mozilla
already has it's own unicode system.  That's we we opted on doing
unicode support ourselves (less code duplication, and a smaller
binary).

Cheers,

Shawn Wilsher

On Jan 24, 2008 11:35 PM, Dan <[EMAIL PROTECTED]> wrote:
>
> On Jan 25, 2008, at 7:26 AM, Myk Melez wrote:
>
> > Hi all,
> >
> > I'm working to enable FTS3 in the next version of Firefox [1] so
> > that extenders can take advantage of it, although Firefox itself
> > isn't using it for the next release.
> >
> > Given Firefox's international audience, it would be useful for FTS3
> > to support Unicode.  We currently do this for upper(), lower(), and
> > LIKE by redefining them with sqlite3_create_function [2].
> >
> > For FTS3 it seems like we'd have to redefine the tokenizer and
> > MATCH. Can that be done using sqlite3_create_function, and what's
> > the status of the international support mentioned in a previous
> > message on this list [3]?
>
> Hi Myk,
>
> The 'icu' and 'fts3' SQLite extensions can take advantage of the
> ICU library to provide internationalization if it is available.
> The ICU extension provides internationalized versions of upper(),
> lower(), collation sequences and a REGEXP operator. Details
> are available here:
>
>    http://www.sqlite.org/cvstrac/fileview?f=sqlite/ext/icu/README.txt
>
> Fts3 has an API for creating new tokenizers. See here:
>
>    http://www.sqlite.org/cvstrac/fileview?f=sqlite/ext/fts3/
> README.tokenizers
>
> One of the example tokenizers uses the ICU library for localization.
> See the same document for details. It is built if the
> SQLITE_ENABLE_ICU macro is defined when fts3 is compiled.
>
> Regards,
> Dan.
>
>
>
>
>
>
>
> -----------------------------------------------------------------------------
> To unsubscribe, send email to [EMAIL PROTECTED]
> -----------------------------------------------------------------------------
>
>

-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------

Reply via email to