<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class="">[CC: to the mailing list in case other people run into the same problem]</div><br class=""><blockquote type="cite" class="">On 21 Feb 2016, at 21:38, Daniel Renau <<a href="mailto:alphak87@gmail.com" class="">alphak87@gmail.com</a>> wrote:<br class=""><br class="">Done!<br class=""><br class=""></blockquote><img apple-inline="yes" id="22B1CFD7-7A66-4742-872C-8FFBD51B4D2E" height="102" width="586" apple-width="yes" apple-height="yes" src="cid:ii_153058d82bd19920" class=""><blockquote type="cite" class=""><br class="">I erased the 4 first hex pairs... and it works well now :)<br class=""></blockquote><div class=""><br class=""></div><div class=""><br class=""></div><div class="">EF BB BF ist the byte-order mark in UTF-8 … the root of all evil! BOMs are chronically inserted by Windows editor programs (but by hardly any other software), and they're quite hard to get rid off.</div><div class=""><br class=""></div><div class="">While CWB should really understand and skip the BOM at the start of a UTF-8 file, once you cat together several such file (e.g. feeding them to CWB from stdin), you produce illegal input with BOMs littered throughout the text.</div><div class=""><br class=""></div><div class="">Best,</div><div class="">Stefan</div></body></html>