UTF-8 BOM is not ignored in plain text or TSV test data files

[GoogleCodeExporter]

Some tools (especially on Windows and particularly Notepad) add byte order
mark (BOM) into the beginning of UTF-8 files. That causes problems with
plain text and TSV test data formats if there is a table header on the
first row because we check does the row start with '*' and in this case it
doesn't.

Although there is a simple workaround (don't have table headers on the
first row) this bug is pretty nasty and it took me some time to understand
what happened when I first encountered it. Luckily the fix is also pretty
simple, we just need to ignore the possible UTF-8 BOM on the beginning of
the first row.

For more info about BOMs see:
http://en.wikipedia.org/wiki/Byte_order_mark

Original issue reported on code.google.com by pekka.klarck on 10 Apr 2010 at 10:46

[GoogleCodeExporter]

Fixed in r2923.

Original comment by pekka.klarck on 12 Apr 2010 at 10:47

• Changed state: Done

[GoogleCodeExporter]

This issue is included in RF 2.5 alpha 1.

Original comment by jussi.ao...@gmail.com on 6 May 2010 at 1:35

• Added labels: alpha1