PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3505 *** shadow/3505 Fri Sep 7 12:32:57 2001 --- shadow/3505.tmp.373 Fri Sep 7 12:32:57 2001 *************** *** 0 **** --- 1,24 ---- + +============================================================================+ + | DOMString::transcode does not always detect wcstombs errors | + +----------------------------------------------------------------------------+ + | Bug #: 3505 Product: Xerces-C++ | + | Status: NEW Version: 1.5.1 | + | Resolution: Platform: Sun | + | Severity: Minor OS/Version: Solaris | + | Priority: Other Component: DOM | + +----------------------------------------------------------------------------+ + | Assigned To: [EMAIL PROTECTED] | + | Reported By: [EMAIL PROTECTED] | + | CC list: Cc: | + +----------------------------------------------------------------------------+ + | URL: | + +============================================================================+ + | DESCRIPTION | + On Win32 and Solaris, if any character except the first cannot be converted by + wcstombs, DOMString::transcode will return the string buffer as returned by + wcstombs (properly NUL terminated, but with invalid characters starting at the + first character which could not be translated). On HP-UX, the same scenario + returns a blank string. The difference between platforms is that wcstombs does + not seem to detect errors when merely computing the target buffer size (ie + wcstombs(NULL,wchar_t *,0)) on Win32 and Solaris. The error is returned when + actually converting the string. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
