Glyphs-Handbook-2013

Recommendations

Info

More information about Monotype’s PANOSE classification system: monotypeimaging.com/ ProductsServices/pan1.aspx license string License description. Corresponds to the OpenType name table name ID 13, the ‘description of how the font may be legally used, or dierent example scenarios for licensed use. This field should be written in plain language, not legalese.’ licenseURL string URL for the license. Corresponds to the OpenType name table name ID 14. ‘URL where additional licensing information can be found.’ note string Arbitrary note about the font. openTypeHheaAscender see hheaAscender openTypeHheaDescender see hheaDescender openTypeHheaLineGap see hheaLineGap openTypeNameCompatibleFullName see compatibleFullName openTypeNameDescription see description openTypeNameLicense see license openTypeNameLicenseURL see licenseURL openTypeNamePreferredFamilyName see preferredFamilyName openTypeNamePreferredSubfamilyName see preferredSubfamilyName openTypeNameSampleText see sampleText openTypeNameWWSFamilyName see WWSFamilyName openTypeNameWWSSubfamilyName see WWSSubfamilyName openTypeOS2Panose see panose openTypeOS2Type see fsType openTypeOS2TypoAscender see typoAscender openTypeOS2TypoDescender see typoDescender openTypeOS2TypoLineGap see typoLineGap openTypeOS2UnicodeRanges see unicodeRanges openTypeOS2VendorID see vendorID openTypeOS2WeightClass see weightClass openTypeOS2WidthClass see widthClass openTypeOS2WinAscent see winAscent openTypeOS2WinDescent see winDescent openTypeVheaVertTypoAscender see vheaVertTypoAscender openTypeVheaVertTypoDescender see vheaVertTypoDescender openTypeVheaVertTypoLineGap see vheaVertTypoLineGap panose list The list must contain 10 non-negative integers that represent the setting for each category in the Panose specification. The integers correspond with the option numbers in each of the Panose categories. This corresponds to the OpenType OS/2 table Panose field. ‘This 10 byte series of numbers is used to describe the visual characteristics of a Glyphs Handbook, May 2013 92
given typeface. These characteristics are then used to associate the font with other fonts of similar appearance having dierent names. […] The Panose values are fully described in the Panose “greybook” reference, currently owned by Monotype Imaging. The PANOSE definition contains ten digits each of which currently describes up to sixteen variations. Windows uses bFamilyType, bSerifStyle and bProportion in the font mapper to determine family type. It also uses bProportion to determine if the font is monospaced. If the font is a symbol font, the first byte of the PANOSE number (bFamily- Type) must be set to “pictorial.” ’ postscriptBlueScale see blueScale postscriptBlueShift see blueShift postscriptFontName string Name to be used for the FontName field in Type 1/CFF table. Should be ASCII-only, no whitespace allowed, e.g., ‘MyFont-Regular’. postscriptFullName string Name to be used for the FullName field in Type 1/CFF table. postscriptUnderlinePosition see underlinePosition postscriptUnderlineThickness see underlineThickness preferredFamilyName string Preferred family name. Corresponds to the OpenType name table name ID 16. ‘For historical reasons, font families have contained a maximum of four styles, but font designers may group more than four fonts to a single family. The Preferred Family allows font designers to include the preferred family grouping which contains more than four fonts. This ID is only present if it is dierent from ID 1’, the Family Name as set in Font Info. preferredSubfamilyName string Preferred subfamily name. Corresponds to the OpenType name table name ID 17. ‘Preferred Subfamily; Allows font designers to include the preferred subfamily grouping that is more descriptive than ID 2. This ID is only present if it is dierent from ID 2 and must be unique for the the Preferred Family.’ sampleText string Sample text. Corresponds to the OpenType name text that the designer thinks is the best sample to display the font in.’ styleMapFamilyName string Family name used for bold, italic, and bold italic style mapping. You can use this to create subfamilies within larger font families. ‘Up to four fonts can share the Font Family name, forming a font style linking group.’ Glyphs Glyphs Handbook, May 2013 93
Page 1 and 2:
Glyphs Handbook May 2013
Page 3 and 4:
Contents 1 Glyphs 6 1.1 A Tool for
Page 5 and 6:
6.3.5 Custom Parameters 58 6.4 Feat
Page 7 and 8:
Because of contractual restrictions
Page 9 and 10:
Left: original glyph outline with t
Page 11 and 12:
You can take advantage of the align
Page 13 and 14:
The results of the Open Corner and
Page 15 and 16:
Tip: You may need to change your Sp
Page 17 and 18:
2.4.4 Components, Anchors, Clouds L
Page 19 and 20:
second example, the diacritic recip
Page 21 and 22:
2.4.8 Cursive Attachment Anchors To
Page 23 and 24:
Tip: On a MacBook, you can simulate
Page 25 and 26:
The x delta values respect the ital
Page 27 and 28:
code. Negative kernings will be dis
Page 29 and 30:
2.9.2 Manipulating Images Move the
Page 31 and 32:
Because of the described difficulti
Page 33 and 34:
2.11.3 Copy the Paths Copy and past
Page 35 and 36:
Smaller curves, e.g. counters, gene
Page 37 and 38:
This means that if you want to scal
Page 39 and 40:
Tip: You can apply the Make Stroke
Page 41 and 42: 4.7 TRANSFORMATIONS 4.7.1 Transform
Page 43 and 44: 5.1.2 List View You can switch the
Page 45 and 46: glyphs with the same glyph names as
Page 47 and 48: 5.3.9 Read-Only Properties in List
Page 49 and 50: 5.5.4 Custom Filters To define a qu
Page 51 and 52: This automation can be deactivated
Page 53 and 54: 6 Font Info 6.1 FONT Open the Font
Page 55 and 56: See section 12.2, ‘Custom Paramet
Page 57 and 58: 6.2.5 Custom Parameters Click on th
Page 59 and 60: Pro User Tip: In complex Multiple M
Page 61 and 62: 6.5 OTHER SETTINGS 6.5.1 Grid Spaci
Page 63 and 64: 7 Spacing and Kerning 7.1 SPACING S
Page 65 and 66: Kerning exceptions are handled per
Page 67 and 68: For an in-depth discussion, see: ty
Page 69 and 70: 8.1.3 Custom Parameters Apart from
Page 71 and 72: Positioning of vertical stem hints
Page 73 and 74: Tip: It is advisable to keep uprigh
Page 75 and 76: Tip: Quickly switch between masters
Page 77 and 78: 10 Error Handling 10.1 GLYPH NAMES
Page 79 and 80: Unnecessary kerning between two scr
Page 81 and 82: 10.5.4 Outline Incompatibility Inco
Page 83 and 84: and some of the font metadata store
Page 85 and 86: Tip: do not use the figure suffix w
Page 87 and 88: All quotes in this chapter are take
Page 89 and 90: UFO3 Font Info properties are descr
Page 91: Further, applications loading embed
Page 95 and 96: The suggested usage for sTypoDescen
Page 97 and 98: The term ANSI refers to the Windows
show all

Glyphs-Handbook-2013

Create successful ePaper yourself

Delete template?

Save as template?