Raleway has a full set of lining numbers (that is, numbers that line up) as well as the ranging numbers (that is, numbers that are designed to fit with running text and thus "bounce up and down", also known as oldstyle numerals). If you're mainly using it on the web, you should be able to specify that you want lining figures using the font-feature-settings attribute in your CSS, specifying that you want "lnum" as one of them.

Thank you for the reply. Can you show me exactly what the code would look like. I've googled it, but 'lnum css' turns up almost nothing.

I've tried:

font-feature-settings: "zero";
/* vendor-prefixes */
-moz-font-feature-settings: 'zero=1';
-ms-font-feature-settings: "zero";
-webkit-font-feature-settings: "zero";
-o-font-feature-settings: "zero";

and

font-feature-settings: 'lnum';
/* vendor-prefixes */
-moz-font-feature-settings: 'lnum=1';
-ms-font-feature-settings: 'lnum';
-webkit-font-feature-settings: 'lnum';
-o-font-feature-settings: 'lnum';

neither worked :(

Strange, the latter looks fine to me. (I'm totally not an expert though.) How are your webfonts served? Some of the services will tend to strip out stuff like several sets of numerals for the sake of economy.

Serving from Google.

link href='http://fonts.googleapis.com/css?family=Raleway:500' rel='stylesheet' type='text/css'

Maybe when I call it from the server, I need to specify the lnum as well in some manner...

There's really virtually nothing about this topic by Googling it.

Okay. Luckily someone else had the exact same problem with the same font. I've found the answer on stackoverflow by Googling 'raleway lnum'.

http://stackoverflow.com/questions/17218891/getting-different-figure-typ...

Apparently the feature isn't available when calling from Google. Only when using .otf files. I'll look into it implementing this and reply back.

Hmmm... I give up on this for now. The Raleway .otf I downloaded doesn't have lnum in the .otf. Or maybe it's not required to be in the .otf to use lnum?

OT support is still spotty.

Hi Damian,
Webfonts served by Google Fonts and most other webfonts services are usually sub-setted (that means its optimized, and some glyphs are removed to make the file smaller so it loads faster).

To force Google to send you the entire full file (no subsetting) you have to specify "subsetting=all".
Here is an example on how to do that for the lobster font: http://www.impallari.com/lobster#subsetting
You can do the same for Raleway or any other font.

Once you are getting the full font, in your CSS you need to add this code to activate the lnum feature in all browsers:
font-feature-settings: "lnum"
-moz-font-feature-settings: "lnum"
-webkit-font-feature-settings: "lnum"
-ms-font-feature-settings: "lnum"
-o-font-feature-settings: "lnum"

By the way, the latest Raleway release (v3) a few days ago, also include Italics and Cyrillics. Is available here: http://www.impallari.com/projects/update/100 and will also be available in Google Fonts pretty soon.

It’s strange that you have to specify all glyphs in order to get the few required for one specific feature.

Yep, is strange. But web-developers are very strict about optimization. They optimize everything: css, javascript, etc... even small 1kb gifs icons making sprites files to save http requests. They want the fonts to be compressed in the same way, even if that means removing some glyphs and OT features.

Currently in Google Fonts there are more subsetting options:
- Latin,
- Latin Extended,
- Cyrillic,
- Cyrillic Extended,
- Greek,
- Greek Extended,
- Khmer,
- Vietnamese,
- All (disable subsetting and get the full font).
- Your can also roll your own custom subsets, using the "text=xxxx" parameter.

But they are mostly intended for language support, and not yet for OT features.
As you might know, not all OT features are currently supported by all browsers, but hopefully in the near future they will, and I also hope for the subsetting options to improve in all the webfonts services.

TypeKit only offers 2 options:
- Default (Latin)
- All Characters (subsetting off)

H&JF has done a great job in their service, in particular about the subsetting options. They have an "easy to use" and "easy to understand" interface for selecting which glyphs gets included and which ones gets removed, allowing the user to fine-tune the subsetting optimizations.
http://www.typography.com/cloud/feature-tour/images/ft_characters_1x.png

I don't know what are the subsetting options that the other services offer to their users. But still, all this webfonts thing is still in an early phase, and there is much to improve when looking at the future.

Be advised that Raleway Thin and Extralight uprights still have their usWeight below the Microsoft Madness limit. Might want to bump it up to 250 as in the italics.

Thanks Té.
I've read about that here http://www.adobe.com/devnet/opentype/afdko/topic_font_wt_win.html but so far we never have had any problems regathering that setting, as we only style-link 400 to 700 and not the other weights.
Also, it seems like a Microsoft's Bug to me, and not a bug in the fonts. They should fix their software, we should not break our fonts to support defective apps.

Good luck getting the PTBita to fix that stupidity... At least I know enough to put in that workaround for myself.

Bringing back this old topic.

The character set as shown by google fonts doesn't include non-bobbing numbers, so if I force load all subsets, it will have it?

http://www.google.com/fonts/specimen/Raleway#charset

The term "lining" is preferable to "non-bobbing".

hhp

Back to initial topic - need substitute for Raleway or Google.fonts. Here's the whole deal - template studio I have subscription with, started using it almost everywhere (most new templates), but I need to have Cyrillic in it - google fonts still doesn't have it in Cyrillic, and I don't know how to set the template up in such a way that it would use any other fonts provider. Could anybody help me please? I am quite new to this thing, but can learn quite fast... Thanks in advance.

Yesterday I've uploaded Raleway v3 to Github. GoogleFonts version will be updated soon.

Thank you, PabloImpallari
How much time does it usually takes? Do you know? "Soon" might mean a day, a month, an year... )))

I can't say for sure, for probably the next week or two

Actually, Google didn’t yet offer even Raleway’s italics…

I guess this one https://docs.google.com/forms/d/1w2JOnVv_Vfcg1H_nploj1FRz4LcFsLaFmFkEj50... resubmitted would speed it up, wouldn't it?

Can't tell if I was able to trigger someth, or it was mere coincedence, but this site rules for sure: https://

Next week upgrade is scheduled...