Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OperatorMonoSSm-Medium is missing ligatures #77

Closed
jtourlamain opened this issue Nov 13, 2018 · 2 comments
Closed

OperatorMonoSSm-Medium is missing ligatures #77

jtourlamain opened this issue Nov 13, 2018 · 2 comments

Comments

@jtourlamain
Copy link

I was able to build the OperatorMonoSSm-Book font, but the OperatorMonoSSm-Medium gives warnings during build. Ligatures like "->" are missing in the font.

On WSL I used

Building OperatorMonoSSmLig-Medium
Dumping "./original/OperatorMonoSSm-Medium.otf" to "./original/OperatorMonoSSm-Medium.ttx"...
Dumping 'GlyphOrder' table...
Dumping 'head' table...
Dumping 'hhea' table...
Dumping 'maxp' table...
Dumping 'OS/2' table...
Dumping 'name' table...
Dumping 'cmap' table...
Dumping 'post' table...
Dumping 'CFF ' table...
Dumping 'GPOS' table...
Dumping 'GSUB' table...
Dumping 'hmtx' table...
Dumping 'DSIG' table...
Reading original font file ./original/OperatorMonoSSm-Medium.ttx
Patching names
Patching glyphs
Patching gpos
Patching gsub
Patching hmtx
Patching charstrings
Writing ligature font file ./build/OperatorMonoSSmLig-Medium.ttx
Done
Compiling "./build/OperatorMonoSSmLig-Medium.ttx" to "./build/OperatorMonoSSmLig-Medium.otf"...
Parsing 'GlyphOrder' table...
Parsing 'head' table...
Parsing 'hhea' table...
Parsing 'maxp' table...
Parsing 'OS/2' table...
Parsing 'name' table...
Parsing 'cmap' table...
Parsing 'post' table...
Parsing 'CFF ' table...
Parsing 'GPOS' table...
Parsing 'GSUB' table...
Parsing 'hmtx' table...
Parsing 'DSIG' table...
WARNING: GSUB/GPOS Coverage is not sorted by glyph ids.
WARNING: GSUB/GPOS Coverage is not sorted by glyph ids.
WARNING: GSUB/GPOS Coverage is not sorted by glyph ids.
WARNING: GSUB/GPOS Coverage is not sorted by glyph ids.
WARNING: GSUB/GPOS Coverage is not sorted by glyph ids.
WARNING: GSUB/GPOS Coverage is not sorted by glyph ids.
WARNING: GSUB/GPOS Coverage is not sorted by glyph ids.

end of output in OperatorMonoSSmLig-Medium.ttx:

<DSIG>
        <!-- note that the Digital Signature will be invalid after recompilation! -->
        <tableHeader flag="0x0" numSigs="0" version="1"/>
    </DSIG>
@kiliman
Copy link
Owner

kiliman commented Nov 13, 2018

Depending on the editor you use, some ligatures won't work, especially those that start with a hyphen.

See tonsky/FiraCode#259 and tonsky/FiraCode#422 for details.

@jtourlamain
Copy link
Author

@kiliman thanks for your quick feedback. I didn't know it was editor dependend. I thought that all the warnings meant that some ligatures where missing during build

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants