Aargh, still stuck on character encoding issues at work. It's stuff I've always known was wrong, and we've fixed in various different ways, but now I'm trying to get to the root of it.
The base problem is that our database is in one character set, but we need our web pages to be another now we have so much multilingual content.
I think we should scrap the pound and start using dollars instead instead, that would solve 90% of the issues. The pound sign (the uk pound sign) is the only symbol we need regularly on the english sites that causes us an issue, but umlauts and cedillas and so on that are common in other languages also need attention.
Good grief we might have to do a Greek website next...
UPDATE: most popular tweet ever1...
Paul Clarke's blog - I live in Hythe in Kent. Married to Clare + father to two, I am a full-stack web developr, and I do js / nodejs, some ruby, other languages ect ect. I like pubs, parkrun, eating, home-automation and other diy jiggery-pokery, history, family tree stuff, Television, squirrels, pirates, lego, + TIME TRAVEL.