Re: unicode string functions

[Simon Josefsson]

Bruno Haible <address@hidden> 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 directories:
>
>   unistr     elementary string functions
>   uniconv    conversion from/to legacy encodings
>   unistdio   formatted output to strings
>   uniname    character names
>   uniwidth   string width when using nonproportional fonts
>   unilbrk    line breaking algorithm
>   unictype   character classification and properties

Nice!  I'm sure LibIDN could use some of these modules.  Currently I
copied code from glib and modified it, which is not very maintainable.

>   unicase    case folding

Is this NFKC?

One feature request: make it possible to use a particular version of
Unicode.  The IDN stuff requires that Unicode 3.2 is used, and will
return incorrect results if used with a newer Unicode version.  Would
that be problematic to support?  It would be nice if you could keep
this idea in mind when implementing it.

/Simon