olikraus
> Is this something that could be pushed forwards to SimpleJSON ? Yes the same problem is here also: https://github.com/nbsdx/SimpleJSON/blob/master/json.hpp#L528 Indeed the conformance report already revealed the problem (section 3,...
The JSON standard defines this escape. Other escapes are handled but the \u is missing. It shouldn't be that complicated. Due to this problem almost sny parsing of none- English...
> And one more thing - correct me if I'm wrong: inside your JSON you're using single slash to escape the quotation marks and double slash to escape the unicode...
ok, closing this. Looks like my terminal was not on utf-8 mode. \u seems to be implemented.
Excause me for reopening this. I spent some time to do further research on this. Now I am sure that chaiscript does not work correctly here. The related code is...
Update: The problem is a little bit difficult to catch, because the normal chaiscript string parser already parses the slash-u escape: https://github.com/ChaiScript/ChaiScript/blob/develop/include/chaiscript/language/chaiscript_parser.hpp#L1266 This means, for any string which is constructed...
I have updated the initial post. It would be great if this could be fixed. I have created a pull request for this.
Came accross the same problem. The interessting thing is, that ``` if ( findResult == -1 ) ``` works, but (as mentioned above) ``` if ( findResult < 0 )...
So you added something like ``` def npos(string s) { return size_t(-1); } ``` Ok, indeed the following will print "true": ``` ./chai -c 'def npos(string s) { return size_t(-1);...
Current output for the 9pt font: ``` ./bdfconv -v -f 1 -M ../build/gb2312.map ../bdf/wenquanyi_9pt.bdf -o test.c -n test -d ../bdf/helvB12.bdf Glyph size problem: encoding=242/0xf2, width=4, height=10, requested position x=4, y=5...