Kent Dahl wrote:
> I'll be back with some local character _writing_ problems once I figure
> this one out. :-)
After some more research, I feel that XMLString::transcode is to blame.
So I've started rewriting it to use a XMLTranscoder gotten from the
TransService, as suggested in the FAQ, and things seem to be working
properly.
But now I'm stuck with no way of getting the local codepage encoding.
(Which I assumed that XMLStrin::transcode did automagically.)
So when I'm reading a file I'm doing this:
[XML file]--->(read in by SAX parser)--->[XMLCh]---...
...--->(transcoder back to ISO8859-1)--->[std::string]
And when I'm writing a file, I do (rougly) the opposite:
[std::string]--->(transcoder from ISO8859-1 to XML)-->[XMLCh]---...
...--->(Written to modified SAXPrint-example)--->[XML file]
(My local codepage is ISO8859-1, the files themselves usually are too.)
Q1: Is there any way to find out the encoding of the local codepage?
Or am I stuck with leaving it to the user of my code?
Q2: Do XMLString (and the underlying LCPTranscoder) handle local
characters (such as �, � and �) , and if so,
what could be the problem in the configuration?
--
<[ Kent Dahl ]>================<[ http://www.stud.ntnu.no/~kentda/ ]>
)____(stud.techn.;ind.�k.data)||(softwareDeveloper.at(Trustix))_(
/"Opinions expressed are mine and not those of my Employer, "\
( "the University, my girlfriend, stray cats, banana fruitflies, " )
\"nor the frontal lobe of my left cerebral hemisphere. "/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
