Media: visual Computed value: as specified 'font-family' Value: * ] | inherit Initial: depends on user agent (Typically, sizes for scalable fontsĪre rounded to the nearest whole pixel, while the tolerance forīitmapped fonts could be as large as 20%.) Further computations, e.g.,īy 'em' values in other properties, are based onġ5.3 Font family: the 'font-family' property That is only available as small-caps shall be selectable as either a 'normal' face or a 'small-caps' face. A font cannot fail to have a normal variant. 'normal' matches a font's normal (non-small-caps) variant. A small-caps font may be synthesized byĮlectronically scaling uppercase letters from a normal font.
Synthesized, or (3) a font where all lowercase letters are replaced by 'Small-caps' matches (1) aįont labeled as 'small-caps', (2) a font in which the small caps are Otherwise the values must be matched exactly or font-style will fail. Labeled with the CSS keyword 'italic' (preferred) or 'oblique'. Will be satisfied if there is either a face in the UA's font database
The per-property matching rules from (2) above are as follows: The CSS 2.1 properties for each character.) (The above algorithm can be optimized to avoid having to revisit The UA should mapĮach character for which it has no suitable font to a visible symbolĬhosen by the UA, preferably a "missing character" glyph from one of the Means to determine a suitable font for that character. If a particularĬharacter cannot be displayed using this font, then the UA may use other Match that can be obtained within the default font. UA-dependent default 'font-family' and repeat step 2, using the best
If there is no font within the family selected in 2, then use a. 'font-family' in the font sets, then repeat step 2 with the next If there is a matching font face, but it does not contain a glyphįor the current character, and if there is a next alternative. In the font set, then repeat step 2 with the next alternative Processed by step 2, and if there is a next alternative 'font-family' If there is no matching font face within the 'font-family' being. Then that is the matching font face for the given element or character. If there are matches for all the remaining properties, The remaining properties are testedĪgainst the family according to the matching criteria described withĮach property. Using theĬomplete set of properties, the UA uses the 'font-family' property toĬhoose a tentative font family. At a given element and for each character in that element, the UAĪssembles the font properties applicable to that element. If there are two fonts with exactly the same properties, the user Properties of all the fonts of which the UA is aware. The User Agent makes (or accesses) a database of relevant CSS 2.1. Possible across UAs (assuming that the same library of font faces is Insure that the results of this matching process are as consistent as The properties are matched in a well-defined order to Properties, matching of properties to font faces must be doneĬarefully. Therefore it is not a simple problem to map typicalįont selection properties to a specific font.īecause there is no accepted, universal taxonomy of font Labeled as being Oblique, Slanted, Incline, Cursive or E.g., 'italic' isĬommonly used to label slanted text, but slanted text may also be Unfortunately, there exists no well-defined and universallyĪccepted taxonomy for classifying fonts, and terms that apply to oneįont family may not be appropriate for others. Setting font properties will be among the most common uses of style The CSS Working Group is also developing CSS level 2 revision 2 (CSS 2.2). Please, see "Cascading Style Sheets (CSS) - The Official Definition" in the latest CSS Snapshot for a list of specifications and the sections they replace. 
Note: Several sections of this specification have been updated by other specifications.
0 kommentar(er)
