I will try ASCII but i'm am 100% certain my issue was UTF8 vs UTF8 without BOM. Of Course that is not to say other formats don't work equally well, just that the OP2 does not read the UTF8 without BOM format correctly and results in parse errors.
Quote:
Originally Posted by vgi
to be on a safe side i would rather suggest people use plane ASCII (ANSI) mode for their files. I don't know for sure but considering standard C/C++ reads/writes ASCII text file by default I doubt there was an effort made to actually support a full UTF8 character set supported.
ASCII is a subset of UTF8 (UTF8 was designed for backward compatibility with ASCII) so it's possible all the chars in your file were just ASCII. If any true UTF8 characters will be in your file I guess it may or may not work.
Also, many editors have a default encoding, you should check what that is. Many editors make an attempt to auto-detect encoding and if they detect some UTF8 characters they may place BOM in the file (BOM is a sequence of bytes (EF BB BF) that allows the reader to identify the file as an UTF-8 file). Windows notepad should be safe to use as default encoding is ASCII unless it detects UTF8 chars, then it will place BOM in the file. It also puts /r/n for new line instead of just unix /n, but it think it should be safe.
|