Re: Bundling libxml2 and expat compatibility layer

Sterling Hughes <sterling@bumblebury.com> wrote: > On Sun, 2003-05-04 at 16:59, Adam Dickmeiss wrote: > > On Sun, May 04, 2003 at 11:21:19AM -0400, Sterling Hughes wrote: > > > On Sun, 2003-05-04 at 08:36, Adam Dickmeiss wrote: <snip> > > > Exactly what you said. :) It doesn't handle these encodings natively, > > > libxml2 does. Libxml2 can detect proper XML encodings, character sets, > > > and use the appropriate functions. It also natively detects and uses > > > iconv() to do encoding transformations. Its not that expat can't be > > > made to properly support unicode, but it can't be said that it does. > > > > Strickly speaking libxml2 doesn't do the conversions either. Both libs > > use iconv which is just fine. As I said a number times, the fact that > > Expat does not interpret encodings is due to ("bad") code in ext/xml. > > > > Well, strictly speaking ;-), expat doesn't support UTF-16, libxml2 does. As for unicode stuff, iconv is not always responsible. It is natively handled within libxml2. iconv is needed to parse XMLs encoded in other than UTFs AFAIK. Moriyoshi