15 Font Specification
| from
www.w3.org/TR/1998/REC-CSS2-19980512 I don't think they are gonna change it interpreted by DGermancss@Real-World-Systems.com |
When a document's text is to be displayed visually, characters
(abstract information elements) must be mapped to abstract glyphs. One or more characters may be depicted by one or more abstract glyphs, in a possibly context-dependent fashion. A glyph is the actual artistic representation of an abstract glyph, in some typographic style, in the form of outlines or bitmaps that may be drawn on the screen or paper. A font is a set of glyphs, all observing the same basic motif according to design, size, appearance, and other attributes associated with the entire set, and a mapping from characters to abstract glyphs.A visual user agent must address the following issues before actually rendering a character:
In both CSS1 and CSS2, authors specify font characteristics via a series of font properties.
How the user agent handles these properties, when there is no matching font on the client has expanded between CSS1 and CSS2. In CSS1, all fonts were assumed to be present on the client system and were identified solely by name. Alternate fonts could be specified through the properties, but beyond that, user agents had no way to propose other fonts to the user (even stylistically similar fonts that the user agent had available) other than generic default fonts.
CSS2 changes all that, and allows much greater liberty for:
CSS2 improves client-side font matching, enables font synthesis and progressive rendering, and enables fonts to be downloaded over the Web. These enhanced capabilities are referred to as 'WebFonts'
In the CSS2 font model, as in CSS1, each user agent has a "font database" at its disposition. CSS1 referred to this database but gave no details about what was in it. CSS2 defines the information in that database and allows style sheet authors to contribute to it. When asked to display a character with a particular font, the user agent first identifies the font in the database that "best fits" the specified font (according to the font matching algorithm) Once it has identified a font, it retrieves the font data locally or from the Web, and may display the character using those glyphs.
In light of this model, we have organized the specification into two sections. The first concerns the font specification mechanism, whereby authors specify which fonts they would like to have used. The second concerns the font selection mechanism, whereby the client's user agent identifies and loads a font that best fits the author's specification.
How the user agent constructs the font database lies outside the scope of this specification since the database's implementation depends on such factors as the operating system, the windowing system, and the client.
The first phase of the CSS font mechanism concerns how style sheet authors specify which fonts should be used by a user agent. At first, it seem that the obvious way to specify a font is by it's name, a single string - which appears to be separated into distinct parts; for example "BT Swiss 721 Heavy Italic".
Unfortunately, there exists no well-defined and universally accepted taxonomy for classifying fonts based on their names, and terms that apply to one font family name may not be appropriate for others. For example, the term 'italic' is commonly used to label slanted text, but slanted text may also be labeled Oblique, Slanted, Incline, Cursive, or Kursiv. Similarly, font names typically contain terms that describe the "weight" of a font. The primary role of these names is to distinguish faces of differing darkness within a single font family. There is no accepted, universal meaning to these weight names and usage varies widely. For example a font that you might think of as being bold might be described as being Regular, Roman, Book, Medium, Semi- or Demi-Bold, Bold, or Black, depending on how black the "normal" face of the font is within the design.
This lack of systematic naming makes it impossible, in the general case, to generate a modified font face name that differs in a particular way, such as being bolder.
Because of this, CSS uses a different model. Fonts are requested not through a single font name but through setting a series of font properties. These property values form the basis of the user agent's font selection mechanism. The font properties can be individually modified, for example to increase the boldness, and the new set of font property values will then be used to select from the font database again. The result is an increase in regularity for style sheet authors and implementors, and an increase in robustness.
CSS2 specifies fonts according to these characteristics:
normal, italic, or
oblique face. italic is a more cursive
companion face to the normal face, but not so cursive as to make it a
script face. oblique is a slanted form of
the normal face, and is more commonly used as a companion face to
sans-serif. This definition avoids having to label slightly slanted
normal faces as oblique, or normal Greek faces as italic.normal glyphs for
lowercase characters or using small-caps glyphs .
A particular font may contain only normal, only small-caps, or
both.On all properties except font-size, 'em' and 'ex' length values refer to the font size of the current element. For font-size, these length units refer to the font size of the parent element. See length units.
properties are used to describe the desired appearance of text in the document.
descriptors, in contrast, are used to describe the characteristics of fonts, so that a suitable font can be chosen to create the desired appearance. See font descriptors.
font-family| Value: | [[ < family-name > | < generic-family > ],]* [ < family-name > | < generic-family > ] | inherit | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Initial depends on user agent , Applies to all elements , Inherited, Percentages:N/A Media:visual | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This property specifies a prioritized list of font family names and/or generic family names. To deal with the problem that a single font may not contain glyphs to display all the characters in a document, or that not all fonts are available on all systems, this property allows authors to specify a list of fonts, all of the same style and size, that are tried in sequence to see if they contain a glyph for a certain character. This list is called a font set .
Example(s):
Text that contains English words mixed with mathematical symbols may need a font set of two fonts, one containing Latin letters and digits, the other containing mathematical symbols. Here is an example of a font set suitable for a text that is expected to contain text with Latin characters, Japanese characters, and mathematical symbols:
BODY { font-family: Baskerville, "Heisi Mincho W3", Symbol, serif }
The glyphs available in the "Baskerville" font (a font that covers only Latin characters) will be taken from that font,
Japanese glyphs will be taken from "Heisi Mincho W3", and the mathematical symbol glyphs will come from
"Symbol". Any others will come from the generic font family "serif".
Monotype corsiva" you MUST use quotes as :
"font-family:Monotype corsiva" | OK |
font-family:"Monotype corsiva" | NG 04/22/04 DGG |
The generic font family will be used if one or more of the other fonts in a font set is unavailable. Although many fonts provide the "missing character" glyph, typically an open box, as its name implies this should not be considered a match except for the last font in a font set.
There are two types of font family names:
serif, sans-serif, cursive, fantasy, monospace.
*
For example:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
<HTML>
<HEAD>
<TITLE>Font test</TITLE>
<STYLE type="text/css">
BODY { font-family: "new century schoolbook", serif }
</STYLE>
</HEAD>
<BODY>
<H1 style="font-family: 'My own font', fantasy">Test</H1>
<P>What's up, Doc?
</BODY>
</HTML>
Example(s):
The richer selector syntax of CSS2 may be used to create language-sensitive typography. For example, some Chinese and Japanese characters are unified to have the same Unicode codepoint, although the abstract glyphs are not the same in the two languages.
*:lang(ja-jp) { font: 900 14pt/16pt "Heisei Mincho W9", serif }
*:lang(zh-tw) { font: 800 14pt/16.5pt "Li Sung", serif }
This selects any element that has the given language - Japanese or Traditional Chinese - and requests the appropriate font.
| Value: | normal | italic | oblique | inherit |
| Initial: | normal Applies to: all elements |
| Inherited: | yes |
| Percentages: | N/A |
| Media: | visual |
font-style property requests normal (sometimes referred to as "roman" or "upright"), italic , and oblique faces within a font family.
Example(s):
normal text in an H1, H2, or H3 element will be displayed with an italic
font. However,
emphasized text (EM) within an H1 will appear in a normal face.
H1, H2, H3 { font-style: italic }
H1 EM { font-style: normal }
| Value: | normal | small-caps | inherit |
| Initial: | normal |
| Applies to: | all elements |
| Inherited: | yes |
| Percentages: | N/A |
| Media: | visual |
In a small-caps font, the glyphs for lowercase letters look similar to the uppercase ones, but in a smaller size and with slightly different proportions. The font-variant property requests such a font for bicameral (having two cases, as with Latin script). This property has no visible effect for scripts that are unicameral (having only one case, as with most of the world's writing systems). Values have the following meanings:
normal not labeled as a small-caps
Example(s):
results in an H3 element in small-caps, with emphasized words (EM) in oblique small-caps:
H3 { font-variant: small-caps }
EM { font-style: oblique }
Insofar as this property causes text to be transformed to uppercase, the same considerations as for 'text-transform' apply.
| Value: | lighter | 100 | 200 | 300 | normal aka 400 | 500 | 600 |bold aka 700 | 800 | 900 | bolder | inherit |
| Initial:normal Applies to:all elements Inherited:yes Percentages:N/A Media: visual | |
The font-weight property specifies the weight of the font. Values have the following meanings:
Example(s):
P { font-weight: normal } /* 400 */
H1 { font-weight: 700 } /* bold */
BODY { font-weight: 400 }
STRONG { font-weight: bolder } /* 500 if available */
Here are some samples: *doesn't seem to be fully implemented in
any browsers<span
style=font-weight:normal>normal</span> <code
style=font-weight:bolder>bolder</code> <code
style=font-weight:lighter>lighter</code> <b>b</b>Child elements inherit the computed value of the weight.
| Value: | normal | wider | narrower | ultra-condensed | extra-condensed | condensed | semi-condensed | semi-expanded | expanded | extra-expanded | ultra-expanded | inherit |
| Initial: normal Applies to: all elements Inherited: yes Percentages: N/A Media: visual | |
The font-stretch property selects a normal, condensed, or extended face from a font family. Absolute keyword values have the following ordering, from narrowest to widest :
| ultra-condensed extra-condensed condensed semi-condensed normal semi-expanded expanded extra-expanded ultra-expanded |
The relative keyword 'wider' sets the value to the next expanded value above the inherited value (while not increasing it above 'ultra-expanded'); the relative keyword 'narrower' sets the value to the next condensed value below the inherited value (while not decreasing it below 'ultra-condensed').
| Value: | <absolute-size> * | <relative-size> | <length> | <percentage> | inherit |
| Initial: | medium |
| Applies to: | all elements |
| Inherited: | yes, the computed value is inherited |
| Percentages: | refer to parent element's font size |
| Media: | visual |
| serif | xx-small | x-small | small | medium | large | x-large | xx-large |
| sans-serif | xx-small | x-small | small | medium | large | x-large | xx-large |
| cursive | xx-small | x-small | small | medium | large | x-large | xx-large |
| fantasy | xx-small | x-small | small | medium | large | x-large | xx-large |
| monospace | xx-small | x-small | small | medium | large | x-large | xx-large |
On a computer screen a scaling factor of 1.2 is suggested between adjacent indexes; ex: the 'medium' font is 12pt, the 'large' font could be 14.4pt. Different media may need different scaling factors. Also, the user agent should take the quality and availability of fonts into account when computing the table. The table may be different from one font family to another.
Note. In CSS1, the suggested
scaling factor between adjacent indexes was 1.5 which user experience
proved to be too large.
For example, if the parent element has a font size of 'medium', a value of 'larger' will make the font size of the current element be 'large'. If the parent element's size is not close to a table entry, the user agent is free to interpolate between table entries or round off to the closest one. The user agent may have to extrapolate table values if the numerical value goes beyond the keywords.
Notice that small differences produce the same font size and sometimes changes in empohis and even character appearance
arial
10%
20%
30%
40%
50%
60%
70%
80%
90%
100%
|
110%
120%
130%
|
140%
150%
160%
|
170%
180%
|
200%
300%
400%
500%
|
img |
|
serif
| 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% 110% 120% 130% 140% 150% 160% 170% 180% 200% 300% 400% 500% |
verdana cellpadding=0 cellspacing=0
| 10% 20% 30% 40% 50% 60% 70% 80% 90% 95% 100% 105% |
| 95% 100% 105% |
| 110% 120% 130% 140% 150% 160% 170% |
| 170% 180% 200% 300% 400% 500% |
The actual value of this property may differ from the computed value due a numerical value on font-size-adjust and the unavailability of certain font sizes.
Child elements inherit the computed font-size value (otherwise, the effect of font-size-adjust would compound).
Example(s):
P { font-size: 12pt } |
do NOT use this form as the visitor cannot change size
and may even resort to disabling varing font-sizes altogether |
BLOCKQUOTE { font-size: larger }
EM { font-size: 150% }
EM { font-size: 1.5em }
| Value: | <number> | none | inherit |
| Initial: | none |
| Applies to: | all elements |
| Inherited: | yes |
| Percentages: | N/A |
| Media: | visual |
In bicameral scripts, the subjective apparent size and legibility of a font are less dependent on their font-size value than on the value of their 'x-height', or,more usefully, on the ratio of these two values, called the aspect value (font size divided by x-height). The higher the aspect value, the more likely it is that a font at smaller sizes will be legible. Inversely, faces with a lower aspect value will become illegible more rapidly below a given threshold size than faces with a higher aspect value. Straightforward font substitution that relies on font size alone may lead to illegible characters.
For example, the popular font Verdana has an aspect value of 0.58; when Verdana's font size 100 units, its x-height is 58 units. For comparison, Times New Roman has an aspect value of 0.46. Verdana will therefore tend to remain legible at smaller sizes than Times New Roman. Conversely, Verdana will often look too big if substituted for Times New Roman at a chosen size.
This property allows authors to specify an aspect value for an element that will preserve the x-height of the first choice font in the substitute font. Values have the following meanings:
y(a/a') = c
where:
y = font-size of first-choice font a' = aspect value of available font c = font-size to apply to available font
Example(s):
For example, if 14px Verdana (with an aspect value of 0.58) was unavailable and an available font had an aspect value of 0.46, the font-size of the substitute would be 14 * (0.58/0.46) = 17.65px.
Font size adjustments take place when computing the actual value of font-size. Since inheritance is based on the computed value, child elements will inherit unadjusted values.
|
| ||
|
|
| Value: | [ [ <font-style> || <font-variant>
|| < font-weight >
]? <font-size> [ / <'line-height'>
]? <'font-family'> ]
| caption | icon | menu | message-box | small-caption | status-bar | inherit |
| Initial: | see individual properties |
| Applies to: | all elements |
| Inherited: | yes |
| Percentages: | allowed on font-size and 'line-height' |
| Media: | visual |
The 'font' property is, except as described below, a shorthand property for setting font-style, font-variant, font-weight, font-size, 'line-height', and 'font-family', at the same place in the style sheet. The syntax of this property is based on a traditional typographical shorthand notation to set multiple properties related to fonts.
All font-related properties are first reset to their initial values, including those listed in the preceding paragraph plus 'font-stretch' and font-size-adjust. Then, those properties that are given explicit values in the 'font' shorthand are set to those values. For a definition of allowed and initial values, see the previously defined properties. For reasons of backwards compatibility, it is not possible to set 'font-stretch' and font-size-adjust to other than their initial values using the 'font' shorthand property; instead, set the individual properties.
Example(s):
In the second rule, the font size percentage value ('80%') refers to the font size of the parent element. In the third rule, the line height percentage ('110%') refers to the font size of the element itself.
The first three rules do not specify the font-variant and font-weight explicitly, so these properties receive their initial values ('normal'). Notice that the font family name "new century schoolbook", which contains spaces, is enclosed in quotes.
The fourth rule sets the font-weight to 'bold', the font-style to 'italic', and implicitly sets font-variant to 'normal'.
The fifth rule sets the font-variant ('small-caps'), the font-size (120% of the parent's font size), the 'line-height' (120% of the font size) and the 'font-family' ('fantasy'). It follows that the keyword 'normal' applies to the two remaining properties: font-style and font-weight.
The sixth rule sets the font-style, font-size, and 'font-family', the other font properties being set to their initial values. It then sets 'font-stretch' to 'condensed' since that property cannot be set to that value using the 'font' shorthand property.
The following values refer to system fonts:
System fonts may only be set as a whole; that is, the font family, size, weight, style, etc. are all set at the same time.These values may then be altered individually if desired. If no font with the indicated characteristics exists on a given platform, the user agent should either intelligently substitute (e.g., a smaller version of the 'caption' font might be used for the 'smallcaption' font), or substitute a user agent default font. As for regular fonts, if, for a system font, any of the individual properties are not part of the operating system's available user preferences, those properties should be set to their initial values.
That is why this property is "almost" a shorthand property: system fonts can only be specified with this property, not with 'font-family' itself, so 'font' allows authors to do more than the sum of its subproperties. However, the individual properties such as font-weight are still given values taken from the system font, which can be independently varied.
Example(s):
BUTTON { font: 300 italic 1.3em/1.7em "FB Armada", sans-serif }
BUTTON P { font: menu }
BUTTON P EM { font-weight: bolder }
If the font used for dropdown menus on a particular system happened to be, for example, 9-point Charcoal, with a weight of 600, then P elements that were descendants of BUTTON would be displayed as if this rule were in effect:
BUTTON P { font: 600 9pt Charcoal }
Because the 'font' shorthand resets to its initial value any property not explicitly given a value, this has the same effect as this declaration:
BUTTON P {
font-style: normal;
font-variant: normal;
font-weight: 600;
font-size: 9pt;
line-height: normal;
font-family: Charcoal
}
Generic font families are a fallback mechanism, a means of preserving some of the style sheet author's intent in the worst case when none of the specified fonts can be selected. For optimum typographic control, particular named fonts should be used in style sheets.
|
All five generic font families are defined to exist in all CSS implementations (they need not necessarily map to five distinct actual fonts). User agents should provide reasonable default choices for the generic font families, which express the characteristics of each family as well as possible within the limits allowed by the underlying technology.
User agents are encouraged to allow users to select alternative choices for the generic fonts.
Glyphs of serif fonts, as the term is used in CSS, have finishing strokes, flared or tapering ends, or have actual serifed endings (including slab serifs). Serif fonts are typically proportionately-spaced. They often display a greater variation between thick and thin strokes than fonts from the 'sans-serif' generic font family. CSS uses the term 'serif' to apply to a font for any script, although other names may be more familiar for particular scripts, such as Mincho (Japanese), Sung or Song (Chinese), Totum or Kodig (Korean). Any font that is so described may be used to represent the generic 'serif' family.
Examples of fonts, shown below in their displayed glyphs for YOUR User Agent (if available) that fit this description include:
| Latin |
Times New Roman,
Bodoni,
Garamond,
Minion Web,
ITC Stone Serif, ,
MS Georgia, ,
Bitstream Cyberbit ,
Roman,
ParkAvenue,
Monotype Corsiva,
Monotype Corsiva,
bedini
| Greek | Bitstream Cyberbit
| Cyrillic | Adobe Minion Cyrillic, Excelcior
Cyrillic Upright, MonotypeAlbion 70, Bitstream Cyberbit, ER Bukinst
| Hebrew | New Peninim, Raanana, Bitstream
Cyberbit
| Japanese | Ryumin Light-KL, Kyokasho ICA, Futo
Min A101
| Arabic | Bitstream Cyberbit
| Cherokee | Lo Cicero Cherokee
| |
Glyphs in sans-serif fonts, as the term is used in CSS, have stroke endings that are plain -- without any flaring, cross stroke, or other ornamentation. Sans-serif fonts are typically proportionately-spaced. They often have little variation between thick and thin strokes, compared to fonts from the 'serif' family. CSS uses the term 'sans-serif' to apply to a font for any script, although other names may be more familiar for particular scripts, such as Gothic (Japanese), Kai (Chinese), or Pathang (Korean). Any font that is so described may be used to represent the generic 'sans-serif' family.
Examples of fonts that fit this description include:
| Latin | MS Trebuchet, ITC Avant Garde Gothic, MS Arial, MS Verdana, Arial, Univers, Futura, Helvetica, , ITC Stone Sans, Gill Sans, Akzidenz Grotesk, |
| Greek | Attika, Typiko New Era, MS Tahoma, Monotype Gill Sans 571, Helvetica Greek |
| Cyrillic | Helvetica Cyrillic, ER Univers, Lucida Sans Unicode, Bastion |
| Hebrew | Arial Hebrew, MS Tahoma |
| Japanese | Shin Go, Heisei Kaku Gothic W5 |
| Arabic | MS Tahoma |
Glyphs in cursive fonts, as the term is used in CSS, generally have either joining strokes or other cursive characteristics beyond those of italic typefaces. The glyphs are partially or completely connected, and the result looks more like handwritten pen or brush writing than printed letterwork. Fonts for some scripts, such as Arabic, are almost always cursive. CSS uses the term 'cursive' to apply to a font for any script, although other names such as Chancery, Brush, Swing and Script are also used in font names.
Examples of fonts that fit this description include:
| Latin | Caflisch Script, Adobe Poetica, Sanvito, Ex Ponto, Snell Roundhand, Zapf-Chancery Script, |
| Cyrillic | ER Architekt |
| Hebrew | Corsiva |
| Arabic | DecoType Naskh, Monotype Urdu 507 |
Fantasy fonts, as used in CSS, are primarily decorative while still containing representations of characters (as opposed to Pi or Picture fonts, which do not represent characters). Examples include:
| Latin | Alpha Geometrique,
Critter, Cottonwood, FB Reactor, Studz, Space Toaster,
Symbol*, Vinta,
Wingdings,
Webdings* Zebrawood-regular miniPics-BorderlineCutout* |
The sole criterion of a monospace font is that all glyphs have the same fixed width. (This can make some scripts, such as Arabic, look most peculiar.) The effect is similar to a manual typewriter, and is often used to set samples of computer code.
Examples of fonts which fit this description include:
| Latin | Courier, MS Courier New, Lucida Console , Prestige , Everson Mono Curlz MT |
| Greek | MS Courier New, Everson Mono |
| Cyrillic | ER Kurier, Everson Mono |
| Japanese | Osaka Monospaced |
| Cherokee | Everson Mono |