Full name for regular style should not require including “Regular”
See original GitHub issueWith Mada-Regular.ttf I get:
ERROR [FULL_FONT_NAME:WINDOWS] entry: expected 'Mada-Regular' or 'Mada Regular' but got 'Mada'
But the spec says:
Full font name; a combination of strings 1 and 2, or a similar human-readable variant. If string 2 is “Regular”, it is sometimes omitted from name ID 4.
Issue Analytics
- State:
- Created 7 years ago
- Comments:37 (34 by maintainers)
Top Results From Across the Web
MLA General Format - Purdue OWL
Whatever font you choose, MLA recommends that the regular and italics type styles contrast enough that they are each distinct from one another....
Read more >MLA Document Formatting | English Composition I
General MLA Formatting Rules. Font: Your paper should be written in 12-point text. Whichever font you choose, MLA requires that regular and italicized...
Read more >Regular expression syntax cheatsheet - JavaScript | MDN
Capturing group: Matches x and remembers the match. For example, /(foo)/ matches and remembers "foo" in "foo bar". A regular expression may have...
Read more >PHP Coding Standards - WordPress Developer Resources
Brace Style; Declaring Arrays; Multiline Function Calls ... Closures (Anonymous Functions); Regular Expressions; Don't extract(); Shell commands.
Read more >Regular expression - Wikipedia
They came into common use with Unix text-processing utilities. Different syntaxes for writing regular expressions have existed since the 1980s, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I can’t find any links to the old version on MS site, but the change log says name id 4 description was updated in version 1.9 in 2009, so here is a link from the wayback machine. Interestingly the exception is mentioned is for CFF fonts, so even if we were to follow the old spec, this should be done for fonts with CFF table only not the ones with glyf table (fontbakery does not even seem to support fonts with CFF table).
@felipesanches looks good