|
From: Scott C. <cy...@sl...> - 2001-04-03 20:19:48
|
> Over the last few weeks, a number of people have asked me about how > hard it would be to internationalize Communicator. I freely admit that > I have barely the faintest idea what that might mean, besides > (perhaps) introducing a wide string datatype. Has anyone thought about > this issue? Internationalization could mean making all the tihngs Communicator prints out obey the localization settings. This is a lot of work. If it is "just" a matter of building multi-lingual systems, then Communicator is out of the picture if the servers can agree on a standard character encoding such as UTF-8, Big5, etc. (CJKV Information Processing by Ken Lunde is a good resource for the harder cases: Chinese, Japanese, Korean, and Vietnamese). None of this is very pleasant in C/C++. |