Talk:Typography refresh/Font choice/Test

A note about Helvetica Neue on Windows
Interestingly, even if one has Helvetica Neue on Windows, it appears to not get used (tested on both Chrome and Firefox, with Helvetica Neue downloaded from Linotype's website). I've tried adding a variety of other font-families as well to see if maybe it was just named differently, but each time the browser kept insisting on using Arial. I was able to finally get it to appear when adding the following CSS as well, but we cannot ensure the exact name of the font the end user has (especially since it is likely different on Windows vs Mac), so I do not think that this is a workable solution; more of a continuation of research into why it isn't appearing: @font-face { font-family: HelveticaNeue; src: local("HelveticaNeueLTStd-Roman"); } Again, I do not believe that the above solution is what we should use to get it to appear on Windows (for reasons already mentioned), it is just what worked for me. If someone knows where I can further go digging into why it isn't simply appearing by default, I'd love to hear your thoughts. -- Skiz zerz  02:13, 8 March 2014 (UTC)


 * The above wouldn't work for me, as I have the Com .ttf version, so I would need  (You probably have the Std type1 version.) Linotype has several versions for Windows, both type1 and truetype, each with their own highly inconsistent font-family names. I have "Helvetica Neue" mapped to "HelveticaNeueLT Com 55 Roman" in my FontSubstitutes in the registry, which is why I do see the font. (Except in Opera Presto, which ignores the FontSubstitutes in Windows.)
 * "Helvetica Neue" is primarely intended for Apple products, which I guess all do have the corect font-family name. Bottom line is, "Helvetica Neue" will never work, nor was it intended to work on Windows. — Edokter  ( talk ) — 12:38, 8 March 2014 (UTC)

'serif' and 'sans-serif'
I have two fonts literally titled 'sans-serif' and 'serif', and I think they're different than the browser default in some of these in Mozilla Firefox (Ubuntu). What should I put where these appear, or should I just not enter anything where these two fonts are the ones being rendered. I think these fonts are installed with GIMP, just if that's relevant. --GeorgeBarnick (talk) 23:43, 11 March 2014 (UTC)

Testing serif
, you were really fast adding serif tests. ,, , , , , , , , your help is welcome! Thank you for the interesting feedback.--Qgil (talk) 01:37, 12 March 2014 (UTC)

Monospace
Re: Talk:Typography refresh - I've added a test set at Typography refresh/Font_choice/Test (but feel free to overhaul it as I might've made mistakes, hence haven't pinged everyone yet). –Quiddity (talk) 19:45, 16 March 2014 (UTC)
 * I have reservations about grputlands suggestions; I don't really know what his goal is. He lists all types of Courier variants, with Consolas thrown in for... I don't know why! Then has Courier before Courier New, which means (for those without Consolas at least), Internet Explorer regresses to using the bitmap Courier font. I don't think this should be considered a valid option. — Edokter  ( talk ) — 20:56, 16 March 2014 (UTC)
 * Ok, makes sense, I've removed that column. (It was just something I stumbled across whilst reading).
 * Feel free to add/edit/overhaul the entire section, however would be most helpful. Ping the people when it's ready for more input? (Or just let me know if it's not useful at all. 'twas just a thought :) –Quiddity (talk) 06:39, 17 March 2014 (UTC)
 * On my system at least (but also at en:Liberation fonts), the font is named "Liberation Mono" rather than "Liberation Sans Mono". Chromium apparently does its own thing, but Firefox (which uses the system font fallback mechanism) doesn't find it using the latter. Anomie (talk) 14:05, 17 March 2014 (UTC)
 * Totally my bad! Fixed the font stack, please retest. — Edokter  ( talk ) — 15:37, 17 March 2014 (UTC)