Comment 3 for bug 1123835

Revision history for this message
Juan Zacarias (juan457) wrote : Re: FOTS: fn-unparsed-text* failures (at least 21 failures)

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