[EMAIL PROTECTED] wrote:
> Again the glibc code has a whole set of wide characters handling
> routines. In fact the conversion tables all lead to wide
> charset. Having UTF-8 as an external charset (used when storing
> strings in bases, when read documents) would allow smooth
Obviously we have to *read* UTF-8 documents for compatibility with
everyone. I think we're discussing exactly the same approach. Of course,
as Torsten pointed out about the <LINK> tag, we'll need to introduce
code to recognize charset tags for documents. Not difficult, though it
makes any document duplication code a little more complex. ;-)
> I had a look at this when searching for i18n support. It only provides
> a small subset of the functions provided by glibc, as far as i18n support is
> concerned. Besides, it does not conform to the standard (?) iconv functions.
Yeah, I don't know how standard iconv functions are, though we could
certainly do an autoconf test for them for those of us running glibc 2.1
systems.
--
-Geoff Hutchison
Williams Students Online
http://wso.williams.edu/
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.
