UNCONFIRMED Bug 53481
Some characters from Junicode font are not displayed on some machines
https://bugs.webkit.org/show_bug.cgi?id=53481
Summary Some characters from Junicode font are not displayed on some machines
Jan Pingel
Reported 2011-02-01 00:55:27 PST
Webkit based browsers such as Safari and Chrome do not seem to support font substitution like gecko based browsers do for unicode characters not available in the page's defined or alternative fonts. For example compare http://www.alanwood.net/unicode/runic.html in webkit and gecko browsers. Webkit just shows the same glyph for each character while gecko will find a font (in this case Junicode) and substitute the proper characters in place.
Attachments
Example of rendering in gecko (45.57 KB, image/png)
2011-02-01 00:57 PST, Jan Pingel
no flags
example of rendering in webkit (66.38 KB, image/png)
2011-02-01 00:58 PST, Jan Pingel
no flags
Jan Pingel
Comment 1 2011-02-01 00:57:59 PST
Created attachment 80727 [details] Example of rendering in gecko
Jan Pingel
Comment 2 2011-02-01 00:58:24 PST
Created attachment 80728 [details] example of rendering in webkit
Alexey Proskuryakov
Comment 3 2011-02-01 11:18:16 PST
We certainly do perform this "font substitution", and I can't reproduce this bug. After installing Junicode-Regular font, all runes we displayed just fine for me in Safari 5.0.3 on Mac. You screenshot shows that some runes did use Junicode, and some didn't. That's obviously not right. Which version of Safari/WebKit are you seeing this with? Does this also happen with nightly WebKit builds from <http://nightly.webkit.org/>?
Philippe Wittenbergh
Comment 4 2011-02-02 00:56:42 PST
(In reply to comment #3) > We certainly do perform this "font substitution", and I can't reproduce this bug. After installing Junicode-Regular font, all runes we displayed just fine for me in Safari 5.0.3 on Mac. They don't display correctly on my side, OS X 10.6.6, Safari 5.0.3, Chrome 10 dev channel, Webkit latest nightly (r77282). Junicode 0.6.17.
Alexey Proskuryakov
Comment 5 2011-02-02 08:36:16 PST
Did you try any troubleshooting steps, like resetting system font cache (see <http://www.extensis.com/en/support/kb_article.jsp?articleNumber=7502205> and <http://hints.macworld.com/article.php?story=20071026081555971>)? Do you have another machine where you could try this on?
Philippe Wittenbergh
Comment 6 2011-02-03 00:33:42 PST
(In reply to comment #5) > Did you try any troubleshooting steps, like resetting system font cache (see <http://www.extensis.com/en/support/kb_article.jsp?articleNumber=7502205> and <http://hints.macworld.com/article.php?story=20071026081555971>)? > > Do you have another machine where you could try this on? Clearing font-caches (and restarting the machine for good measure) didn't help. Testing on a second machine running 10.6.6 fails with Safari 5. Camino (Gecko 1.9.2), a recent Minefield nightly (Gecko 2.0b) and Opera 11 all display the test page correctly.
Jan Pingel
Comment 7 2011-02-03 07:11:30 PST
I have two machines running 10.6.6 and it does not work under Safari 5.0.3, Webkit r77282, or Chrome 9.0.597.84 beta. Clearing the font cache has no affect.
Alexey Proskuryakov
Comment 8 2011-02-07 00:10:39 PST
I tried on a different machine (in shipping Safari/WebKit 5.0.3), and I still can't reproduce.
Patrick R. Gansterer
Comment 9 2011-02-08 16:31:10 PST
I can't reproduce this too. I installed the fonts and it works in Safari 5.0.3 and trunk on 10.6.6... Is it possible that this is caused by some language/locale setting???
Jan Pingel
Comment 10 2011-03-12 21:07:33 PST
(In reply to comment #9) > I can't reproduce this too. I installed the fonts and it works in Safari 5.0.3 and trunk on 10.6.6... > Is it possible that this is caused by some language/locale setting??? I tried creating a new account and left the preferences at their defaults. Still not working for me.
Jan Pingel
Comment 11 2011-12-24 19:33:22 PST
New Mac and able to reproduce this on Lion with a new user account. Affects Chrome as well as Safari. English for Language and Canada for Format settings.
Note You need to log in before you can comment on or make changes to this bug.