Preloaded, User-Created, and Drag-and-Drop Glyph Mappings using Formulas

Got a request? Post it here. Please do not post bug reports here.
Post Reply
outofstepfontco
Posts: 85
Joined: Sun Feb 22, 2015 4:35 pm
Contact:

Preloaded, User-Created, and Drag-and-Drop Glyph Mappings using Formulas

Post by outofstepfontco »

Hi everyone
Looking to minimize filesize on some old fonts and doing a lot of glyph mapping using Formulas.

For example, making all uppercase A variations (Aring, Agrave, Aacute, etc) map to A 0065. All uppercase E variations map to E. Currently shift+ and ctrl+ clicking glyphs and then hitting the Formula button, setting them equal one glyph at a time.

Why not have user created maps that I can activate with one button? Here are some great ones:
- all uppercase letters to the basic 26 uppercase
- all lowercase letters to the basic 26 lowercase
- basic 26 lowercase letters get mapped to the uppercase version

Why not set the formula for a selection of glyphs by dragging and dropping them onto the glyph that they are to be set equal to?

I tried to set up an FCP file as a template, but it means editing the Font Info and Metrics every time I use it.

Hope this is something workable.

Have a good one,
FC12.0 Professional
Bhikkhu Pesala
Top Typographer
Top Typographer
Posts: 9114
Joined: Tue Oct 29, 2002 5:28 am
Location: Seven Kings, London UK
Contact:

Re: Preloaded, User-Created, and Drag-and-Drop Glyph Mappings using Formulas

Post by Bhikkhu Pesala »

Why would anyone want to map all accented vowels to their base glyph? :?

To copy all lower case mappings to uppercase, just use copy and paste special.
My FontsReviews: MainTypeFont CreatorHelpFC13 Pro + MT10.0 @ Win10 2004 build 19041.867
outofstepfontco
Posts: 85
Joined: Sun Feb 22, 2015 4:35 pm
Contact:

Re: Preloaded, User-Created, and Drag-and-Drop Glyph Mappings using Formulas

Post by outofstepfontco »

Bhikkhu Pesala wrote: Thu Feb 04, 2021 7:25 am Why would anyone want to map all accented vowels to their base glyph? :?
I would be happy to answer that question for you. And not just vowels, but all accented characters:
  • Because for quite a few glyphs, Complete Composites won't map anything without diacritics
  • Because not all clients pay for diacritics
  • Because not all fonts are profitable enough to develop and align diacritics
  • Because it reduces the amount of work required to stop .notdef showing up in non-English languages
  • Because at least one of your competitors (Fontself) has it as the default setting in their software: all accented glyphs are mapped to the source glyph unless you specifically design for the accented glyph. Assume they did their own research.
I hope that helps.
FC12.0 Professional
Post Reply