Re: "Re: [xml] xmlParseChunk with UTF-16LE fails on special occasion"

On Fri, Nov 28, 2003 at 04:47:16PM +0100, Kasimier Buchcik wrote:
This seems still somehow inconsistent to me, since the parser will not take the 
declared encoding if all data is processed with the first chunk.

Does anybody have a hint on how to let the push parser eat UTF-16LE regardless of
the declared encoding - if this is possible at all?


Can you restate cleanly what the problem is.
You have an UTF-16 entity. It's labelled with encoding= which is
not compatible with UTF-16. That encoding could be ignored 
if you passed the real encoding used "UTF-16" at parser creation.
That how HTTP encoding information in header are used to override
the encoding= declaration is availble. That should work. Still
the internal format will be UTF-8 once parser.


Daniel Veillard      | Red Hat Network
veillard redhat com  | libxml GNOME XML XSLT toolkit | Rpmfind RPM search engine

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]