Post by Allan Murray on Jun 18, 2017 17:34:21 GMT -5
OK I figured out that you are using FontForge to check the tables.
I compared the glyphs shown in the coverage table between FontForge and OTMMaster Light, and it appears that FontForge is not displaying all of the glyphs:
I will do some further checks with Type 3.2 (specifically the output structure of the coverage table), but I think this appears to be a FontForge issue?
UPDATE: I have identified a small error in the output of the coverage table for contextual lookups. This was not apparent in DTL OTMaster Light, TrueTypeViewer and does not even appear to affect the operation of the font (in InDesign etc). But has shown up in FontForge (note that the glyphs are actually in the coverage table, but some index values are incorrect). I will issue an update asap.
Post by Allan Murray on Jun 18, 2017 16:33:44 GMT -5
What application are you using there to examine the feature tables?
I used your ORDN .feax script in a test font (with all the required glyphs present) and the output font seems to be fine.
I am using DTL OTMaster Light to examine the output tables (which is a very useful free application for doing this, by the way) fontmaster.nl/
Couple of thoughts: - Are you also including other .feax features? As a test, try outputting with just the ORDN to eliminate the possibility of interference/overflow from the other features. - Have you tried the output font in InDesign or other application to see if the features are actually working?
Post by Allan Murray on Jun 17, 2017 23:04:38 GMT -5
There are two possibilities that I can think of: 1. You have mapped the same glyph to two characters 2. You have made a composite glyph - where a glyph is made up of other glyphs
Select one of the characters into the edit window and select information from the glyph menu. Here you will be able to see if the glyph is of type 'composite' or if it is mapped to multiple characters.
If it is composite, use decompose glyph from the glyph menu to fix it.
If it is mapped to multiple characters, use the unmap button on the mapping window to unmap it.
Post by Allan Murray on Jun 14, 2017 14:36:06 GMT -5
Open the font that you want to add glyphs to. On the mapping window, click on the small down arrow and select add external font. Select the font that you want to add glyphs from. The glyphs of the font will now appear in the mapping window.
You can right click glyphs and select various options: copy to clipboard, transfer to font (adds glyph to current font), transfer and map (adds glyph to current font and maps it) etc.
Post by Allan Murray on Jun 14, 2017 3:50:03 GMT -5
A new update for Type 3.2 has been released - Window 3.2.043.
This includes two major new features:
- Glyph validation window (full, demo and light versions) - allows checking of glyphs for common errors and potential issues. Full and demo versions also have: an auto-repair option which will fix most issues, and the ability to run validation over multiple glyphs using an action script.
- Support for contextual OpenType features (full and demo versions). For example, it is now possible to implement features of the form:
SUB one s' t' by s_t
Here the glyphs s and t are replaced by the ligature glyph (s_t), but only when they are preceded by the glyph one.
A new .feax file called Fractions is included in the update which uses contextual substitution.