This is why I love the Internet. I didn't even think about different Unicode characters and symbols. I whipped up the entire site in 2 days (most of it was spent tweaking the different frosting colors) and haven't even put it through my regular barrage of tests. I'll try to get Unicode working tomorrow, it mostly has to do with the specific font I used. Maybe I can give a few more font-choices. Also, I could auto-size the font according to the length of text.
I try UTF characters in everything which displays text, especially when it's graphically manipulated. It's slightly amazing how few handle it, even if there's little reason not to (unless a library along the pipeline only reads ASCII).
I think it's just that most people are used to dealing with / have encountered C char arrays, and 8 bits per character just makes sense to programmers. 'Tis why I jump for joy when I hear about framework-X fully supporting UTF - IMO, they all should, from day one, but I realize it can sometimes be a lot of work, and is always a performance hit.
You don't know how right you are. Google Web Toolkit has the most impressive support for Arabic, but it's ASCII only out of the box, even though it runs on Java, a thorough-bred Unicode language.
I made you a happy cake, just to show how much I liked it: http://cakesy.com/8a7d3b35a