Search found 9 matches

I know PHP doesn't have the best UTF-8 support on the planet, but can we please have UTF-8 support for reviews? With just 500 characters, typing multiple hyphens for em-/en-dashes and HTML entities for accented characters is pretty wasteful, and the anal retentive nerd inside me just can't accept om...

In the XML feeds, could you put the year in the reviewdate field please? It's the only part of the date missing, and guessing the current year is going to become wrong very soon.

Yep, that's it. It's appropriate to encode them in XML and (X)HTML but not plaintext. <br> <br>It would be nice to get UTF-8 support, too, so that people can use stuff like em-dashes (—) and accents (á, ä, à). You're sending pages as ISO-8859-1 at the moment, so I presume you're storing data as lati...

Oh, another bug (I bet you love me :P): you're encoding XML/HTML entities in your plain-text feeds, which shouldn't happen.

Not allowing formatting such as HTML I can understand, but not even allowing line breaks? It would be pretty useful, IMO. <br> <br>Also, since you're presumably offering your web services for actual consumption, it might be worth maintaining old versions (and by extension passing a version in the UR...

Neat. Does it apply in reviews as well?

Also, if we're having random suggestions here, it would be nice if newlines were converted automatically to paragraph tags (á la Matt Mullenwegs Newlines to Paragraphs http://photomatt.net/scripts/autop/) in reviews, and if review fields were longer.

D'oh, those brackets were supposed to be an ampersand followed by amp; and #0x26; respectively

Thanks for the data feeds, they'll come in handy! I wrote a PHP package for parsing text data here: http://robm.me.uk/2007/08/14/php-criticker However, your XML and RSS feeds for ratings are currently broken; you'll need to parse ampersands into their correct XML entity (either & or &) to g...