You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Importing the Display into the Libre Caslon Text GlyphsApp source
I suspected that the baseline wouldn't change in InDesign if the fonts were exported from the same GlyphsApp source. So, I imported LC Display into the LC Text source file, then exported these as static fonts.
Unfortunately, InDesign is computing the text box sizing based on the height of the lowercase /d in each font style ... so the baseline does shift when the style is changed.
Additionally, putting LC Display into the GlyphsApp source file prevents successful FontMake exports, even though I have only set up Text instances.
As a side-effect, the imported Display seems to lose its former kerning between /v and /e.
However, for now, my objective is simply to make the text styles publishable. So, I'll keep the Display out of the Text GlyhpsApp source, then fix these issues in the future.
The text was updated successfully, but these errors were encountered:
From my documentation on experiments:
Importing the Display into the Libre Caslon Text GlyphsApp source
I suspected that the baseline wouldn't change in InDesign if the fonts were exported from the same GlyphsApp source. So, I imported LC Display into the LC Text source file, then exported these as static fonts.
Unfortunately, InDesign is computing the text box sizing based on the height of the lowercase /d in each font style ... so the baseline does shift when the style is changed.
Additionally, putting LC Display into the GlyphsApp source file prevents successful FontMake exports, even though I have only set up Text instances.
As a side-effect, the imported Display seems to lose its former kerning between /v and /e.
However, for now, my objective is simply to make the text styles publishable. So, I'll keep the Display out of the Text GlyhpsApp source, then fix these issues in the future.
The text was updated successfully, but these errors were encountered: