[
https://issues.apache.org/jira/browse/XERCESC-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16090931#comment-16090931
]
Scott Cantor commented on XERCESC-2038:
---------------------------------------
r1802231
Added fix to check for null return and throw exception if transcoder isn't
available.
I don't believe the last issue is accurate, it's populating the input parameter
memory manager into a member variable, that's what fMemoryManager is, not a
global.
I can't really speak for #1 but with all the various fixes to this stuff across
versions, I'd rather deal with that in a separate bug if it still fails.
> Problems with TranscodeToStr
> ----------------------------
>
> Key: XERCESC-2038
> URL: https://issues.apache.org/jira/browse/XERCESC-2038
> Project: Xerces-C++
> Issue Type: Bug
> Components: DOM
> Affects Versions: 3.1.1, 3.1.2, 3.1.3, 3.1.4
> Environment: bash-4.1$ uname -a
> Linux sadbprodcompile1 2.6.32-431.23.3.el6.x86_64 #1 SMP Wed Jul 16 06:12:23
> EDT 2014 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Old Account That Somhow Should Be Erased
> Assignee: Scott Cantor
> Fix For: 3.2.0
>
>
> This is actually 3 reports in one (but hey, sue me;-)
> 1. TranscodeToStr fails of the XMLCh-string contains just one character when
> encoding is "WCHAR_T" or "UTF-32" (i.e. types larger than XMLCh) and you get
> "invalid-multibyte-character"
> 2. In the constructor of TranscodeToStr, the result (or 'failReason') from
> makeNewTranscoderFrom is never checked and if it fails the
> ::transcode-function dumps miserably. An exception would be preffered
> 3. It is not documented why the parameter 'manager' is not used (in the call
> to makeNewTranscoderFrom instead and not to the ::transcode-function) but the
> (global) fMemoryManager is used instead
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
