From: Bjorn Reese (breese@mail1.stofanet.dk)
Date: Sat Feb 24 2001 - 08:33:29 EST
James McCann wrote:
> into a project is not. libxml already knows how to translate from one
> encoding to another, what I am suggesting is to make this ability
> available to the user, who should not be forced to use or deal with UTF8.
> There is already a flexible means for transcoding in the library, why
> not extend the API to permit this in SAX callbacks? It would not break
As libxml uses UTF-8 internally, it seems to me that the only proper
solution to your suggestion would be to insert a wrapper layer for the
SAX functions. The purpose of this layer would be to convert the data
into to the application-requested encoding and then pass the data on
to the application through the "real" SAX interface.
I would like to support Craig's idea of putting this wrapper in your
application, since it is the one that is dependent on a specific
encoding. You can use the functions from libxml to do this conversion
for you (this is fairly easy; I have done something similar for UTF-8
to HTML).
---- Message from the list xml@rpmfind.net Archived at : http://xmlsoft.org/messages/ to unsubscribe: echo "unsubscribe xml" | mail majordomo@rpmfind.net
This archive was generated by hypermail 2b29 : Sat Feb 24 2001 - 08:47:00 EST