209 words on Software
The issue of text encoding keeps following us around these days. If you’re only using the English parts of the web or computers you may remain blissfully unaware of that. But even if you’re wanting things as simple as umlauts the problems start appearing quickly. Two examples I recently ran into follow. The first is from Services menu entries provided by RealPlayer:
And the second was in the BatteryInfo Dashboard widget which I recently tried out:
And those problems puzzle me. How comes that Real hire people who don’t know how to write a properly encoded
Er, for some reason the link to the tshirts by everyone’s favourite Icelanders is coming out as “Sigur RÃ³s - Shirts”. Presumably because you’re declaring these pages as ISO 8859-1 but the feed from delicious is UTF8.
Yup, that’s true. It’s the reason why I first hesitated to include the delicious script for which you can’t (easily) change the encoding.
I guess I could just serve these pages as UTF-8 though but that’ll require another excursion to the dreaded htaccess manuals.
I changed the encoding I give within the HTML and that the server gives away… but some parts of MT still use the old encoding and I’m not really sure where and how to set that up.
Received data seems to be invalid. The wanted file does probably not exist or the guys at last.fm changed something.