Forum Moderators: open
This is frustrating :-)
Is it possible to fix that?
Thank you
Frédéric
Thank you for your quick reply (as usual :-) )
Don't you think you loose the coming back of a large audience with this encoding problem?
Quick links to RSS validator :
It has been mentioned by 2 people in 4 years. The rss feed does about 50k unique's a day. I'd call that - a liveable problem. (compared to the solution which would involve about 200-300 hrs of programming. which is effectively a nonfixable error at this point)
> Also affects anyone based on PHP Magpie or Perl XML::RSS.
I use perl rss to read it about 100 times a day. I have never seen a error due to char encoding. We are read by many people who use PHP Magpie - encoding is not an issue that causes any fatal errors.
We are read by many people who use PHP Magpie - encoding is not an issue that causes any fatal errors.
From my feed reader:
MagpieRSS: Failed to parse RSS file. (not well-formed (invalid token) at line 103, column 176))
And using XML::RSS:
not well-formed (invalid token) at line 103, column 176, byte 5422 at /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/XML/Parser.pm line 185
Sean
right said fred - but it's not that simple said jed. Also known as: fix it for one person, and break it for another.
The real issue here is the system used for encoding. Ultimately, we should move 100% to unicode. Unfortunately, many of todays browsers don't play nice in that arena. There is not a piece of forum software on the net that does not experience similar to this problem in one form or another. All of them must mishandle char encoding when dealing with a set of world wide browsers, todays html standards and the lack of adherence to those standards.