This bug should be fixed now. It was related to handling times in Infoboxes.
Sorry for the inconvenience!
max
On Sun, Jun 13, 2010 at 6:47 PM, Dimitris Kontokostas jimk...@gmail.com wrote:
The day you applied my patch, you also applied some more patches
(dataparser, wikiparser,...)
and when
First of all you don't have to apologize for any inconvinience...
you are all doing the best you can.
for now, i am not familiar with the code enough, so i just report :)
the problem was fixed, but some new came up...
now about 1% of the pages fail with new errors
and there is a compile error
I've looked a little closer here and this now looks like a bug in
Virtuoso's JSON encoder.
The server is sending unescaped newlines in JSON values/objects, eg.
^M instead of \n.
From:
http://tools.ietf.org/html/rfc4627#page-5
the only characters allowed unescaped in JSON are:
%x20-21 /
Hi Joe,
We shall look into this issue and report back on this mailing list ...
Best Regards
Hugh Williams
Professional Services
OpenLink Software
Web: http://www.openlinksw.com
Support: http://support.openlinksw.com
Forums: http://boards.openlinksw.com/support
Twitter:
Joe Presbrey wrote:
I've looked a little closer here and this now looks like a bug in
Virtuoso's JSON encoder.
The server is sending unescaped newlines in JSON values/objects, eg.
^M instead of \n.
From:
http://tools.ietf.org/html/rfc4627#page-5
the only characters allowed unescaped in
