search

razmitech / googlefontdirectory

Automatically exported from code.google.com/p/googlefontdirectory
0 stars 0 forks source link

Locally installed copy of Play fails to display #54

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
[Note: I've only confirmed this on Mac OS X; have yet to test to see if this 
issue also exists in Windows or Linux.]

What steps will reproduce the problem?
1. Download the "Play" font from: 
http://www.google.com/webfonts/family?family=Play&subset=latin#download
2. Install it using Font Book.
3. Go to the font preview page in Firefox: 
http://www.google.com/webfonts/family?family=Play&subset=latin#specimen

What is the expected output? What do you see instead?
Expected: The font sample appears.
What I see instead: There's a blank space where the font sample should be. (See 
attached screenshot.)

What version of the product are you using? On what operating system?
Latest Mercurial repo version, under Mac OS X 10.6.7.

Please provide any additional information below.
The page appears as expected with the font uninstalled from Font Book, so that 
the embedded font file is used-- this is strictly an issue with the 
downloadable font.

Original issue reported on code.google.com by codeman38 on 6 May 2011 at 11:56

Attachments:

GoogleCodeExporter commented 9 years ago 
Additional note: Locally-installed copies of the font render fine in Webkit 
(i.e., Safari and Chrome)-- this is strictly a Gecko-related bug.

Original comment by codeman38 on 6 May 2011 at 11:57

GoogleCodeExporter commented 9 years ago 
Actually, this is reproducible even in TextEdit. Enter "The quick brown fox 
jumps over the lazy dog", and the sentence completely disappears upon typing 
the "t" in the second "the". Weird.

Original comment by codeman38 on 6 May 2011 at 5:44

GoogleCodeExporter commented 9 years ago 
Oddly enough, regenerating the fonts in FontForge got rid of this glitch. So 
it's definitely something in the font files themselves.

I'm attaching the regenerated fonts for anyone else experiencing this issue.

Original comment by codeman38 on 7 May 2011 at 12:05

Attachments:

GoogleCodeExporter commented 9 years ago 
Upon further investigation, this appears to be due to a corrupt 'kern' table. 
The Python FontTools library cannot make sense of that table in the original 
font.

Original comment by codeman38 on 29 Jun 2011 at 2:20

GoogleCodeExporter commented 9 years ago 
Is there any way to quickly fix this bug?

Original comment by rso...@gmail.com on 30 Jun 2011 at 1:01

GoogleCodeExporter commented 9 years ago 
The regenerated font files attached in Comment 3 have the corrupt table removed 
and work fine in OS X.

Original comment by codeman38 on 30 Jun 2011 at 3:57

GoogleCodeExporter commented 9 years ago 
Issue 99 has been merged into this issue.

Original comment by pathum...@gmail.com on 12 Aug 2014 at 9:09

GoogleCodeExporter commented 9 years ago

Original comment by pathum...@gmail.com on 12 Aug 2014 at 9:09