Re: AbiSource, Ispell, Aspell, take 2


Subject: Re: AbiSource, Ispell, Aspell, take 2
From: Robert Sievers (bob@abisource.com)
Date: Mon Mar 06 2000 - 10:47:44 CST


>Sender: hp@icon.labs.redhat.com
>To: Kevin Atkinson <kevinatk@home.com>
>Cc: abiword-dev@abisource.com
>Subject: Re: AbiSource, Ispell, Aspell, take 2
>References: <Pine.LNX.4.10.10003050431110.21419-100000@kevins-linux>
>From: Havoc Pennington <hp@redhat.com>
>Date: 06 Mar 2000 02:10:12 -0500
>In-Reply-To: Kevin Atkinson's message of "Sun, 5 Mar 2000 04:34:21 -0500
(EST)"
>Message-ID: <y5whfekzi97.fsf@icon.labs.redhat.com>
>Lines: 26
>User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.4
>MIME-Version: 1.0
>Content-Type: text/plain; charset=us-ascii
>
>
>(list will probably bounce my mail, feel free to forward...)
>
>Kevin Atkinson <kevinatk@home.com> writes:
>> <word> can be any one of const char *, const unsigned short *, or
>> const unsigned int *. Strings of const char * are expected to use
>> iso8859-1 or some other 256 bit character set as determined by the
>> current language in use. Stings of const unsigned short * and const
>> unsigned int * are expected to be in Unicode.
>>
>
>If you want to support multiple encodings you can't really do it by
>overloading types this way; for example UTF8 (which GTK+ and GNOME
>will use) is a multibyte unicode encoding that comes in a char*, not a
>unsigned short*/int*.
>
>You will need an enum or something.
>
>However it's probably easier to just do what GTK/GNOME will do, and
>require everything to get converted to UTF8 on its way in to the
>program, then all internal APIs use UTF8.
>
>Havoc



This archive was generated by hypermail 2b25 : Mon Mar 06 2000 - 10:45:51 CST