fn-unparsed-text* failures

Please take into account that "fn-unparsed-text-lines-052" needs a correct implementation of XML canonicalization support in "assert-xml".

All the other 20 reported failures are not impacted so they should pass after the issues in "fn-unparsed-text*" are fixed.

Hi this are my observations on this bug report

Tests failing because of missing implementation of validation of utf-8 characters Bug 1073175:
fn-unparsed-text-038, fn-unparsed-text-039, fn-unparsed-text-available-037, fn-unparsed-text-available-038, fn-unparsed-text-lines-038, fn-unparsed-text-lines-039, fn-unparsed-text-lines-048

The function description specifies that utf-8 is the default form of read, The bugs I will list assume that the file it is being read as utf-16 without specifieng an encoding of utf-16 so they return invalid utf-8 characters. The question is if the function is supposed to make the encoding if the encoding is described in the xml tag? (example: <?xml version="1.0" encoding="utf-16"?>) or is it supposed to identify if a resource is encoded?
tests that assume utf-16: fn-unparsed-text-lines-040, fn-unparsed-text-lines-042, fn-unparsed-text-lines-047
tests that expect that the encoding of a file is varified: fn-unparsed-text-037, fn-unparsed-text-lines-037

This is the list of failing test-cases as of Zorba rev.11432:

- 9 in "fn-unparsed-text-lines" test set
- 5 in "fn-unparsed-text-available" test set
- 4 in "fn-unparsed-text" test set

Here are the test-cases failing:
"fn-unparsed-text-lines-038,fn-unparsed-text-lines-039,fn-unparsed-text-lines-042,fn-unparsed-text-lines-049,fn-unparsed-text-lines-050,fn-unparsed-text-lines-051,fn-unparsed-text-lines-052,fn-unparsed-text-lines-053,fn-unparsed-text-lines-054"
"fn-unparsed-text-available-023,fn-unparsed-text-available-024,fn-unparsed-text-available-036,fn-unparsed-text-available-037,fn-unparsed-text-available-038"
"fn-unparsed-text-038,fn-unparsed-text-039,fn-unparsed-text-042,fn-unparsed-text-050"