Not rendering Thai or Lao correctly

Bug #688492 reported by Jeroen T. Vermeulen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: chromium-browser

I've been using the daily PPA builds on Ubuntu for some time now. I'm currently using Maverick, with the Ubuntu font.

Unfortunately Chromium on my system still does not render the Thai and Lao languages legibly. I hear the same from others. The problem definitely predates the Ubuntu font; I don't think it's ever worked. For instance I can go to translate.google.com or launchpad.net and type "เปิด" (Thai) or "ເປຶດ" (Lao) and the vowel " ิ " or " ຶ " will appear over the "เ" or "ເ" respectively, instead of over the ป/ປ where it belongs. This can turn the text in total gibberish, distorting even where the words begin and end let alone their meanings.

Similar problems probably occur with Khmer and Myanmar, as well as Indic scripts, all of which are related but more complex (and sometimes less mature in their standardization).

Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

Just confirming: the display is incorrect, not just the input—I see the bug in this bug report as well.

Revision history for this message
Fabien Tassin (fta) wrote :

just to clarify, are you saying it's an ubuntu bug and that the upstream builds are not impacted?

i just checked the upstream bug tracker, and it seems there are a few bugs for Thai already:
http://code.google.com/p/chromium/issues/detail?id=29091
http://code.google.com/p/chromium/issues/detail?id=23371
http://code.google.com/p/chromium/issues/detail?id=56916
http://code.google.com/p/chromium/issues/detail?id=46694
..

Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

I'm not sure where the bug creeps in, to be honest; I just know it's there in Ubuntu, and it does not appear to be in Safari (so it's not webkit). It could be related to Ubuntu's font rendering or the fonts I have installed. So I thought it was appropriate to go through triage for Ubuntu.

I didn't find Google's bug tracker before, "issue" being such a ridiculously vague euphemism, so that's why I failed to check for existing bugs. But now I find that this problem is the same as their "issue" 56916 (which may still be Ubuntu-specific).

Revision history for this message
Olivier Tilloy (osomon) wrote :

Upstream bug fixed.

Changed in chromium-browser (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.