Bureaucrats, content-moderator, emailconfirmed, Administrators (Semantic MediaWiki), Curators (Semantic MediaWiki), Administrators, threadmoderator
85,404
edits
User talk:Wildheart7: Difference between revisions
From Tardis Wiki, the free Doctor Who reference
→signature
| Line 55: | Line 55: | ||
::A little word of caution about font families. In high web design theory, you should create what's called a "font stack", rather than including only one family. The chances of most people actually having Consolas on their sstem is quite small. (About a quarter of Windows users don't have the font installed. But 75% of Mac users don't have it installed. And Linux/Ubuntu users don't even have Consolas available to them at all.) So you should create a list of alternative fonts that are somewhat close to what you want. Peoples' browsers will then try each of the fonts, in order, until it finds one it can use. Click [http://coding.smashingmagazine.com/2009/09/22/complete-guide-to-css-font-stacks/ here] for a good overview of the concept, and [http://www.codestyle.org/servlets/FontStack here] for a free font stack generator that tells you the probability that your font stack will result in a font that people actually have on their systems. (On my system, incidentally, your signature is just falling through to the random generic font of Tahoma.) {{user:CzechOut/Sig}} <span style="{{User:CzechOut/TimeFormat}}">'''20:57:19 Sat '''09 Jul 2011 </span> | ::A little word of caution about font families. In high web design theory, you should create what's called a "font stack", rather than including only one family. The chances of most people actually having Consolas on their sstem is quite small. (About a quarter of Windows users don't have the font installed. But 75% of Mac users don't have it installed. And Linux/Ubuntu users don't even have Consolas available to them at all.) So you should create a list of alternative fonts that are somewhat close to what you want. Peoples' browsers will then try each of the fonts, in order, until it finds one it can use. Click [http://coding.smashingmagazine.com/2009/09/22/complete-guide-to-css-font-stacks/ here] for a good overview of the concept, and [http://www.codestyle.org/servlets/FontStack here] for a free font stack generator that tells you the probability that your font stack will result in a font that people actually have on their systems. (On my system, incidentally, your signature is just falling through to the random generic font of Tahoma.) {{user:CzechOut/Sig}} <span style="{{User:CzechOut/TimeFormat}}">'''20:57:19 Sat '''09 Jul 2011 </span> | ||
:::Format for font families is straightforward. It's just a matter of listing them, separated by commas. I've taken the liberty of building a bit of a font stack for you. It'd look something like this: | |||
::::font-family: Consolas, | |||
::::Monaco, | |||
::::'Bitstream Vera Sans Mono', | |||
::::'Nimbus Mono L', | |||
::::monospace; | |||
:::The thing about Consolas that I gather you like about Consolas is that it's monospace and that it has a line through zeros. Monaco does the samething for 99.5% of all Mac users, so they're taken care of. It also picks up a sliver of Windows and Linux users. Bitstream Vera Sans Mono is, I think, the same thing for Linux users, although it's a little less ubiquitous, so you need Nimbus Mono L in there to round out the Linux guys. This leaves you with about 17% of all Windows users to take care of, which I guess if I weren't trying to do this in a hurry, I'd be able to figure out. But, I'm just gonna let them fall through to any old monospace font, since you don't actually have a zero in your name anyway. | |||
:::So there ya go. Note that the families don't ''have''to be on separate lines. I just did that for clarity. You can certainly get away with:<pre><span style="font-family:Consolas,Monaco,'Bitstream Vera Sans Mono','Nimbus Mono L',monospace;">Enter text here</span> </pre>Also, you ''can'' put single quotes around the one-word fonts, but you don't have to. The final, generic font (monospace), should probably not go in single quotes. I'm honestly not sure if it would hurt things, but I've never seen it done. Finally, observe how the final bit of punctuation is a semi-colon. That lets the system know when the definition of the font-family is over. You can put additional styling elements after that, such as font-size, color, whatever, but each stylistic instruciton must be separated from the next by a semi-colon. {{user:CzechOut/Sig}} <span style="{{User:CzechOut/TimeFormat}}">'''22:43:44 Sat '''09 Jul 2011 </span> | |||
