Where are the lining numerals?

[dandv]

The README says "It is a display face that features both old style and lining numerals".

I discovered Raleway via Google Fonts, but I can only see the old style fonts

[adrientetar]

@dandv You need to enable OpenType lining numerals.

[dandv]

@adrientetar: Interesting. How can I do that?

[adrientetar]

@dandv It depends on the applications and in fact needs application support.

font-feature-settings in browsers, Adobe apps should also support that in the character selection as well as Microsoft Word 2010+ – see here at the bottom.

[iby]

True… but being one of the most popular Google fonts with Safari not supporting this yet it's kind of a problem. Raleways absolutely kicks ass, but jumpy numerals as it seems isn't many's favourite feature.

Wouldn't it be better to keep the old style as a customisable option and use aligned numerals by default? Things evolve, things get better, people who care about their typography won't have problems with a little maintenance if they really want to use the old style. Pretty sure of that.

[zkirill]

Raleway is an absolutely incredible piece of art but I really need to use lining numerals in the browser. The following doesn't seem to work.

font-feature-settings: 'lnum';
-moz-font-feature-settings: 'lnum=1';
-ms-font-feature-settings: 'lnum';
-webkit-font-feature-settings: 'lnum';
-o-font-feature-settings: 'lnum';

[iby]

@zkirill the right way to make this work is to use font-feature-settings: "lnum" 1; with the right prefixes, but many browsers are still ignoring this…

[zkirill]

@ianbytchek Thank you! Still can't get it to work. :smiley: Yes, the browser support table for font-feature-settings looks pretty grim.

[luisrudge]

any news on this? I can't do this work with chrome/safari :(

[iby]

It works alright in OS X in Chrome and Safari, but not in Windows the last time I checked.

[luisrudge]

oh, that sucks :( I love this font, but those misaligned numbers SUCK big time.

[cssobral2013]

Update: I made a version that has lining numerals by default, so I virtually solved this problem. Check out at: https://github.com/cssobral2013/rising-sun Cheers!

[h-ibaldo]

I also made a version of Raleway with lining numerals, and it's as easy to use as a Google Font: you can embed into your website with a single line of code. Check it here: https://h-ibaldo.github.io/Raleway_Fixed_Numerals/

[ghost]

A bug given as a feature.

[h-ibaldo]

Why would you call it a bug @atilkan? Text firgures are very useful. I believe the problem most people have with Raleway numerals is that, being it such a great display font, that works so well in uppercase titles, the text figures, designed to be used with lowercase text, look out of place, or unaligned: they're not, they have x height, ascenders and descenders, just like the lowercase alphabet. Another problem I faced more than once is while using Raleway for pricing layouts.

Anyway, the Rawline font was created to fix this: https://h-ibaldo.github.io/Raleway_Fixed_Numerals/

[ethangromet]

Thank you Rawline!!!! :)

[ghost]

@h-ibaldo As you said, there is something to fix. I call it bug. You can call it Santa Cruz.

[dandv]

It's a matter of style whether misaligned numerals are a bug or feature - see http://ux.stackexchange.com/questions/54740/what-is-the-appeal-of-old-style-numbers-and-why-do-modern-fonts-still-include-th

[iby]

The matter of style is what you chose to use. Default option is a matter of common sense. Quoting the most popular answer from that discussion:

There are fonts that support both old style and modern numbers. These fonts can easily be used for title, paragraph, table and graph text.

Since we don't live in old times good sir, it feels more appropriate to have modern numbers as a default option – common sense. All that aside, every major browser including Safari already supports font-feature.

[dandv]

I also hate the old style. That's why I asked that question on UX.SE and filed this issue. If I were a fonts dictator, I'd ban old style numerals, those ligatures that combine "f" with a following "i", fonts whose "l" looks indistinguishable from "I", "O" from "0" etc.

[iby]

@dandv if you were a font dictator I'd totally vote for you and pray on your barbarian regime and repressions against liberalistic ligature freedoms! :heart_eyes:

[stevenvachon]

For this feature to work with web fonts generated/minified with tools such as fontsquirrel.com, be sure to either flatten the style set(s) in permanently or not remove them. Otherwise, the CSS setting won't work.

Also, the shorthand font-variant-numeric: lining-nums is better.

[jwvanderbeck]

What about using these outside of a web context? For example I want to use it in a game using Unity where there is no option for enabling such advanced font features as more font heavy programs would have.

[alerque]

@jwvanderbeck First of all, please complaint to Unity. It's bad enough that as recently as a few years ago (as shown in comments above) browsers were still catching up. It's unacceptable that desktop software that draws text wouldn't give you access to this. It isn't "advanced" features — we're not even talking about variable fonts here, this is a pretty basic selector.

After you've complained to Unity I suggest you use one of many tools that are available to take an OTF or TTF font and generate another OTF or TTF with whatever features you want enabled or disabled by default and spoon feed that to you app. This is the standard way of getting modern font features into legacy apps.

[alerque]

By the way I'm leaving this open because it's something I'll look into when generating this font with Fontship ... the potential number of feature combinations that could be generated for legacy usages is quite large, but if we're automating it... at the very least maybe we'll have a command to generate your own font instances. Note as mentioned above you can already do this with other tools...

[alerque]

Here is a sample showing old-style and lining numbers from the 4.100 release.

SILE test code

```sile \begin{document} \script[src=packages/grid] \font[family=Raleway,size=40pt] \grid[spacing=1ex] \grid:debug \font[features=+onum]{Raleway +onum 0123458789} \font[features=+lnum]{Raleway +lnum 0123458789} \end{document} ```

Google Fonts does not support OpenType feature selection through their API at all. As published from this repository webfont builds are included. If you host them yourself you'll be able to use OT features as desired.

Also track this issue for what will be the easiest way to generate your own instances. There is other tooling out there to take existing fonts and toggle the features, so feel free to go that route too but the official way supported by this project will be generating your own font instances from source using that feature (when it is added to Fontship). Subscribe to that issue if this interests you.