Skip to content

Commit

Permalink
Merge pull request #150 from googlefonts/combining-marks
Browse files Browse the repository at this point in the history
Requirements combining marks made subhead
  • Loading branch information
emmamarichal authored Oct 10, 2024
2 parents 4881986 + 6e38237 commit 7c6acda
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions gf-guide/diacritics.md
Original file line number Diff line number Diff line change
Expand Up @@ -106,7 +106,7 @@ As the name suggests, the combining diacritics are the marks actually used to co

**Automatic alignment**

When creating the precomposed characters in the source file, ideally, automatic alignment should be enabled consistently in the composite glyphs. This way they would get authomatically updated after any change on any of the components is performed.
When creating the precomposed characters in the source file, ideally, automatic alignment should be enabled consistently in the composite glyphs. This way they would get automatically updated after any change on any of the components is performed.

*Tip: When using `ufo2glyphs` to convert source files, use this argument to preserve alignments: `--enable-automatic-alignment`*

Expand All @@ -117,7 +117,7 @@ All the glyphs involved in the generation of accented letters use *Anchors*, whi
Anchors are commonly represented as a red rhombus in the glyph view of the source file and are identified with a name. The name part should be shared among the base glyph and the mark glyph, but in the mark glyph there should be a preceding underscore. For example, there should be a `top` anchor in the base glyph and a corresponding `_top` anchor in the mark.
This name schema is crucial for the positioning to work as expected - for example if the underscore is omitted in the mark glyph, it would not be attached to the base letter - so you must pay special care and attention to them.

**Requirements for combining marks:**
### Requirements for combining marks

- **They must have a zero width value once in the font binary `=0`**. While working on the source file, it is possible to use a positive width with positive sidebearings to facilitate access to the glyph. Then, if the glyphs have the anchors and the correct name, the tool generating the font will take care of changing the width to 0 to comply with the requirement that they must be zero value width glyphs (hence the name **nonspacing**).
- The glyph name of combining marks should use the *comb* suffix, e.g. `acutecomb`, `gravecomb`.
Expand Down

0 comments on commit 7c6acda

Please sign in to comment.