Updates:
        Status: Started
        Owner: [email protected]

Comment #17 on issue 6135 by [email protected]: RTL: Hebrew text with  
diacritical marks rendered with extra spaces in Chrome/Windows.
http://code.google.com/p/chromium/issues/detail?id=6135

Thank you for all those who gave me lots of information, and sorry for my  
late updates.
This week, I have changed the "white-space" property and investigated the  
behaviors of WebKit in rendering both complex texts and simple texts. To
write from conclusion, the UniscribeHelper class can treat line-break  
characters (U+000A and U+000D) as whitespace.
When the "while-space" property of a complex text is "pre" (or the text is  
in a <pre> element), WebKit automatically splits the text with line-
break characters and call the UniscribeHelper class line by line. So, a  
string passed to the UniscribeHelper class does not contain line-break
characters.
On the other hand, when the "while-space" property of a complex text is  
either "nowrap" or "normal", WebKit calls the UniscribeHelper class
without splitting the text with line-break characters. So, a string passed  
to the UniscribeHelper class may contain line-break characters.
These facts make me assume the UniscribeHelper class can treat line-break  
characters as whitespace ones. In fact, the Font::drawSimpleText()
function (which renders a simple text) actually does it and it works  
without problems.

(*1) Correctly, our GlyphPage implementation treats line-break characters  
as whitespace.

I filed a bug (*2) in webkit.org and sent a review request to fix this  
issue to Webkit.

(*2) https://bugs.webkit.org/show_bug.cgi?id=23786



--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---

Reply via email to