Old style figures have been swapped with Lining
m4rc1e opened this issue · 29 comments
This may be pretty disruptive for existing users
@davelab6 I heard you requested this. Shall we go ahead with it?
Oh please leave the osf the default.
I absolutely do not agree with this change! Please revert it.
I also realise that Google Fonts needs the family name to be "EB Garamond" whereas @georgd names his family "EB Garamond 12"
Therefore I propose that @octaviopardo sets up the glyphs file so that 2 families are exported, one with old style figures as default with family name "EB Garamond 12" and one with lining tabular figures as default ""EB Garamond" that GF will onboard.
"we get a lot of users complaining about 'funny looking' numbers."
But in this case, isn't the user wrong?
But in this case, isn't the user wrong?
No.
Google Fonts was launched in 2010 with the aim of wildly heterogenous typefaces and no standards, with the idea that we would gather data on what worked and what didn't and then unify in the future. And in 2017, here we are, and this is one of the things that will be unified.
I see the argument that a classical Garamond revival like this would prefer old style figures as defaults.... @octaviopardo did raise a question with me about this when I requested it, and I suggested he check some other garamond defaults to make a more informed decision - and he was surprised to find that the 'gold standard' of garamonds, Adobe Garamond Premiere Pro, does have lining tabular numbers as default.
After the release I will upload a new file with OSF as default :)
...with family name "EB Garamond 12"? This is possible using instance Custom Parameters, there is some glyphs switcheroo setting for it.
Well, I'm just an interested bystander and in no way or no position to correct you on that.
It's just that some parts of typography always struck me as "trust the designer more than the reader". Not overall, but in instances. After all, typecutters shaped our perception of type in the first place.
PS: sometimes it's in the name. "old style" sound always a bit negative to me. I like the German name "Minuskelziffern", translating to 'lowercase figures', and indeed, those figures typically pair better with lowecase letters…
PPS: Sorry for the OT…
All good, german typography words are cool :)
trust the designer more than the reader
I trust Robert Slimbach ;)
Granted ;)
Sorry for the Off-Topic, but at least it's not that far off from the actual topic here :)
Vollkonrn typeface offers not only lining and old style figures, but also small caps figures. I think it's a cool feature because it covers all scenarios.
@octaviopardo I'll be adding a number swapper inside the source files. No need to do this.
pros know that they can find what they want in the font, because they are pros and know how to activate them
So how would one activate old style figures?
So how would one activate old style figures?
@vyp By activating the corresponding OpenType tag, which in this case is "onum". [My second off-topic on this thread, but anyway.] On LibO 5.3 and later, you just need to attach to the font name a colon followed by the tag, something like
Font Name:+onum
It's also possible to use these tags (on other ways, though) on html and, of course, XeTeX, LuaTeX and co.
Thank you @RGB-es. I found that my question was oversoon as I found answers to my question for html (css) and luatex by searching for it. Sorry for the noise, I didn't know it was simple.
@davelab6 I still don’t agree with this change — for years, we’ve been reading typography books that tell us we should use old style figures in running text and that lament at the same time that a normal user not able to access pro tools can’t do so. With EB Garamond I wanted to provide a font where everybody could use old style figures.
Yet, I see that you don’t want to discuss this so I’ll accept that you want to deliver the fonts with tabular lining features as default. However, as you told this was all about the user I’d prefer the sources to continue with oldstyle figures as default, so yesterday I asked Octavio if it was possible to switch the sources back and use the procedure you proposed for a second font version when you generate the fonts for Google Fonts.
Once I release the next version I will also produce one version with the figures as they were before!
@georgd sorry I didn't make time to discuss this. I discussed it with some other projects too, and I'm persuaded that lining proportional figures ought to be the uniform default in the GF collection. I appreciate that you want to have the sources and your distribution have the default numerals as old style, and I'm happy for Octavio to do that as long as the build process for GF automatically swaps the defaults (which is easy to set up in GlyphsApp.)
cc @m4rc1e
@davelab6 thanks for answering. Please clarify: in the first post you said lining tabular should be default, in your last it's lining proportional. Which one is it now?
@octaviopardo please don't bother with producing a second version. I have thought a lot about it and I came to the conclusion that, although I still think it's stupid to displace the old style figures, I don't think it's worth the troubles with two different versions of the same font.
@davelab6 Is it possible to get old style numerals via Google Fonts? I mean…
@import url('https://fonts.googleapis.com/css?family=EB+Garamond:400');
body {
font: 16px 'EB Garamond', serif;
font-variant-numeric: oldstyle-nums;
}
But that doesn't work at the moment — you'll still see lining digits.
https://blog.bramp.net/post/2018/01/21/google-font-features/
AFAICT Google Fonts' distributed fonts does not support OpenType features, nor variants with them activated. You'll have to obtain the release from this repo and serve them yourself.