Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Quick Links
Categories
- 3.1K All Categories
- 5 Introductions
- 2.5K Typeface Design
- 400 Font Technology
- 809 Technique and Theory
- 334 Type Business
- 309 Type Design Critiques
- 422 Type Design Software
- 29 Punchcutting
- 65 Lettering and Calligraphy
- 41 Technique and Theory
- 24 Lettering Critiques
- 246 Typography
- 173 History of Typography
- 73 Education
- 362 Announcements
- 60 Events
- 75 Job Postings
- 105 Type Releases
- 121 Miscellaneous News
- 183 About TypeDrawers
- 41 TypeDrawers Announcements
- 79 Suggestions and Bug Reports
mergefonts and OTFs
Rainer Erich Scheichelbauer
Posts: 153
I need help with mergefonts.
I am trying to exchange the k in src.otf for the k from k.otf. This is the command line I came up with:
The glyphalias.txt file reads as follows:
I receive the following output:
And a new file called output.otf is indeed generated, but it is not a valid OTF. It doesn’t start with the OTTO header. I posted a screenshot of the file opened in TextMate: http://cl.ly/image/3X0e2J1j0p1P
Can someone enlighten me:
1. How do I get mergefonts to output OTFs?
2. And what file format is it in now?
I am trying to exchange the k in src.otf for the k from k.otf. This is the command line I came up with:
mergefonts -gx k output.otf src.otf glyphalias.txt k.otfThe glyphalias.txt file reads as follows:
mergeFonts
k k
I receive the following output:
mergefonts: --- src.otf
mergefonts: (cfr) /BlueScale too large/small (ignored)
mergefonts: --- k.otf
mergefonts: (cfr) /BlueScale too large/small (ignored)
And a new file called output.otf is indeed generated, but it is not a valid OTF. It doesn’t start with the OTTO header. I posted a screenshot of the file opened in TextMate: http://cl.ly/image/3X0e2J1j0p1P
Can someone enlighten me:
1. How do I get mergefonts to output OTFs?
2. And what file format is it in now?
0