Skip to content

Commit

Permalink
Merge branch 'dev'
Browse files Browse the repository at this point in the history
  • Loading branch information
@chrissimpkins
chrissimpkins committed Aug 13, 2018
2 parents 2c1fc7c + 069ff8d commit ae93bab
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions docs/MODS.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -68,13 +68,13 @@ The following glyph name modifications were made to the upstream source as part

### Adobe Glyph List for New Fonts (AGLFN) data

Glyph names included in the AGLFN data were parsed from the upstream source file. The parsed data were tested against the data contained in the GlyphData.xml file in an automated fashion an the data were modified when invalid glyph names were identified (see above Data Modifications section for details). The glyph name data in each text file was supplemented with additional data from the Glyphs application GlyphData.xml data. These supplemental data included the following: (1) glyph unicode code point in hexadecimal format; (2) glyph production name (when AGL-like nice name included and production name available); (3) glyph nice name (when glyph production name used and nice name available); (4) Unicode short description string. These data were added as a comment-delimited line of text directly above the glyph name.
Glyph names included in the AGLFN data were parsed from the upstream source file. The parsed data were tested against the data contained in the GlyphData.xml file in an automated fashion and the data were modified when invalid glyph names were identified (see above Data Modifications section for details). The glyph name data in each text file were supplemented with additional data from the Glyphs application GlyphData.xml data. These supplemental data included the following: (1) glyph unicode code point in hexadecimal format; (2) glyph production name (when AGL-like nice name included and production name available); (3) glyph nice name (when glyph production name used and nice name available); (4) Unicode short description string. These data were added as a comment-delimited line of text directly above the glyph name.

### Google Fonts Glyph Set data

Glyph names in the Google Fonts Core, Plus, Pro, and Expert glyph sets are released in the same file format at the upstream source files. The data in these files were tested against data contained in the Glyphs application GlyphData.xml file in an automated fashion and the data were modified when invalid glyph names were identified (see above Data Modifications section for details). The glyph name data in each text file was supplemented with additional data from the Glyphs application GlyphData.xml data. These supplemental data included the following: (1) glyph unicode code point in hexadecimal format; (2) glyph production name (when AGL-like nice name included and production name available); (3) glyph nice name (when glyph production name used and nice name available); (4) Unicode short description string. These data were added as a comment-delimited line of text directly above the glyph name.
Glyph names in the Google Fonts Core, Plus, Pro, and Expert glyph sets are released in the same file format at the upstream source files. The data in these files were tested against data contained in the Glyphs application GlyphData.xml file in an automated fashion and the data were modified when invalid glyph names were identified (see above Data Modifications section for details). The glyph name data in each text file were supplemented with additional data from the Glyphs application GlyphData.xml data. These supplemental data included the following: (1) glyph unicode code point in hexadecimal format; (2) glyph production name (when AGL-like nice name included and production name available); (3) glyph nice name (when glyph production name used and nice name available); (4) Unicode short description string. These data were added as a comment-delimited line of text directly above the glyph name.

### Underware Latin Plus data

Glyph names included in the Underware Latin Plus data were parsed and reformatted as individual language/dialect-specific filter list files. Each glyph name was tested against data contained in the Glyphs application GlyphData.xml file in an automated fashion and the data were modified when invalid names were found in the data (see above Data Modifications section for details). The glyph name data in each text file was supplemented with additional data from the Glyphs application GlyphData.xml data. These supplemental data included the following: (1) glyph unicode code point in hexadecimal format; (2) glyph production name (when AGL-like nice name included and production name available); (3) glyph nice name (when glyph production name used and nice name available); (4) Unicode short description string. These data were added as a comment-delimited line of text directly above the glyph name.
Glyph names included in the Underware Latin Plus data were parsed and reformatted as individual language/dialect-specific filter list files. Each glyph name was tested against data contained in the Glyphs application GlyphData.xml file in an automated fashion and the data were modified when invalid names were found in the data (see above Data Modifications section for details). The glyph name data in each text file were supplemented with additional data from the Glyphs application GlyphData.xml data. These supplemental data included the following: (1) glyph unicode code point in hexadecimal format; (2) glyph production name (when AGL-like nice name included and production name available); (3) glyph nice name (when glyph production name used and nice name available); (4) Unicode short description string. These data were added as a comment-delimited line of text directly above the glyph name.

0 comments on commit ae93bab

Please sign in to comment.