orszaczky / googlefontdirectory

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

Gudea TTF version has warped 'S' #108

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Download the TrueType version of the Gudea font from the Mercurial repo, or 
at http://code.google.com/p/googlefontdirectory/source/browse/gudea.
2. Open the font.

What is the expected output? What do you see instead?
Expected output: the capital 'S' looks normal.
Actual output: the curve is completely warped and overlaps the bowl, as shown 
in the attached screenshot.

What version of the product are you using? On what operating system?
Revision 3c9aa030625c, OS X 10.7.2.

Please provide any additional information below.
The OpenType source file is fine; something went wrong in generating the SFD 
from it. No idea what happened; it comes out fine when I convert it in 
FontForge using ttf2sfd.ff.

Original issue reported on code.google.com by codeman38 on 7 Jan 2012 at 12:23

Attachments:

GoogleCodeExporter commented 9 years ago
Aha, that's where it went wrong - I'd forgotten to run it through 
SetQuadraticAddExtremaSimplify. Something apparently goes wrong in the 
quadratic conversion, that *doesn't* go wrong when just doing a direct otf->ttf 
export.

Original comment by codeman38 on 7 Jan 2012 at 12:30

GoogleCodeExporter commented 9 years ago
Upon further investigation, it's in the Simplify step that the 'S' gets 
garbled. And, even more specifically, it's the 'mergelines' part of the 
simplification-- if that parameter is removed, the 'S' comes out un-mangled.

Original comment by codeman38 on 7 Jan 2012 at 12:51

GoogleCodeExporter commented 9 years ago
http://code.google.com/p/googlefontdirectory/source/detail?r=8de5a8d1bb8a9f513ce
1e8ce1f1247ab0e4506b5

Fixed - thank you for spotting this!

Original comment by dcrossland@google.com on 8 Jan 2012 at 8:49

GoogleCodeExporter commented 9 years ago
Still not entirely fixed... the bold font has the same bug. (Sorry, didn't 
clarify!)

Original comment by codeman38 on 11 Jan 2012 at 4:29