You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by bu...@apache.org on 2002/10/13 23:44:05 UTC
DO NOT REPLY [Bug 13584] New: -
Win32LCPTranscoder::transcode doesn't handle wcstombs errors
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13584>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13584
Win32LCPTranscoder::transcode doesn't handle wcstombs errors
Summary: Win32LCPTranscoder::transcode doesn't handle wcstombs
errors
Product: Xerces-C++
Version: 2.1.0
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: Normal
Priority: Other
Component: Utilities
AssignedTo: xerces-c-dev@xml.apache.org
ReportedBy: vminarik@ips-ag.cz
I have had troubles with converting XMLCh string into char* in MSVC6.
When converting a XMLCh string containing characters with codes greater than
255, I have got strings of correct lengths, but the content was correct up to
the first character >255. Win32LCPTranscoder::transcode will stop and the rest
of the string is not filled, if such a character occurs.
When debugging, I observed that LC_CTYPE should be set, so I used setlocale(
LC_CTYPE, "Czech_Czech.1250") and the problem was solved. But everybody is not
able to debug xercesc, so I think there should be some error tracking, if
transcode function fails.
Maybe also add a short notice about setlocale into xercesc documentation.
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org