It looks like it supports it using the string "UCS2" (no dash). Are you
talking about transcoding _from_ UCS-2, or transcoding _to_ UCS-2? It just
uses the UTF-16 transcoder, which shouldn't be a problem, as as long as
your input documents have no surrogates.
Dave
"Mark A Russell"
<mark_russell@csgsy To: "Xerces C++ Mailing List"
<[EMAIL PROTECTED]>
stems.com> cc: (bcc: David N
Bertoni/CAM/Lotus)
Subject: supported encodings
06/28/2001 04:23 PM
Please respond to
xerces-c-dev
Any idea what encodings the transcoding service supports? More
specifically
does it support UCS-2?
I know it supports UCS4, UTF16, and UTF8.
Mark A Russell
NextGen Software Engineer
CSG Systems, Inc.
E-Mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
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]
- supported encodings Mark A Russell
- RE: supported encodings Peter Fein
- Re: supported encodings peiyongz
- RE: supported encodings David_N_Bertoni
- RE: supported encodings Carl_Erhorn
