关于unicode international 的看法！

What You Have to Do · So what, practically speaking, should you do, as a software practitioner? Here are a bunch of recommendations:

• Embrace Unicode, don't fight it; it's probably the right thing to do, and if it weren't you'd probably have to anyhow.
• Inside your software, store text as UTF-8 or UTF-16; that is to say, pick one of the two and stick with it.
• Interchange data with the outside world using XML whenever possible; this makes a whole bunch of potential problems go away.
• Try to make your application browser-based rather than write your own client; the browsers are getting really quite good at dealing with the texts of the world.
• If you're using someone else's library code (and of course you are), assume its Unicode handling is broken until proved to be correct.
• If you're doing search, try to hand the linguistic and character-handling problems off to someone who understands them.
• Go off to Amazon or somewhere and buy the latest revision of the printed Unicode standard; it contains pretty well everything you need to know.
• Spend some time poking around the Unicode web site and learning how the code charts work.
• If you're going to have to do any serious work with Asian languages, go buy the O'Reilly book on the subject by Ken Lunde.
• If you have a Macintosh, run out and grab Lord Pixel's Unicode Font Inspection tool. Totally cool.
• If you're really going to have to get down and dirty with the data, go attend one of the twice-a-year Unicode conferences. All the experts go and if you don't know what you need to know, you'll be able to find someone there who knows.