RESOLVED FIXED 14070
Synthetic bold and italic don't render 
https://bugs.webkit.org/show_bug.cgi?id=14070
Summary Synthetic bold and italic don't render
Torsten Kammer
Reported 2007-06-11 13:19:58 PDT
In Safari 3 public beta for Windows on Windows 2000 (I know it isn't supported), any text that uses a synthesized bold or italic font doesn't render. Texts that have true italic/bold fonts render just fine.
Attachments
Test case for bug (615 bytes, text/html)
2007-06-11 13:24 PDT, Torsten Kammer 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Torsten Kammer
Comment 1 2007-06-11 13:24:03 PDT
Created attachment 14936 [details] Test case for bug This demonstrates the bug. It assumes that Arial has no italic and bold versions on your computer. It should work with any other font that doesn't have these versions, too.
Paulo Aguiar
Comment 2 2007-06-12 06:25:03 PDT
(In reply to comment #1) > This demonstrates the bug. It assumes that Arial has no italic and bold > versions on your computer. It should work with any other font that doesn't have > these versions, too. > On my computer I have 'Arial', 'Arial Black', 'Arial Black Italic', 'Arial Bold', 'Arial Bold Italic', 'Arial Italic', 'Arial Narrow', 'Arial Narrow Bold', 'Arial Narrow Bold Italic', 'Arial Narrow Italic' and 'Arial Unicode MS'. I get the same problem too. It sucks since I can't even read Google's results properly. I hope they fix this soon...
Torsten Kammer
Comment 3 2007-06-12 12:17:54 PDT
To clarify: This is on a german installation of Windows (because others report that this doesn't happen on english installs)
Robert Blaut
Comment 4 2007-06-12 14:56:57 PDT
You can fix rendering issues by changing language for non-Unicode programs. The instruction: http://www.microsoft.com/globaldev/handson/user/xpintlsupp.mspx#EVE You should restart system after applying setting.
Robert Blaut
Comment 5 2007-06-15 14:22:08 PDT
Probably duplication of a bug #14086 which is actually fixed. On my Windows XP Pro with Polish locales test case works fine.
Alexey Proskuryakov
Comment 6 2007-07-06 05:33:52 PDT
Marking as fixed; please re-open if this still happens for you with Safari beta 3.0.2.
Note You need to log in before you can comment on or make changes to this bug.