Curious how everyone determine their standard glyph/character set for a font.
I also need one for myself, but don't know how to determine them.
For example in Fontlab: ISO 8859-1 Latin 1, Windows 1252 ANSI, MacOS Roman, OpenType Standard, etc.
Would you mind to share yours?
Thank you.
0
Comments
I totally forgot about Google Fonts! I've been there before. I think this is a good starting point.
Here's the link
Hope this helps others too.
So, what's your suggestion for that? As I haven't make any font with that character yet.
Set of files, matches the Adobe standard character sets as of 2014, with an update in 2017. May not be up to date with the very latest currency symbols and tweaks, though.
For the basic encoding, more or less I decided to include all that is grouped the "Opentype Standard" Encoding.
Then you can turn to Unicode Pages and see what is more relevant for you. The Controls and Basic Latin and Latin 1 Supplement ranges are already covered by the "Opentype Standard", then you might decide how much of Latin Extended-A and B you want to include, depending on the intended language coverage of your basic versions.
I added the most important Combining Diacritical Marks (0300-036F), selected glyphs from General Punctuation (2000-206F), the numerals from Superscripts and Subscripts (2070-209C), for now just the Euro from the Currency Symbols range (20A0-20BF) but I might add some, and so on.
I think arrows can be useful, so you could consider to add the basic ones from 2190-21FF, and so on… Just parse the various typographic signs/symbols ranges and see what you find more relevant to include in your standard basic set.
Then one can create more extended sets with specific or more complete uses in mind.
I adapted the file to my needs: Latin European languages, Win and/or Word alt-codes, Fontlab 7 names.
I used the "Bulletproof" and "Alphabet Type" apps (Windows 10 for me) to help me fine tune the needed characters.
At the moment, I create fonts supporting: Afrikaans, Albanian, Alsatian, Aromanian, Asturian, Breton, Catalan, Croatian, Czech, Danish, Dutch, English, Esperanto, Estonian, Finnish, French, Gagauz, German, Hungarian, Icelandic, Indonesian, Irish, Italian, Latin, Latvian, Lithuanian, Norwegian, Polish, Portuguese, Romanian, Scottish Gaelic, Serbian, Slovak, Slovenian, Spanish, Swedish, Tagalog, Turkish, Walser German, West Frisian, Zazaki, Zulu.
(Not all exactly European)
I'm looking forward to support Onĕipŏt!
https://fontmeme.com/alt-codes-shortcuts-html-codes-for-special-characters/
where you find also the html and Mac codes
I don't care if they steal my fonts (it's a risk!) They are already pirated!
https://bulletproof.italic.space/
https://www.alphabet-type.com/tools/
But as has been discussed many times on this forum, there are some inefficiencies and duplicated data in the original OpenType CFF format. Which is why CFF2 was invented: there was a need to support variable fonts in OpenType CFF anyway, so Adobe took it as also being an opportunity to clean up the cruft in the OpenType CFF format. CFF2 removes some things from CFF that are also in the main table-based part of OpenType, outside the CFF/CFF2 table.
I think this was a great idea… in principle. But the lack of backwards compatibility for non-variable CFF2 fonts, plus the fact that CFF2 was not ready nearly as fast as the variable font extensions to TTF (I assume at least partly because of these optimizations), has meant that variable fonts other than Adobe’s are nearly all TTF based at this point, and pretty nearly nobody is creating non-variable fonts in OpenType CFF2 format.
(I am curious as to whether even Adobe is issuing fonts routinely in this format.)
I join the new version and hope it will help somebody.
It seems "two different ways" is an optimistic view. I should say "many different ways".
This is why I mentioned the "usual names"(?) and the ones in Fontlab.
A lot of the standard names are cryptic and give you no clue as to what they represent (e.g., "afii10032" is the cyrillic "O") and are hard to remember. Glyphs' "friendly names" substitutes readable names for the convenience of the type designer. These are changed to standard names when a font is generated.
Other font editors use the standard names, or allow you to make up your own as long as they are changed to standard names somehow in the final fonts. I know I did something like this when I used RoboFont, but don't remember the details.
«Not all arrows are created equal», the evil one said.
May I present, circleDividedByHorizontalBarAndTopHalfDividedByVerticalBar, downHarpoonWithBarbLeftBesideDownHarpoonWithBarbRight, and rightTwoHeadedArrowWithTailWithDoubleVerticalStroke:
https://github.com/LettError/glyphNameFormatter