Re: 3.2.4 release candidate
+1 > On 2022-10-10 18:58, Cantor, Scott wrote : > > I've posted a signed RC here: > https://dist.apache.org/repos/dist/dev/xerces/c/3/sources/ > > The web site update embedded in it includes a note on the front page that > the library lacks maintainers and should not be used for new projects. > > This is my +1 to release it. I can do the release next week so people have > all week to test and vote. > > -- Scott > > > > - > To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org > For additional commands, e-mail: c-dev-h...@xerces.apache.org > - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
Re: Xerces V3.2.3 release candidate - call for vote
+1 > Le 7 avr. 2020 à 17:00, Cantor, Scott a écrit : > > I have posted a release candidate [1] on my project site for evaluation > (signed with my key) and would like to call for a vote to release, ending > Friday. > > The issues fixed are at [2], they're largely minor and mostly build related. > > This is my +1. > > -- Scott > > [1] https://shibboleth.net/downloads/prerelease/ > [2] > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10510=12344135 > > > - > To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org > For additional commands, e-mail: c-dev-h...@xerces.apache.org > - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
Re: Call for vote on Xerces-C 3.2.2 release
This build (with make as indicated, plus -DCMAKE_INSTALL_PREFIX) is ok. However, after 'make install', there is a dangling libxerces-c.so symlink towards cygxerces-c-3-2.dll not installed (but present in build directory). Trying to use this installation fails with many many missing references (transcode etc.). I need to figure out what is wrong. > On 2018-09-13 at 00:06, Roger Leigh wrote: > > On 12/09/18 22:45, Denis Excoffier wrote: >>> On 2018-09-21 at 23:31, Roger Leigh wrote: >>> >>> Are you building with the autotools build or the cmake build? >> I don't know. I run ./configure --disable-network --enable-transcoder-iconv. >> No cmake around (although the cmake and libcurl-devel packages are present). > > The equivalent for testing would be: > > mkdir build > cd build > cmake -Dnetwork=OFF -Dtranscoder=iconv /path/to/xerces/source > make > ctest > > > Regards, > Roger > > - > To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org > For additional commands, e-mail: c-dev-h...@xerces.apache.org > - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
Re: Call for vote on Xerces-C 3.2.2 release
> On 2018-09-21 at 23:31, Roger Leigh wrote: > > Are you building with the autotools build or the cmake build? I don't know. I run ./configure --disable-network --enable-transcoder-iconv. No cmake around (although the cmake and libcurl-devel packages are present). Regards, Denis Excoffier. - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
Re: Call for vote on Xerces-C 3.2.2 release
Forgot to mention that i also tried to build on Linux 32bits (Debian 7), solaris 2.10 and darwin 17.7.0, and succeeded with no problem. > On 2018-09-12 at 23:21, Denis Excoffier wrote: > > Hello, > > Don't know whether it's wise or appropriate to vote +1 and also report an > error (minor): on a clean and up-to-date cygwin (windows 10, x86_64, > pre-2.11.2), i had to remove the two lines: > template class ArrayJanitor; > template class ArrayJanitor; > in > src/xercesc/util/JanitorExports.cpp > to be able to build successfully, otherwise, i don't know why, i get: > xercesc/util/JanitorExports.cpp:22:16: error: duplicate explicit > instantiation of 'class xercesc_3_2::ArrayJanitor' > [-fpermissive] > template class ArrayJanitor; > ^ > xercesc/util/JanitorExports.cpp:23:16: error: duplicate explicit > instantiation of 'class xercesc_3_2::ArrayJanitor' [-fpermissive] > template class ArrayJanitor; > ^~~ > Regards, > > Denis Excoffier. > >> On 2018-09-12 at 20:05, Cantor, Scott wrote: >> >> I would like to call for a vote to release the RC3 artifact built from svn >> revision 1840539 as V3.2.2. It's published and signed at [1]. >> >> The release notes are at [2]. >> >> The issues are build related for the most part, nothing substantive. >> >> I'll hold the vote open through the weekend, as next week is the soonest I >> can do the upload of a release. >> >> This is my +1. >> >> -- Scott >> >> [1] https://dist.apache.org/repos/dist/dev/xerces/c/3/sources/ >> <https://dist.apache.org/repos/dist/dev/xerces/c/3/sources/> >> [2] >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10510=12342890 >> >> <https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10510=12342890> >> >> - >> To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org >> <mailto:c-dev-unsubscr...@xerces.apache.org> >> For additional commands, e-mail: c-dev-h...@xerces.apache.org >> <mailto:c-dev-h...@xerces.apache.org> >> >
Re: Call for vote on Xerces-C 3.2.2 release
Hello, Don't know whether it's wise or appropriate to vote +1 and also report an error (minor): on a clean and up-to-date cygwin (windows 10, x86_64, pre-2.11.2), i had to remove the two lines: template class ArrayJanitor; template class ArrayJanitor; in src/xercesc/util/JanitorExports.cpp to be able to build successfully, otherwise, i don't know why, i get: xercesc/util/JanitorExports.cpp:22:16: error: duplicate explicit instantiation of 'class xercesc_3_2::ArrayJanitor' [-fpermissive] template class ArrayJanitor; ^ xercesc/util/JanitorExports.cpp:23:16: error: duplicate explicit instantiation of 'class xercesc_3_2::ArrayJanitor' [-fpermissive] template class ArrayJanitor; ^~~ Regards, Denis Excoffier. > On 2018-09-12 at 20:05, Cantor, Scott wrote: > > I would like to call for a vote to release the RC3 artifact built from svn > revision 1840539 as V3.2.2. It's published and signed at [1]. > > The release notes are at [2]. > > The issues are build related for the most part, nothing substantive. > > I'll hold the vote open through the weekend, as next week is the soonest I > can do the upload of a release. > > This is my +1. > > -- Scott > > [1] https://dist.apache.org/repos/dist/dev/xerces/c/3/sources/ > [2] > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10510=12342890 > > - > To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org > For additional commands, e-mail: c-dev-h...@xerces.apache.org >
Re: Call for vote
> On 2016-06-22 18:31, Cantor, Scott wrote: > > I've done a bit of minor cleanup (removing .svn detritus) and posted new > artifacts with signatures: > > https://dist.apache.org/repos/dist/dev/xerces/c/3/sources/ Couldn't you find a more recent config.guess? See for example the one in gcc-6.1.0.tar.bz2, dated 2016-01-01. > > I would like to call for a vote by the PMC to release V3.1.4. > > This is my +1 +1 anyway > Denis Excoffier. - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
small typo in Xerces-C++ 3.1.2
Dear all, Please someone to improve xerces-3.1.2 with this typo correction: diff -uNr xerces-c-3.1.2o/src/xercesc/util/XMLUni.cpp xerces-c-3.1.2p/src/xercesc/util/XMLUni.cpp --- xerces-c-3.1.2o/src/xercesc/util/XMLUni.cpp 2015-03-09 23:45:27.0 +0100 +++ xerces-c-3.1.2p/src/xercesc/util/XMLUni.cpp 2015-04-11 16:59:32.0 +0200 @@ -337,7 +337,7 @@ , chForwardSlash, chLatin_a, chLatin_p, chLatin_a, chLatin_c , chLatin_h, chLatin_e, chPeriod, chLatin_o, chLatin_r, chLatin_g , chForwardSlash, chLatin_x, chLatin_m, chLatin_l, chForwardSlash -, chLatin_U, chLatin_k, chLatin_n, chLatin_o, chLatin_w, chLatin_n +, chLatin_U, chLatin_n, chLatin_k, chLatin_n, chLatin_o, chLatin_w, chLatin_n , chLatin_N, chLatin_S, chNull }; Thanks. Denis Excoffier. - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
Re: Final Xerces-C 3.1.2 RC posted
On 2015-03-18 16:16, Cantor, Scott wrote: A hopefully-final distribution set is now posted [1]. No code changes have occurred since the second beta posting last week, but various distribution tweaks and changes to the doc/ content for generation of the web site have been made. Thanks. When i compare the first RC and the second RC (current), i observe some improvement in the doc/ and samples/ folders, but also that - config.guess has timestamp='2013-05-16' (RC2) instead of timestamp='2014-11-04' (RC1) - config.sub has timestamp='2013-04-24' (RC2) instead of timestamp='2014-12-03' (RC1) Just in case it might not be under control. Regards, Denis Excoffier. - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
Re: Xerces 3.1.2 Release Candidate available
On 2015-03-10 15:37, Cantor, Scott wrote: I have prepared a hopefully-final distribution for testing [1] as a release candidate. The filenames are identical to the eventual release. I fixed the distribution last night to include all missing content that was present in the 3.1.1 distribution, including the HTML site and API docs. If anything is still missing, please let us know. Not missing ones i guess but extra ones. I suppose the following files should not be present in the gz and bz2 distributions: m4/._libtool.m4 m4/._ltoptions.m4 m4/._ltsugar.m4 m4/._lt~obsolete.m4 The zip distribution does not include them. By the way, could we please also get a xerces-c-3.1.2.tar.xz distribution, in addition to or instead the bz2 distribution? Regards, Denis Excoffier. - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
Re: Xerces-C 3.1.2 beta-3 available, call for testing
On 2015-03-06 16:34, Cantor, Scott wrote: A third beta with the missing test file added is now available [1]. The test output now matches the output checked in as a baseline. -- Scott [1] https://people.apache.org/~scantor/ Would it be feasible to also include the documentation (the doc folder, like under xerces-c-3.1.1)? If not (because for example it breaks 'make install'), please include a doc.tar.xz file, in order that we can have the documentation handy. Thanks in advance, Denis Excoffier. - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
xerces-c-3.1.2b1
Hi, Compiled successfully and somewhat tested on Cygwin 32 bits (1.7.35), Solaris 10, Linux 32 bits Ubuntu, and Darwin Yosemite (10.10.2). It seems that you forgot the following one: diff -uNr xerces-c-3.1.1o/src/xercesc/util/XMLString.cpp xerces-c-3.1.1p/src/xercesc/util/XMLString.cpp --- xerces-c-3.1.1o/src/xercesc/util/XMLString.cpp 2010-01-20 09:44:38.0 +0059 +++ xerces-c-3.1.1p/src/xercesc/util/XMLString.cpp 2012-10-08 16:46:32.743150300 +0159 @@ -802,7 +802,7 @@ { chDigit_0, chDigit_1, chDigit_2, chDigit_3, chDigit_4, chDigit_5 , chDigit_6, chDigit_7, chDigit_8, chDigit_9, chLatin_A, chLatin_B -, chLatin_C, chLatin_D, chLatin_e, chLatin_F +, chLatin_C, chLatin_D, chLatin_E, chLatin_F }; if (!maxChars) @@ -893,7 +893,7 @@ { chDigit_0, chDigit_1, chDigit_2, chDigit_3, chDigit_4, chDigit_5 , chDigit_6, chDigit_7, chDigit_8, chDigit_9, chLatin_A, chLatin_B -, chLatin_C, chLatin_D, chLatin_e, chLatin_F +, chLatin_C, chLatin_D, chLatin_E, chLatin_F }; if (!maxChars) Regards, Denis Excoffier. - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
Re: consistent error messages (and more)
Hi, Glad for being useful to someone. Thank you. My patch dated 2012-08-21 (see in the archives of this list) handles NULs characters gently, instead of doing like if an EOF had been met. If you were interested, you'll also be interested that NULs found in system identifiers be reported by a specific error message: invalid character 0x{0} in system id similar to the one you get in public identifiers: invalid character 0x{0} in public id Here (attached) is a patch for this (3.1.1). You might also find useful my patch dated 2012-09-03 about empty public and system identifiers. I've also a patch to introduce set/getCreateProcessingInstructionNodes (similar to set/getCreateCommentNodes), and to introduce set/getCreateCDATASectionNodes (similar to set/getCreateEntityReferenceNodes) if you are interested. And a little patch to avoid incrementing fCurLine when a #xD (with no #xA) is found within an input file. Hoping all this (functionality if not patches) will be introduced in the next formal issue (3.2.0?). Regards, Denis Excoffier. On Mon, Oct 08, 2012 at 05:46:33PM +0200, Alberto Massari wrote: Thanks for reporting this, it is fixed in SVN now. Alberto Il 08/10/2012 17:19, Denis Excoffier ha scritto: Hi, If you want consistent error messages, not like invalid character 0x1e and invalid character 0x1F, you will want to apply the patch included (either Xerces-C-3.1.1 or trunk) Regards, Denis Excoffier. - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org diff -uNr xerces-c-3.1.1o/src/xercesc/NLS/EN_US/XMLErrList_EN_US.Xml xerces-c-3.1.1p/src/xercesc/NLS/EN_US/XMLErrList_EN_US.Xml --- xerces-c-3.1.1o/src/xercesc/NLS/EN_US/XMLErrList_EN_US.Xml 2010-04-11 15:04:35.0 +0159 +++ xerces-c-3.1.1p/src/xercesc/NLS/EN_US/XMLErrList_EN_US.Xml 2012-10-09 16:35:10.554189500 +0159 @@ -343,6 +343,7 @@ Message Id=XIncludeDisallowedChild Text=element '{0}' is not allowed as a child of include element/ Message Id=XIncludeConflictingNotation Text=included notation '{0}' conflicts with notation already defined/ Message Id=XIncludeConflictingEntity Text=included entity '{0}' conflicts with entity already defined/ +Message Id=InvalidSystemIdChar Text=invalid character 0x{0} in system id/ /FatalError /MsgDomain MsgDomain Domain=http://apache.org/xml/messages/XMLValidity; diff -uNr xerces-c-3.1.1o/src/xercesc/framework/XMLErrorCodes.hpp xerces-c-3.1.1p/src/xercesc/framework/XMLErrorCodes.hpp --- xerces-c-3.1.1o/src/xercesc/framework/XMLErrorCodes.hpp 2009-08-10 15:33:24.0 +0159 +++ xerces-c-3.1.1p/src/xercesc/framework/XMLErrorCodes.hpp 2012-10-09 16:37:58.427040700 +0159 @@ -301,7 +301,8 @@ , XIncludeDisallowedChild= 284 , XIncludeConflictingNotation= 285 , XIncludeConflictingEntity = 286 - , F_HighBounds = 287 + , InvalidSystemIdChar= 287 + , F_HighBounds = 288 }; static bool isFatal(const XMLErrs::Codes toCheck) diff -uNr xerces-c-3.1.1o/src/xercesc/util/MsgLoaders/ICU/resources/root.txt xerces-c-3.1.1p/src/xercesc/util/MsgLoaders/ICU/resources/root.txt --- xerces-c-3.1.1o/src/xercesc/util/MsgLoaders/ICU/resources/root.txt 2009-11-18 12:28:05.0 +0059 +++ xerces-c-3.1.1p/src/xercesc/util/MsgLoaders/ICU/resources/root.txt 2012-10-09 16:35:24.507135900 +0159 @@ -288,6 +288,7 @@ element '{0}' is not allowed as a child of include element , included notation '{0}' conflicts with notation already defined , included entity '{0}' conflicts with entity already defined , + invalid character 0x{0} in system id , F_ End , } diff -uNr xerces-c-3.1.1o/src/xercesc/util/MsgLoaders/InMemory/XercesMessages_en_US.hpp xerces-c-3.1.1p/src/xercesc/util/MsgLoaders/InMemory/XercesMessages_en_US.hpp --- xerces-c-3.1.1o/src/xercesc/util/MsgLoaders/InMemory/XercesMessages_en_US.hpp 2009-11-18 12:28:05.0 +0059 +++ xerces-c-3.1.1p/src/xercesc/util/MsgLoaders/InMemory/XercesMessages_en_US.hpp 2012-10-09 17:44:26.172871900 +0159 @@ -575,6 +575,8 @@ 0x0069,0x0074,0x0068,0x0020,0x006E,0x006F,0x0074,0x0061,0x0074,0x0069,0x006F,0x006E,0x0020,0x0061,0x006C,0x0072,0x0065,0x0061,0x0064,0x0079,0x0020,0x0064,0x0065,0x0066,0x0069,0x006E,0x0065,0x0064,0x00 } , { 0x0069,0x006E,0x0063,0x006C,0x0075,0x0064,0x0065,0x0064,0x0020,0x0065,0x006E,0x0074,0x0069,0x0074,0x0079,0x0020,0x0027,0x007B,0x0030,0x007D,0x0027,0x0020,0x0063,0x006F,0x006E,0x0066,0x006C,0x0069,0x0063,0x0074,0x0073,0x0020,0x0077,0x0069,0x0074, 0x0068,0x0020,0x0065,0x006E,0x0074,0x0069,0x0074,0x0079,0x0020,0x0061,0x006C
consistent error messages (and more)
Hi, If you want consistent error messages, not like invalid character 0x1e and invalid character 0x1F, you will want to apply the patch included (either Xerces-C-3.1.1 or trunk) Regards, Denis Excoffier. diff -uNr xerces-c-3.1.1o/src/xercesc/util/XMLString.cpp xerces-c-3.1.1p/src/xercesc/util/XMLString.cpp --- xerces-c-3.1.1o/src/xercesc/util/XMLString.cpp 2010-01-20 09:44:38.0 +0059 +++ xerces-c-3.1.1p/src/xercesc/util/XMLString.cpp 2012-10-08 16:46:32.743150300 +0159 @@ -802,7 +802,7 @@ { chDigit_0, chDigit_1, chDigit_2, chDigit_3, chDigit_4, chDigit_5 , chDigit_6, chDigit_7, chDigit_8, chDigit_9, chLatin_A, chLatin_B -, chLatin_C, chLatin_D, chLatin_e, chLatin_F +, chLatin_C, chLatin_D, chLatin_E, chLatin_F }; if (!maxChars) @@ -893,7 +893,7 @@ { chDigit_0, chDigit_1, chDigit_2, chDigit_3, chDigit_4, chDigit_5 , chDigit_6, chDigit_7, chDigit_8, chDigit_9, chLatin_A, chLatin_B -, chLatin_C, chLatin_D, chLatin_e, chLatin_F +, chLatin_C, chLatin_D, chLatin_E, chLatin_F }; if (!maxChars) - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
Re: [jira] Updated: (XERCESC-1701) Xerces-C++ Allows junk after root element (null characters)
Still a problem in 3.1.1. Patch included. Regards, Denis Excoffier. On Tue, Nov 03, 2009 at 09:36:00AM +, Boris Kolpackov (JIRA) wrote: [ https://issues.apache.org/jira/browse/XERCESC-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boris Kolpackov updated XERCESC-1701: - Affects Version/s: (was: 2.7.0) 3.0.1 Still a problem in 3.0.1. Xerces-C++ Allows junk after root element (null characters) --- Key: XERCESC-1701 URL: https://issues.apache.org/jira/browse/XERCESC-1701 Project: Xerces-C++ Issue Type: Bug Components: Non-Validating Parser Affects Versions: 3.0.1 Environment: WindowsXP Reporter: Maarten Koskamp Attachments: sample.xml, version.incl Xerces-C allows a sequence of null characters after the document root at the end of the xml instance. XML Specifiction states that only white-space is allowed after the document root. See attached sample for details. Info about the affected version of the parser is also added as an attachment to this issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org diff -uNr xerces-c-3.1.1o/src/xercesc/internal/DGXMLScanner.cpp xerces-c-3.1.1p/src/xercesc/internal/DGXMLScanner.cpp --- xerces-c-3.1.1o/src/xercesc/internal/DGXMLScanner.cpp 2009-11-05 14:21:03.0 +0059 +++ xerces-c-3.1.1p/src/xercesc/internal/DGXMLScanner.cpp 2012-08-06 10:45:26.765625000 +0159 @@ -1407,7 +1407,7 @@ // It was some special case character so do all of the checks and // deal with it. -if (!nextCh) +if (!nextCh fReaderMgr.atEOF()) ThrowXMLwithMemMgr(UnexpectedEOFException, XMLExcepts::Gen_UnexpectedEOF, fMemoryManager); if (nextCh == chForwardSlash) @@ -1858,7 +1858,7 @@ // It was some special case character so do all of the checks and // deal with it. -if (!nextCh) +if (!nextCh fReaderMgr.atEOF()) ThrowXMLwithMemMgr(UnexpectedEOFException, XMLExcepts::Gen_UnexpectedEOF, fMemoryManager); if (nextCh == chForwardSlash) @@ -2812,7 +2812,7 @@ { nextCh = fReaderMgr.getNextChar(); -if (!nextCh) +if (!nextCh fReaderMgr.atEOF()) ThrowXMLwithMemMgr(UnexpectedEOFException, XMLExcepts::Gen_UnexpectedEOF, fMemoryManager); // Check for our ending quote in the same entity @@ -3021,7 +3021,7 @@ const XMLCh nextCh = fReaderMgr.getNextChar(); // Watch for unexpected end of file -if (!nextCh) +if (!nextCh fReaderMgr.atEOF()) { emitError(XMLErrs::UnterminatedCDATASection); ThrowXMLwithMemMgr(UnexpectedEOFException, XMLExcepts::Gen_UnexpectedEOF, fMemoryManager); diff -uNr xerces-c-3.1.1o/src/xercesc/internal/IGXMLScanner.cpp xerces-c-3.1.1p/src/xercesc/internal/IGXMLScanner.cpp --- xerces-c-3.1.1o/src/xercesc/internal/IGXMLScanner.cpp 2009-11-20 14:43:50.0 +0059 +++ xerces-c-3.1.1p/src/xercesc/internal/IGXMLScanner.cpp 2012-08-06 10:46:25.703125000 +0159 @@ -762,7 +762,7 @@ // It was some special case character so do all of the checks and // deal with it. -if (!nextCh) +if (!nextCh fReaderMgr.atEOF()) ThrowXMLwithMemMgr(UnexpectedEOFException, XMLExcepts::Gen_UnexpectedEOF, fMemoryManager); if (nextCh == chForwardSlash) @@ -1910,7 +1910,7 @@ // It was some special case character so do all of the checks and // deal with it. -if (!nextCh) +if (!nextCh fReaderMgr.atEOF()) ThrowXMLwithMemMgr(UnexpectedEOFException, XMLExcepts::Gen_UnexpectedEOF, fMemoryManager); if (nextCh == chForwardSlash) diff -uNr xerces-c-3.1.1o/src/xercesc/internal/IGXMLScanner2.cpp xerces-c-3.1.1p/src/xercesc/internal/IGXMLScanner2.cpp --- xerces-c-3.1.1o/src/xercesc/internal/IGXMLScanner2.cpp 2010-03-19 15:29:23.0 +0059 +++ xerces-c-3.1.1p/src/xercesc/internal/IGXMLScanner2.cpp 2012-08-06 10:47:39.46875 +0159 @@ -2271,7 +2271,7 @@ // Its got to at least be a valid XML character if (!fReaderMgr.getCurrentReader()-isXMLChar(nextCh)) { -if (nextCh == 0) +if (nextCh == 0 fReaderMgr.atEOF