Don't work with UTF-8

[signmotion]

File aka
{
"name": "Блок стен 4x4"
}

don't parse with command line
json_reformat.exe -u < filename.json

"parse error: client cancelled parse via callback ..."

[falconindy]

Works for me, using yajl 2.0.3. Is there a byte order mark in a file that's throwing off yajl?

[signmotion]

Mark in a first '{'.
I found problem. The json-file created by Notepad++ in Windows Explorer. By default N++ use BOM in the text file. Solution: convert the file in UTF-8 without BOM (see menu).
Test files for yajl > http://www.mediafire.com/?9eahbxz9kx7mkk4

Thanks for your work!

[josephholsten]

Should this issue be renamed "Doesn't work with UTF-8-BOM"? While it is acceptable for legacy applications to act strangely with the BOM, modern software that is intended to work with UTF-8 needs to play nice.

[robdaemon]

Ran into this issue earlier and managed to work around it, but it's problematic that the JSON I was using was parseable in other parsers (namely the Ruby JSON gem) but not in Yajl.