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.
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.
Since I have a new hardware setup (now running AMD-64-bit), I cannot guarantee
that xerces-3.0 library works as expected - I need a matching xalan library
to run my own test scenarios. Using all the pre-compiled libraries
(SuSE-10.1) is just working perfectly, but I was able to run my projects
successfully with the bleeding edge of xerces/xalan some months ago, with my
old hardware setup.
Thanks,
Axel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
