"Bruno Haible" <[EMAIL PROTECTED]> writes:
> Simon Josefsson wrote:
>> > unicasecase folding
>>
>> Is this NFKC?
>
> I didn't consider normalization functions so far, on the premise that text
> being exchanged between applications is assumed to be precomposed.
> But their presence in Java AP
Simon Josefsson wrote:
> > unicasecase folding
>
> Is this NFKC?
I didn't consider normalization functions so far, on the premise that text
being exchanged between applications is assumed to be precomposed.
But their presence in Java APIs and the IDN case shows that APIs for
composing and de
Bruno Haible <[EMAIL PROTECTED]> writes:
> I'll therefore add a set of modules for Unicode text handling.
>
> The choice of the in-memory representation (UTF-8, UTF-16 or UTF-32) is up to
> the application; libunistring supports all three equally.
>
> The modules are organized in the following dir
tion (UTF-8,
UTF-16 and UTF-32), but without installing a multi-megabyte library.
Someone wanting 2 or 3 Unicode string functions does not want to link
with a megabyte big library.
- The basic character type, ucs4_t, is an alias of uint32_t. But
one could not assume .
Gnulib solv
