On Sat, Jun 01, 2002 at 02:20:15AM +0900, Dan Kogai wrote:
> >2) If not, would a Encode::ICU be wise?
> I'm not so sure. But if I were the one to implement Encode::ICU, it
> will not be just a compiled collection of UCM files but a wrapper to all
> library functions that ICU has to offer. I, f
> On Fri, May 31, 2002 at 06:18:55AM +0900, Dan Kogai wrote:
>actually adopted. Useful it may be I found raw ICM too Big and too
>Blue :)
Whats that mean, too Blue? :)
-Melvin
On Saturday, June 1, 2002, at 12:34 AM, Autrijus Tang wrote:
> On Fri, May 31, 2002 at 06:18:55AM +0900, Dan Kogai wrote:
>> As a matter of fact GB18030 is ALREADY supported via Encode::HanExtra
>> by
>> Autrijus Tang. The only reason GB18030 was not included in Encode main
>> is sheer size of t
On Fri, May 31, 2002 at 06:18:55AM +0900, Dan Kogai wrote:
> As a matter of fact GB18030 is ALREADY supported via Encode::HanExtra by
> Autrijus Tang. The only reason GB18030 was not included in Encode main
> is sheer size of the map.
Yes, partly because it was not implemented algorithmically.
On Fri, May 31, 2002 at 06:18:55AM +0900, Dan Kogai wrote:
> On Friday, May 31, 2002, at 06:06 AM, George Rhoten wrote:
> > Hopefully you take the implicit information in the UCM files and put
> > that
> > into encode implementation too. For instance, in gb18030 there are
> > whole
> > ranges o
On Friday, May 31, 2002, at 06:06 AM, George Rhoten wrote:
> Hopefully you take the implicit information in the UCM files and put
> that
> into encode implementation too. For instance, in gb18030 there are
> whole
> ranges of Unicode mappings that aren't in the UCM file, but they are in
> the
It's a good timing to make my first post to this mailing list.
On Thursday, May 30, 2002, at 09:04 PM, Bryan C. Warnock wrote:
> On Tue, 2002-05-28 at 17:42, George Rhoten wrote:
>
>> It is true that parts of ICU uses C++. Some parts of ICU are written
>> in C++
>> with a C wrapper. Some other p
On Tue, 2002-05-28 at 17:42, George Rhoten wrote:
> It is true that parts of ICU uses C++. Some parts of ICU are written in C++
> with a C wrapper. Some other parts are written in C with a C++ wrapper. It
> depends on the API being used. Most of the functionality in the common
> library is writt
Melvin Smith wrote:
> I'm curious, is it possible to carve out an "ICU-lite" in ANSI-C89?
It is possible, but it depends on what you want. From what I understand,
the ICU common library would cover most of your basic Unicode needs, and
most of the effort could be put there.
As I recall, the fol
At 02:42 PM 5/28/2002 -0700, George Rhoten wrote:
>Hello all,
>
>Hopefully I won't get too burned by flames by jumping into the middle of
>the conversation like this.
Fortunately this list is very low on flammable material. :)
Thanks for the helpful info. One of the concerns with using
an extern
10 matches
Mail list logo
