3 of the failing test-cases are correct (fn-unparsed-text-lines-039, 
fn-unparsed-text-039, fn-unparsed-text-available-038).

Here is why:
The 3 test-cases use fn/unparsed-text/non-xml-character.txt that contains BOM 
followed by NULL character.

Here is the catch: NULL is not a valid XML 1.0 nor XML 1.1 character.

The F&O spec mentions as an error condition for all 3 unparsed-text* functions:

"A dynamic error is raised [err:FOUT1190]
if the resulting characters are not permitted XML characters."
Your team Zorba Coders is subscribed to branch lp:zorba.

Mailing list: https://launchpad.net/~zorba-coders
Post to     : zorba-coders@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zorba-coders
More help   : https://help.launchpad.net/ListHelp

Reply via email to