My favorites | Sign in
Logo
             
New issue | Search
for
| Advanced search | Search tips
Issue 8150: Complex script support
13 people starred this issue and may be notified of changes. Back to list
 
Reported by evan@chromium.org, Feb 26, 2009
We currently don't pass layout tests that involve complex scripts because 
we haven't implemented support in our WebKit port.

An implementation of this may be able to just borrow from the GtkWebKit 
port, but it seems it will more likely touch Skia.  It may be the case that 
work on this is already being done for Android, so you'd best ask agl or 
Mike Reed before working on this.
Comment 1 by evan@chromium.org, Feb 27, 2009
(No comment was entered for this change.)
Owner: ---
Comment 2 by evan@chromium.org, Feb 27, 2009
(No comment was entered for this change.)
Status: Assigned
Owner: a...@chromium.org
Comment 3 by agl@chromium.org, Mar 27, 2009
(No comment was entered for this change.)
Status: Started
Comment 4 by jon@chromium.org, Apr 08, 2009
(No comment was entered for this change.)
Labels: Mstone-Linux
Comment 5 by jon@chromium.org, May 04, 2009
Removing the mstone:linux label which will no longer be used.  The 
mstone:LinuxDev label indicates issues that should be resolved before the 
release of the Linux build to testers and then the dev channel.

There will also be a mstone:LinuxBeta label to indicate features that are 
required for the release to the beta channel.

The initial assignment is based on priority.  We need to triage the entire 
list to check these assignements.
Labels: Mstone-LinuxDev
Comment 6 by evan@chromium.org, May 15, 2009
(No comment was entered for this change.)
Labels: -Pri-2 Pri-1
Comment 7 by evan@chromium.org, May 15, 2009
(No comment was entered for this change.)
Labels: -Mstone-LinuxDev
Comment 8 by est...@chromium.org, May 26, 2009
 Issue 12672  has been merged into this issue.
Cc: hb...@chromium.org js...@chromium.org
Comment 9 by delphiexile, May 26, 2009
OK , still waiting for solving this problem.
Comment 10 by evan@chromium.org, Jun 15, 2009
 Issue 13993  has been merged into this issue.
Cc: e...@chromium.org xly...@chromium.org
Comment 11 by evan@chromium.org, Jun 15, 2009
Keywords for other people searching the bug tracker: Arabic, Aramaic, Farsi, Urdu, 
Indic.  (Maybe Thai, too?)
Comment 12 by xlyuan@chromium.org, Jun 16, 2009
Adding "I18N" label for tracking purpose :-)
Labels: I18N
Comment 13 by xlyuan@chromium.org, Jun 17, 2009
 Issue 13523  has been merged into this issue.
Comment 14 by agl@chromium.org, Jun 17, 2009
https://bugs.webkit.org/show_bug.cgi?id=25068
Comment 15 by mal.chromium, Jun 17, 2009
(No comment was entered for this change.)
Labels: Mstone-LinuxBeta
Comment 16 by agl@chromium.org, Jun 19, 2009
 Issue 13210  has been merged into this issue.
Cc: est...@chromium.org a...@chromium.org
Comment 17 by strickyak, Jun 22, 2009
+Thai +Tibetan
Comment 18 by strickyak, Jun 22, 2009
I think the biggest problem is that even ASCII becomes invisible 
when it's on the same line as (say) Thai.

Demonstrated at http://code.google.com/p/chromium/issues/detail?id=14762

Worse, it affects submissions in Edit Boxes -- the entire edit box goes blank
if any Thai is in it.

I suggest at least a workaround, replacing affected langs with Bad Char symbols,
allowing the rest to render.

Comment 19 by evan@chromium.org, Jun 23, 2009
 Issue 15043  has been merged into this issue.
Comment 20 by agl@chromium.org, Jul 02, 2009
 Issue 15772  has been merged into this issue.
Cc: x...@chromium.org jer...@chromium.org id...@chromium.org
Comment 21 by juhpetersen, Jul 08, 2009
http://wikipedia.org/ looks quite good to me now: on par with firefox. :)
Comment 22 by agl@chromium.org, Jul 08, 2009
Marking this bug as Fixed, since stuff mostly works. If you have specific bugs about 
complex text rendering, please file new bugs and CC me. (Note: there is one 
outstanding WebKit patch to fix the case where selecting Thai text causes a renderer 
crash).
Status: Fixed
Comment 23 by delphiexile, Jul 09, 2009
The Rendering of complex-script' characters is not so precious as under Firefox ,
clear types are not used , should correct that.
Comment 24 by mfto7.com, Jul 09, 2009
I think the about:linux-splash should be changed since complex text support and 
complex tab dragging are now working

Comment 25 by mfto7.com, Nov 26, 2009
This is not fixed in the chromeOS version of the browser
Example:
google.com.eg
All Arabic text is not rendered

Screenshot.png
67.9 KB   View   Download
Comment 27 by jeremy@chromium.org, Nov 26, 2009
mfto7.com: The behavior you're seeing is due to the font used on ChromeOS not 
currently containing glyphs for various languages e.g. Hebrew/Arabic which is 
completely different than the bug this issue was tracking.
Comment 28 by jungs...@google.com, Nov 26, 2009
Jeremy is right. We're gonna add more fonts soon to ChromeOS. See 
http://code.google.com/p/chromium-os/issues/detail?id=373



Sign in to add a comment