encoding translation (was Re: [libxml++] Libxml++ 1.0.0 soon)

[Christophe de VIENNE <cdevienne alphacent com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Le Jeudi 6 Mars 2003 12:01, Murray Cumming Comneon com a écrit :
> > Another thing that was suggested and could be included in 1.0
> > since we won't
> > support the UTF-8 encoding is to give to constructors, or in
> > as a general
> > config in the library, which encoding should be put in the
> > std::string type,
> > instead of copying raw utf-8 systematicaly. libxml should
> > have the necessary
> > method to do the conversion.
>
> What libxml functions do you mean?
>

Since libxml has some encoding translation to do, I suspect it contains some 
functions which are able to translate UTF-8 to any encoding and vice versa.
I had a quick look to the API and found only UTF8Toisolat1 and isolat1ToUTF8. 
But a better search is needed I think.

> This sounds like a large change that probably doesn't belong in 1.0. People
> can do conversions outside of libxml++ if they need to - I suspect that
> it's rare.

If it's really rare, then indeed there is no need to include encoding 
translations inside libxml++. The thing is I'll probably need it for myself 
but if I'm the only one...
However the change seems not that large to me : the default behavior would 
remain the same as today, but instead of simply cast the xmlChar* to char* we 
would use translation functions and use the asked encoding (probably better, 
at least easier, as a global conf I guess).

Any comment welcome

Christophe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+ZzJpB+sU3TyOQjARAlArAJ9VQ/a7iYWfz10XosfQ9JSZyPIBsACfbFC5
wvne4piN90B0dGcu9A5yomU=
=Ufan
-----END PGP SIGNATURE-----