Files starting with <U+FEFF> don't get processed

[GoogleCodeExporter]

Some files from window systems will start with <U+FEFF>. This causes the 
file not to process. In most text editors you will not even see this, so 
the mistake is made very easely.
Is it possible to check for this at the beginning of the file, and then 
igonore it? This way these files do not have to be edited by hand

Original issue reported on code.google.com by joran.wo...@gmail.com on 28 Oct 2008 at 2:41

Attachments:

• ZA.zip

[GoogleCodeExporter]

It'd be better, probably, to just run the file directly from wow (or use a text 
editor that doesn't insert stuff).

At any rate, this should only affect the first line now; please reopen another 
issue (or this one) if you have a 
problem past the first line.

Original comment by gianmerlino@gmail.com on 23 Jan 2009 at 7:20

• Changed state: WontFix

[GoogleCodeExporter]

Changed my mind, this is probably something that should be fixed. Priority kind 
of low, though, for now.

Original comment by gianmerlino@gmail.com on 30 Jan 2009 at 6:09

• Changed state: Accepted

[GoogleCodeExporter]

<U+FEFF> is the BOM for UTF-16 encoded files. It's not a surprise that stasis 
doesn't 
handle this kind of files ;)

The raw WoWCombatLog.txt is encoded with UTF-8, without the byte order mark.

But, your file (ZA.log) is in utf-8 /with/ the BOM (EF BB BF). Most text 
editors have 
options to save files with or without that mark.

Stasis can safely ignore the first three bytes 0xEF 0xBB 0xBF if present.

Original comment by hati.elune@gmail.com on 6 Feb 2009 at 12:11