As with any shorthand property, any individual value that is not specified is set to its corresponding initial value (possibly overriding values previously set using non-shorthand properties). Though not directly settable by font, the longhands font-size-adjust and font-kerning are also reset to their initial values.
Tip: The font-family property should hold several font names as a "fallback" system, to ensure maximum compatibility between browsers/operating systems. Start with the font you want, and end with a generic family (to let the browser pick a similar font in the generic family, if no other fonts are available). The font names should be separated with a comma. Read more about fallback fonts in the next chapter.
Serif font families are traditionally used in print media, making reading from paper easier. The basic print text is black on white, but modern printing techniques and electronic media have made room for more diverse colors in documents.
The font styles, just like the basic text styles, can serve many purposes. You can apply the font size setting globally or to a selected part of the text to make it catch the eye of the reader. Using different font families can help differentiate between sections of the content that serve various purposes (like main text and a side quotation or a recap). Different font colors can work as markers and guides just like font background colors that stand out even more and draw attention.
By default, all font-family values that are not specified in the config.fontFamily.options are stripped. You can enable support for all font names by using the config.fontFamily.supportAllValues option.
By default, the number of displayed document colors is limited to one row, but you can adjust it (or remove the whole section) by using the config.fontColor.documentColors or config.fontBackgroundColor.documentColors options.
Read or download the full official license text: OFL version 1.1 (26 February 2007)
Read or download the current OFL-FAQ version 1.1-update7 (November 2023)
Read more about why many individuals and companies choose the OFL and the history of the OFL
Explore a showcase of fonts released under the OFL
We recommend these fonts because they are legible and widely available and because they include special characters such as math symbols and Greek letters. Historically, sans serif fonts have been preferred for online works and serif fonts for print works; however, modern screen resolutions can typically accommodate either type of font, and people who use assistive technologies can adjust font settings to their preferences. For more on how font relates to accessibility, visit the page on the accessibility of APA Style.
Instructors and publishers vary in how they specify length requirements. Different fonts take up different amounts of space on the page; thus, we recommend using word count rather than page count to gauge paper length if possible.
The font subsets defined by an array of string values with the names of each subset you would like to be preloaded. Fonts specified via subsets will have a link preload tag injected into the head when the preload option is true, which is the default.
To use the font, set the className of the parent container of the text you would like to style to the font loader's variable value and the className of the text to the styles property from the external CSS file.
Every time you call the localFont or Google font function, that font will be hosted as one instance in your application. Therefore, if you need to use the same font in multiple places, you should load it in one place and import the related font object where you need it. This is done using a font definitions file.
Yeah. This is a really annoying problem. There are two reasons for it.
One is that even though you are in the old editor, you are still using the new dynamic themes. So the system doesn't accept any changes made in the old editor that are present in the new editor. Select one of themes from the old editor and the changes will stick.
The other thing is that sometimes, the manner in which the theme is applied results in less specific selectors being used to change the font. For this inspect the element whose theme who want to change, then change the values in custom CSS and add !important to enforce them.
I was in your position one day and wasted around two hours just fighting with the system, till somehow I stumbled on these solutions.
Hi ahmedA,
Thanks so much for your reply as I'm so frustrated. Off-and-on, I've been at it for days.
I had the theme set on "blank" but selected Qualtrics 2017 in the old editor and progress has been made (thank-you!!). In preview mode, I now see my text in the correct colour (black) and question is bolded. However, the theme has a question container which I can neither edit nor delete. The students don't want a background colour to the text.
I find CSS coding quite a mystery and had tried posting in bits from other posts but failed to achieve changing the text colour to black.
The other problem is for me personally - the font on the screen (edit mode) still shows as grey which is sending me blind. I know there is the high contrast option in the new style editor, but then I'm back to the original problem with being unable to fix the text display to black (and bold for question).
Try this. Use the new look and feel editor, revert to defaults. And use the settings provided here to adjust the fonts.
As I said earlier, because you were making changes using the old editor, they weren't getting registered. But since you don't want the old theme, then make the changes in the new editor.
PS: Have you tried other themes. I think the Qualtrics minimal themes don't have a question container.
Thanks for your continuing help ahmedA. I reset all the defaults using the new look and feel editior, which is where I started: it looks good for most questions but matrix tables and rank order questions have different fonts and font size. That's when I read about the Old Editor and discovered it was more powerful, even allowing me to change the colours of question vs choice text etc.
I guess at the end of the day, if I have to use the rich content editor for just those types of questions so be it. Qualtrics appeared to promise much but without a working knowledge of CSS and/or javascript, it's very difficult to make a survey look appealing.
A glyph is a shape used to render a character or a sequence of characters. In simple writing systems, such as Latin, typically one glyph represents one character. In general, however, characters and glyphs do not have one-to-one correspondence. For example, the character 'á' LATIN SMALL LETTER A WITH ACUTE, can be represented by two glyphs: one for 'a' and one for ''. On the other hand, the two-character string "fi" can be represented by a single glyph, an "fi" ligature. In complex writing systems, such as Arabic or the South and South-East Asian writing systems, the relationship between characters and glyphs can be more complicated and involve context-dependent selection of glyphs as well as glyph reordering. A font encapsulates the collection of glyphs needed to render a selected set of characters as well as the tables needed to map sequences of characters to corresponding sequences of glyphs. Physical and Logical Fonts The Java Platform distinguishes between two kinds of fonts: physical fonts and logical fonts. Physical fonts are the actual font libraries containing glyph data and tables to map from character sequences to glyph sequences, using a font technology such as TrueType or PostScript Type 1. All implementations of the Java Platform must support TrueType fonts; support for other font technologies is implementation dependent. Physical fonts may use names such as Helvetica, Palatino, HonMincho, or any number of other font names. Typically, each physical font supports only a limited set of writing systems, for example, only Latin characters or only Japanese and Basic Latin. The set of available physical fonts varies between configurations. Applications that require specific fonts can bundle them and instantiate them using the createFont method. Logical fonts are the five font families defined by the Java platform which must be supported by any Java runtime environment: Serif, SansSerif, Monospaced, Dialog, and DialogInput. These logical fonts are not actual font libraries. Instead, the logical font names are mapped to physical fonts by the Java runtime environment. The mapping is implementation and usually locale dependent, so the look and the metrics provided by them vary. Typically, each logical font name maps to several physical fonts in order to cover a large range of characters. Peered AWT components, such as Label and TextField, can only use logical fonts. For a discussion of the relative advantages and disadvantages of using physical or logical fonts, see the Internationalization FAQ document. Font Faces and Names A Font can have many faces, such as heavy, medium, oblique, gothic and regular. All of these faces have similar typographic design. There are three different names that you can get from a Font object. The logical font name is simply the name that was used to construct the font. The font face name, or just font name for short, is the name of a particular font face, like Helvetica Bold. The family name is the name of the font family that determines the typographic design across several faces, like Helvetica. The Font class represents an instance of a font face from a collection of font faces that are present in the system resources of the host system. As examples, Arial Bold and Courier Bold Italic are font faces. There can be several Font objects associated with a font face, each differing in size, style, transform and font features. The getAllFonts method of the GraphicsEnvironment class returns an array of all font faces available in the system. These font faces are returned as Font objects with a size of 1, identity transform and default font features. These base fonts can then be used to derive new Font objects with varying sizes, styles, transforms and font features via the deriveFont methods in this class. Font and TextAttribute Font supports most TextAttributes. This makes some operations, such as rendering underlined text, convenient since it is not necessary to explicitly construct a TextLayout object. Attributes can be set on a Font by constructing or deriving it using a Map of TextAttribute values. The values of some TextAttributes are not serializable, and therefore attempting to serialize an instance of Font that has such values will not serialize them. This means a Font deserialized from such a stream will not compare equal to the original Font that contained the non-serializable attributes. This should very rarely pose a problem since these attributes are typically used only in special circumstances and are unlikely to be serialized.