Re: Getting...oriented.
| From: | a . h . s . boy | Date: | Wed, 12 Feb 2003 16:32:46 +0000 |
| Subject: | Re: Getting...oriented. | ||
| References: | 1 | Groups: | php.i18n |
| Request: | Send a blank email to php-i18n+get-448@lists.php.net to get a copy of this message | ||
On Wednesday, February 12, 2003, at 02:42 AM, Moriyoshi Koizumi wrote:
I realized, somewhere in the midst of writing my last post, that UTF-8 was capable of displaying Japanese characters, but it doesn't seem to be a particularly common choice. And as long as I was only expecting single-byte languages, shouldn't Japanese input still cause potential problems, especially with str functions? I just attempted a cut-n-paste (since I can't input real Japanese myself) into my app from a random Japanese site, and it appeared to work, but I can't forsee what problems may occur that I'm not considering. And I've only tested it using the Safari browser under Mac OS X (which supports Unicode and various language inputs quite well), so I'm not sure how well it works with the more common Windows 98/XP MSIE combination... There's a development version of the app at http://dev.dadaimc.org/, if anyone more familiar with Japanese would like to test. Use the "post an article" link at the top of the page to submit... Cheers, spud. ------------------------------------------------------------------- a.h.s. boyWell, I've mostly lived through the experience of internationalizing a very large PHP application (using gettext()) to support the majority of Western languages. I'm using UTF-8 as the default encoding for the site (and form input), though MySQL still has Latin1 as its default character set (which doesn't seem to pose any problems). But just when I thought that might be sufficient, of course someone comes along and wants to use the system in English and...Japanese.UTF-8 also covers Japanese letters...
spud(at)nothingness.org "as yes is to if,love is to yes"http://www.nothingness.org/ -------------------------------------------------------------------