Hi Adam, Well, the Mac's native character encoding is no more non-standard than any other, it's just different! (And it has the moral advantage of having been defined before the Window's code page).
But to answer your question may require more information about what you're really trying to do, and what's not working. You can set the output encoding by using the setEncoding method on DOMWriter, for instance. Does that help at all? -jdb On 9/17/03 10:29 AM, "Adam Heinz" <[EMAIL PROTECTED]> wrote: > I'm getting some high-byte character trashing on serialization and my reading > has revealed that MacOS uses a somewhat non-standard encoding: x-mac-roman or > x-mac-latin1 (a variant of ISO-8859-1). I've been poring over the various > transcoding-related classes to see if I can change my "native" codepage > easily, so that XMLString::transcode will save me some extra work. For that > matter, how can I determine what Xerces thinks my native codepage is? Any > ideas? > > Adam Heinz > Development Consultant > > Exstream Software > 2424 Harrodsburg Road, Suite 200 > Lexington, KY 40503 > (317) 879-2831 > [EMAIL PROTECTED] > > connecting with the eGeneration > www.exstream.com > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
