Currently I am running version 5.0.0.714 of the BlackBerry OS on my bold 9700, because my carrier has not released the latest version 6 of the OS for my phone. Still version 5 is pretty mature, and so I was surprised to run across this bug with rendering a particular Vietnamese letter.
On my BlackBerry, whether I am using the blackberry browser, gmail, blackberry's messenger, or opera mini, the blackberry renders the character ờ, which is unicode U+1EDD, as the character ớ, which is unicode unicode U+1EDB.
Here is a blown up screenshot of the two _different_ characters "ờ ớ" on the BlackBerry noted above using blackberry's messenger application:
This is the same way that it looks in all of the applications noted above using BlackBerry OS 5.0.0.714.
Curiously, I also found that this same rendering problem is happening on my Android phone for the same email. And the issue is also happening using with Android web browser in pages like this one. So it looks like several mobile platforms are having this issue. And now that I think of it, this blog post would be much harder to understand if you are reading it on a mobile device which has this bug.
On the other hand if I use LogicMail, which is currently the most popular open source email client available for the BlackBerry, and I turn on the "Unicode normalization" feature in the configuration, here is the resulting screen shot from the same email:
What is nice about this feature of LogicMail is that it improves your ability to read Vietnamese emails whether you are running older versions of the OS or not, so anyone whose carrier (or company) has locked them into older versions of the BlackBerry OS, can still get the benefit of LogicMail's unicode normalization option. Open source is great.
I wonder if this is still an issue with BlackBerry OS 6. If it is then these two different characters will look the same: ờ ớ
Maybe you can let us know in the comments below.
Incidentally, this character must be from the same family of characters which appear to be quite popular on reddit.com.
Monday, January 03, 2011
Subscribe to:
Post Comments (Atom)
2 comments:
I just tested this on an OS 5.0 device (Storm 9550) and my OS 6.0 device (9700 running a leaked build).
I can confirm that the bug definitely exists in OS 5.0, and that the bug is definitely fixed in OS 6.0!
Hi Vernon
I've sent you an email to ask about NFC and NFKD (your gmail). Please reply it
thank u very much :)
Post a Comment