Axel Weiß wrote:
David Bertoni wrote:
It looks like the .xlf file might be corrupt and Xerces-C is complaining
during the parse. Can you look at XalanMsg_en_US.xlf and see if there's
anything on line 20 that looks suspicious?
I just built the sources from SVN recently and did not have any problems.
Hi Dave,
sorry for the delay. I did some random tests now (e.g. DOMCount from the
xerces samples) and found something strange:
XalanMsg_en_US.xlf, line 21: <xliff version="1.1">
xliff.dtd, line 43: version CDATA #FIXED "1.0"
produces a version mismatch error (at least when parsed with xercesc-2.7,
which shows a lot of errors following this one). Xerces-3.0 complains only
'fatal error in xml file', without a reason.
That seems to me like there's a bug in the 3.0 branch.
From the reading, XalanMsg_en_US.xlf cannot be validated by xliff.dtd -
otherwise the validator is broken. I have double-checked that I have the
current svn checkout of xalan (Revision 431957, without changes since some
days). Dave, can you check whether your (funcional) files show this version
conflict? I guess, there's only some stupid not-yet-checked-in issue.
It may be that something has changed in Xerces-C in the 3.0 branch that
affects validation. I suspect that we have never enabled validation for
the message file.
You could try either changing the version attribute in the message file, or
ensuring that all validation is turned off in
xml-xalan/c/src/xalanc/Util/MsgCreator/MsgCreator.cpp
This might also be a bug in Xerces-C 3.0. In general, Xalan-C doesn't
start testing with a new version Xerces-C until there's a concrete date for
the release. I don't real feel that the 3.0 branch is stable enough for
that yet.
Note that, as a workaround, you can produce the message library with a
version of the MsgCreator utility that was compiled with Xerces-C 2.7.
Then, you can simply use that library and the resulting intermediate files
to build Xalan-C with Xerces-C 3.0.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
