The following glyph name modifications were made to the upstream source as part of the work in this project:
- glyph name
H18533changed toblackCircle - glyph name
H18543changed toblackSmallSquare - glyph name
H18551changed towhiteSmallSquare - glyph name
H22073changed towhiteSquare - glyph name
Ifrakturchanged toI-fraktur - glyph name
Rfrakturchanged toR-fraktur - glyph name
SF010000changed toboxLightDownAndRight - glyph name
SF020000changed toboxLightUpAndRight - glyph name
SF030000changed toboxLightDownAndLeft - glyph name
SF040000changed toboxLightUpAndLeft - glyph name
SF050000changed toboxLightVerticalAndHorizontal - glyph name
SF060000changed toboxLightDownAndHorizontal - glyph name
SF070000changed toboxLightUpAndHorizontal - glyph name
SF080000changed toboxLightVerticalAndRight - glyph name
SF090000changed toboxLightVerticalAndLeft - glyph name
SF100000changed toboxLightHorizontal - glyph name
SF110000changed toboxLightVertical - glyph name
SF190000changed toboxVerticalSingleAndLeftDouble - glyph name
SF200000changed toboxVerticalDoubleAndLeftSingle - glyph name
SF210000changed toboxDownDoubleAndLeftSingle - glyph name
SF220000changed toboxDownSingleAndLeftDouble - glyph name
SF230000changed toboxDoubleVerticalAndLeft - glyph name
SF240000changed toboxDoubleVertical - glyph name
SF250000changed toboxDoubleDownAndLeft - glyph name
SF260000changed toboxDoubleUpAndLeft - glyph name
SF270000changed toboxUpDoubleAndLeftSingle - glyph name
SF280000changed toboxUpSingleAndLeftDouble - glyph name
SF360000changed toboxVerticalSingleAndRightDouble - glyph name
SF370000changed toboxVerticalDoubleAndRightSingle - glyph name
SF380000changed toboxDoubleUpAndRight - glyph name
SF390000changed toboxDoubleDownAndRight - glyph name
SF400000changed toboxDoubleUpAndHorizontal - glyph name
SF410000changed toboxDoubleDownAndHorizontal - glyph name
SF420000changed toboxDoubleVerticalAndRight - glyph name
SF430000changed toboxDoubleHorizontal - glyph name
SF440000changed toboxDoubleVerticalAndHorizontal - glyph name
SF450000changed toboxUpSingleAndHorizontalDouble - glyph name
SF460000changed toboxUpDoubleAndHorizontalSingle - glyph name
SF470000changed toboxDownSingleAndHorizontalDouble - glyph name
SF480000changed toboxDownDoubleAndHorizontalSingle - glyph name
SF490000changed toboxUpDoubleAndRightSingle - glyph name
SF500000changed toboxUpSingleAndRightDouble - glyph name
SF510000changed toboxDownSingleAndRightDouble - glyph name
SF520000changed toboxDownDoubleAndRightSingle - glyph name
SF530000changed toboxVerticalDoubleAndHorizontalSingle - glyph name
SF540000changed toboxVerticalSingleAndHorizontalDouble
- glyph name
NULLchanged to.null - removed private use area code point glyph name
uniE0FF - removed private use area code point glyph name
uniEFFD - removed private use area code point glyph name
uniF000
- removed
napostrophe.scas this was removed from the upstream data (see discussion in googlefonts/gftools#69)
- removed invalid glyph name
ijacute - removed invalid glyph name
IJacute
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.
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.
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.