majstang Posted January 21, 2011 Posted January 21, 2011 (edited) There seem to be a unicode error somewhere inside the recordings database. I can read everything from the RS API with both Chrome and IE8, but recordings.html[?utf8=] fails each and every time with both browsers. Chrome reports: This page contains the following errors: error on line 1 at column 35: Unsupported encoding uft-8 Below is a rendering of the page up to the first error. IE8 reports something similar. Tried to delete the whole database and start fresh but same error persists. Removing utf-8 from link works (/api/recordings.html), but this is of course no unicode but iso-8859-1. Bug? Edited January 21, 2011 by majstang
Moses Posted January 23, 2011 Posted January 23, 2011 Chrome and IE8 reports for me, that it doesn't support the encoding. Firefox displays the recordings perfectly in utf-8. Now, given that utf-8 should be the correct classification of utf-8 encoding, this seems like a shortcomming of IE8 and chrome. The only issue related to utf-8 xml, that I found by searching the web, is some talk about http header. But firefox displays that the RS should have send the correct header with it's reply (but maybe it shows the correct info it guessed and the header is indeed "wrong"?). Anyway, if you don't want to use firefox, I stumpled upon a useful info for you: just click "view source" in chrome, while it displays the error message and you'll see the full xml and for me it was correctly decoded utf-8...
majstang Posted January 23, 2011 Author Posted January 23, 2011 (edited) Yes, you're right. Firefox displays the XML, but it looks funny and very different from the format IE and Chrome reports (tested with /api/recordings.html (the only comparison I can do)). Seems Firefox is doing some kind of parsing and adds characters not found in the original source. Maybe that could explain why Firefox can read the utf-8 recordings.html and Chrome 'n IE8 not. Edited January 23, 2011 by majstang
majstang Posted March 18, 2011 Author Posted March 18, 2011 Lars, when you are at it checking if right encoding routines is used could you check this thing also? It probably doesnt work on IE8 and Chrome cuz the wrong encoding routine is used.
Lars_MQ Posted March 18, 2011 Posted March 18, 2011 <?xml version="1.0" encoding="UFT-8"?> oh my... wrong encoding. Should be UTF -> fixed.
majstang Posted March 18, 2011 Author Posted March 18, 2011 :blush: man...I did spend an hour at least on this and I didnt see this little slipped in error...despite Chrome gives me exact position and explanation where the problem is. Sometimes one can be so blind Well, lucky you are more sharped-eyed...thanks Lars
jhrdlicka Posted March 19, 2011 Posted March 19, 2011 Version 1.7.0.1 is still has problems in preview - timeline, tv program etc. When the double character at the end of the line is divided, the result is incorrectly interpreted, character before "...)" is (18:10 - 19:05 Vražedná čísla III (3) - (Numbers III) V místním muzeu lupič ukradne vzácný obraz jednoho z prvn�...) be (Numbers III) V místním muzeu lupič ukradne vzácný obraz jednoho z prvních impresionistů) josef
Recommended Posts