Is there a better way than printf? It seems that on MVS-USS, printf can
handle POD objects but Linux cannot. I found one way to get this to work
on Linux was to allocate a character string for the size of the
CharVectorType that TranscodeToLocalPage constructs, and then strncpy the
CharVectorType into the character string , and then use the resultant
string for printf. But, somehow this seems like the long way , as if there
should be a function call that just goes and 'printf's CharVectorTypes. It
also feels as if it may be defeating the purpose of unicode.
??
Thanks,
Suzanne
----- Forwarded by Suzanne Dirkers/Raleigh/IBM on 05/08/2003 12:01 PM -----
Suzanne
Dirkers/Raleigh/I To:
xalan-c-users@xml.apache.org
[EMAIL PROTECTED] cc:
Subject:
TranscodeToLocalCodePage
05/08/2003 08:31
AM
Hi,
I"m having a problem whereby an Exception message coming back on
Linux is showing up in weird characters. The same message, when
the same code is run on MVS-USS does print out the exception in a readable
format. I suspect that TranscodeToLocalCodePage(e.getMessage(),
m_errorMessage, true) is 'translating' something it doesn't need to
translate when you are already in ASCII to begin with? But if I don't use
TranscodeToLocalCodePage at all and just try to print out e.getMessage()
with a printf, that is also gibberish, just different gibberish. My
question is, if you are already on an ASCII system to begin with, do you
not need to use 'TranscodeToLocalCodePage'? And how then do you print out
an Exception message?
By the way, this is happening at RH 8 Linux using Xalan 1.4, Xerces
2.1, ICU 2.2.
Thanks,
Suzanne
