unable to parse. error 9 at line 17, colmn 44

Post a reply

Smilies
:D :) ;) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :!: :?: :idea: :arrow: :| :mrgreen: :geek: :ugeek:

BBCode is ON
[img] is OFF
[url] is OFF
Smilies are ON

Topic review
   

Expand view Topic review: unable to parse. error 9 at line 17, colmn 44

Re: unable to parse. error 9 at line 17, colmn 44

by forumadmin » March 24th, 2012, 6:46 pm

Hey, thank you! Encoding and internationalization is one of the major weak points in the current version. Thank you for your input and you time investigating the issue. I know that it has been some time, however, i can assure you that there is newer versions in the works. Proper encoding and at minimum, support, for these feeds is currently the top priority. It has been a long time coming, but new versions are indeed coming...

Re: unable to parse. error 9 at line 17, colmn 44

by Guest » February 27th, 2012, 7:33 am

W3C Feed Validation Service says:

Sorry
This feed does not validate.
'utf8' codec can't decode byte 0xe4 in position 792: invalid continuation byte (maybe a high-bit character?) [help]

In addition, interoperability with the widest range of feed readers could be improved by implementing the following recommendation.
line 17, column 43: title contains bad characters (8 occurrences)
<title>Tageskarte für Sonntag, den 04. M?rz 2012</title>

unable to parse. error 9 at line 17, colmn 44

by me- » February 27th, 2012, 7:29 am


Top