The problems surrounding encoding is slowly starting to get the attention of web developers around the world. Previously content was mainly written in English, so we only needed support for the characters used in the English language. As pages in other languages started to appear they needed a way to display their special characters. The solutions they found rarely added support for special characters from other languages. This approached worked for a while, but now we’re seeing content written in one language with comments in every language imaginable. So a method to display all of these different characters at the same time is needed.
-
5 Reasons why decoupled-ness matters to your clients
-
Heroku's Cedar Polyglot Stack Goes GA
-
Windows Software Development Kit (SDK) for Windows 8 Consumer Preview
-
How-To: Use Application Deployment Tool in Windows Phone
-
Web Meeting: Load testing with JMeter - Best practices, regular expression extraction and use cases
-
So.cl by Microsoft - First Impression
Comments
amphi replied ago:
Since his blog doesn't want my comment (first database error, then "duplicate comment"... but the comment wasn't there) I'll comment here instead.
Verification of database rollbacks are often forgotten. If something goes wrong there (happens quite often actually) and you notice it too late, you'll have mixed encodings in your database.
Old stuff will be broken and if you fix it, the new stuff will be broken. Not cool.
The easiest way to identify this issue is to put some special chars (e.g. some Japanese) into the very first post. So, whenever you do a rollback you can quickly check if everything went well.
Voters For This Link (4)
Voters Against This Link (0)