shadowfacts/fonttools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

a few more should > must

Browse Source
This commit is contained in:
Colin M. Ford 2023-11-28 22:07:55 -05:00 committed by GitHub
parent 67f858b598
commit bc17e738f0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Doc/source/designspaceLib/index.rst
View File

@ -137,7 +137,7 @@ be defined in the ``public.fontInfo`` lib. Checking validity of the data using
A tool generating the font should copy the font info directly from the A tool generating the font should copy the font info directly from the
``public.fontInfo`` lib item to the instance or the variable font, superceding ``public.fontInfo`` lib item to the instance or the variable font, superceding
all other settings. All info **not** supplied in ``public.fontInfo`` should be all other settings. All info **not** supplied in ``public.fontInfo`` must be
inherited from the name attributes in the ``<instance>`` or ``<variable-font>`` inherited from the name attributes in the ``<instance>`` or ``<variable-font>``
elements (first) and the UFO font info from the source at the origin (second). elements (first) and the UFO font info from the source at the origin (second).
Absence of a key from the ``public.fontInfo`` lib does **not** mean a that piece Absence of a key from the ``public.fontInfo`` lib does **not** mean a that piece
@ -145,7 +145,7 @@ of font info should be interpreted as being undefined unless it is also left
undefined in the other locations. In the case of information in ``public.fontInfo`` undefined in the other locations. In the case of information in ``public.fontInfo``
conflicting with supplied name strings in the ``<instance>`` or ``<variable-font>`` conflicting with supplied name strings in the ``<instance>`` or ``<variable-font>``
elements, or the info supplied from the source at the origin, the data in elements, or the info supplied from the source at the origin, the data in
``public.fontInfo`` should supercede that information because it is understood ``public.fontInfo`` must supercede that information because it is understood
that the designer is using ``public.fontInfo`` to gain more granular control that the designer is using ``public.fontInfo`` to gain more granular control
over the resulting font. over the resulting font.