Having been using CJKOS for a while, I finally realised that having it only support GB2312, GBK, and Big5 directly is a big nasty disadvantage, in my opinion... While it's not really noticeable when using my Treo normally, it has become apparent.
e.g. The developer was obviously a bit lazy, so that when I view a UTF-8 webpage with traditional characters, but the display charset is set to GB2312, it will use a code-page conversion to convert from UTF-8 to GB2312, but it won't think about trying to convert to Big5, so it won't display the traditional characters, but only those whose simplified form is the same as their traditional. Now, that's not cool. It's also obvious in other contexts (e.g. I need to use AppLocal to load Palm Desktop with GB2312 in order to view my Chinese Contacts, Chinese Memos, etc).
But I suspect that it gets worse. If you're studying, say, Japanese and Chinese, then you're going to have a lot of fun trying to text properly in both languages (not that any cellphone can display both at the same time).
It also causes problems with other applications. Certain accented characters (é) have the same byte-code as CJK characters, meaning that I need to turn CJKOS off to read my eBooks.
I'm not sure if changing the encoding would make a difference, but it might.
The one other thing I've noticed is that you can't enter Kanji for Japanese with CJKOS. Now, this isn't a problem for me, but I imagine it would be for Japanese speakers...
So, does anyone have any idea how hard this would be to do for Palm OS as a whole? Mike, I believe you're using UTF-8 internally for Pleco? Any comments on this?
It'd also be nice to have only one piece of software for any given language.
I'm really just thinking out loud with this, but it does annoy me that CJKOS thinks encoding everything in non-unicode formats is a good idea. I'm also well aware this would cause several problems (Text Messaging being the biggest), but I'm sure there are ways around that.
e.g. The developer was obviously a bit lazy, so that when I view a UTF-8 webpage with traditional characters, but the display charset is set to GB2312, it will use a code-page conversion to convert from UTF-8 to GB2312, but it won't think about trying to convert to Big5, so it won't display the traditional characters, but only those whose simplified form is the same as their traditional. Now, that's not cool. It's also obvious in other contexts (e.g. I need to use AppLocal to load Palm Desktop with GB2312 in order to view my Chinese Contacts, Chinese Memos, etc).
But I suspect that it gets worse. If you're studying, say, Japanese and Chinese, then you're going to have a lot of fun trying to text properly in both languages (not that any cellphone can display both at the same time).
It also causes problems with other applications. Certain accented characters (é) have the same byte-code as CJK characters, meaning that I need to turn CJKOS off to read my eBooks.
I'm not sure if changing the encoding would make a difference, but it might.
The one other thing I've noticed is that you can't enter Kanji for Japanese with CJKOS. Now, this isn't a problem for me, but I imagine it would be for Japanese speakers...
So, does anyone have any idea how hard this would be to do for Palm OS as a whole? Mike, I believe you're using UTF-8 internally for Pleco? Any comments on this?
It'd also be nice to have only one piece of software for any given language.
I'm really just thinking out loud with this, but it does annoy me that CJKOS thinks encoding everything in non-unicode formats is a good idea. I'm also well aware this would cause several problems (Text Messaging being the biggest), but I'm sure there are ways around that.