Bug 24230 - SMP characters (0x16000-0x1607F) in ttf offered by font-face fail to render in Windows
: SMP characters (0x16000-0x1607F) in ttf offered by font-face fail to render i...
: WebKit
: 528+ (Nightly build)
: PC Windows XP
: P2 Normal
Assigned To:
: http://m8y.org/tmp/testcase63.xhtml
: 84012
  Show dependency treegraph
Reported: 2009-02-27 09:51 PST by
Modified: 2013-10-09 12:53 PST (History)



You need to log in before you can comment on or make changes to this bug.

Description From 2009-02-27 09:51:26 PST
This test page for text shadow and downloadable fonts renders the ring inscription using the private plane codepoint commonly used in the past (2nd and 3rd block) and the "draft" codepoint at 0x16000-0x1607F for the 4th inscription.

According to Rik, it displays fine in Safari 4 beta under OSX.
However, in webkit nightly and safari 4 beta under XP, the 4th inscription in BMP does not render.
------- Comment #1 From 2009-02-27 10:04:01 PST -------
I am a little confused by the terminology here (I thought 0x16000 was outside the BMP). The inability to display non-BMP characters on Windows is not specific to CSS3 web fonts, but I am not sure that there is a bug in Bugzilla about the general problem.
------- Comment #2 From 2009-02-27 10:05:04 PST -------
(My last comment was referring specifically to the Windows port used by Safari; the Chromium and Cairo ports may not have this issue).
------- Comment #3 From 2009-02-27 10:19:52 PST -------
I couldn't find any general bug about it.
I figured it might well extend beyond web fonts, but just thought I'd describe what I encountered.

You're right. Sorry. Should say SMP.  Altered title.
I'm not so great on the terminology is clear :)
------- Comment #4 From 2012-06-30 10:31:09 PST -------
*** Bug 90337 has been marked as a duplicate of this bug. ***
------- Comment #5 From 2012-06-30 10:33:10 PST -------
This bug also happens for fonts installed on the system. See bug 90337.
------- Comment #6 From 2013-10-09 12:53:09 PST -------
*** Bug 122526 has been marked as a duplicate of this bug. ***