[Webkit-unassigned] [Bug 8854] CSS1: text-transform: capitalize doesn't handle ligatures and non-BMP characters

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Apr 14 15:48:41 PDT 2010


https://bugs.webkit.org/show_bug.cgi?id=8854





--- Comment #6 from Nicholas Wilson <nicholas at nicholaswilson.me.uk>  2010-04-14 15:48:40 PST ---
We might have different results then (Debian). I admit though that after
opening the test case in Chrome, which is fine, I cavalierly modified the test
before looking at in my trunk version of WebKit because I wanted to add in some
harder combining characters. By an unlucky fluke, also I moved the Deseret to
the end of the line, and by a bug-of-a-bug the SMP problems vanish in that
specific case only (on trunk webkit; Chrome[ium] is entirely good). WebKit
mangles things that follow SMP characters, but renders perfectly SMP text at
the end of lines.

Further probing does reveal that this is an especially odd fluke,
unfortunately, because normally the end of the string is truncated as well
(str.len is clearly being incorrectly used to find the length of the UTF-16
strings used internally in vectors of UChars). I really cannot work out what is
going on though that the Deseret text displays without any truncation, but
other examples lose exactly one UChar from the end of the string per SMP
surrogate pair. On the plus side, it is not possible to get half a pair to
display, however hand you try; the dangling half is dropped cleanly. Some
characters after runs of SMP text are wrong too (possibly UTF-16 treated as
UCS-1 then encoded as UTF-8?).

On the other hand, ligature handling does work. That was the little bug though,
unfortunately. SMP problems are actually more urgent because we need the maths
symbols hidden in there.

As a side-note, whatever Chrome did to fix this we might be able to copy.

There is plenty of discussion along lines in their bug tracker, so I will have
a look at that.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list