Arial Windows compatible® font family


Designed by  Robin Nicholas in 1982
Patricia Saunders in 1982
Arial was designed for Monotype in 1982 by Robin Nicholas and Patricia Saunders. A contemporary sans serif design, Arial contains more humanist characteristics than many of its predecessors and as such is more in tune with the mood of the last decades of the twentieth century. The overall treatment of curves is softer and fuller than in most industrial style sans serif faces. Terminal strokes are cut on the diagonal which helps to give the face a less mechanical appearance.

Arial is an extremely versatile family of typefaces which can be used with equal success for text setting in reports, presentations, magazines etc, and for display use in newspapers, advertising and promotions.

Arial Windows compatible Arial OS Bold Italic

Desktop fonts are designed to be installed on a computer for use with applications. Licensed per user.
Annual web fonts are licensed for a set number of page views.
Annual web fonts are licensed for a set number of page views.
Application licensing allows fonts to be embedded in your software applications. The license may be based on the number of titles or the number of installations.
Electronic Document Fonts can be embedded in an eBook, eMagazine or eNewspaper. Fonts are licensed annually per issue.
Server fonts can be installed on a server and e.g. used by automated processes to create items. A license is per server core CPU per year.
A Digital Ads license allows you to embed web fonts in digital ads, such as ads created in HTML5. These license is based on the number of ad impressions.
Arial Windows compatible


Select technical format and
language support of the font.
world-map map

WGL / OT TTF

supports at least

79 languages.















Technical details
OpenType outline flavour:
TTF - TrueType-Outlines
Technical font names:
File name: arialbi_M.ttf
Windows menu name: Arial
PostScript name: , Arial-BoldItalicMT
PostScript full name: , Arial Bold Italic
Catalog number:
168421806
Characters:
3279
US$ 54.99
Add to cart

Features

Languages

Denominators

Tag: dnom

Function: Replaces selected figures which follow a slash with denominator figures. In the string 11/17 selected by the user, the application turns the 17 into denominators when the user applies the fraction feature.

Fractions

Tag: frac

Function: Replaces figures separated by a slash with 'common' (diagonal) fractions. The user enters 3/4 in a recipe and gets the threequarters fraction.

Lining Figures

Tag: lnum

Function: This feature changes selected figures from oldstyle to the default lining form. The user invokes this feature in order to get lining figures, which fit better with all-capital text. Various characters designed to be used with figures may also be covered by this feature. In cases where lining figures are the default form, this feature would undo previous substitutions.

Localized Forms

Tag: locl

Function: Many scripts used to write multiple languages over wide geographical areas have developed localized variant forms of specific letters, which are used by individual literary communities. For example, a number of letters in the Bulgarian and Serbian alphabets have forms distinct from their Russian counterparts and from each other. In some cases the localized form differs only subtly from the script 'norm', in others the forms are radically distinct. This feature enables localized forms of glyphs to be substituted for default forms. The user applies this feature to text to enable localized Bulgarian forms of Cyrillic letters; alternatively, the feature might enable localized Russian forms in a Bulgarian manufactured font in which the Bulgarian forms are the default characters.

Numerators

Tag: numr

Function: Replaces selected figures which precede a slash with numerator figures, and replaces the typographic slash with the fraction slash. In the string 11/17 selected by the user, the application turns the 11 into numerators, and the slash into a fraction slash when the user applies the fraction feature.

Old Style Figures

Tag: onum

Function: This feature changes selected figures from the default lining style to oldstyle form. The user invokes this feature to get oldstyle figures, which fit better into the flow of normal upper- and lowercase text. Various characters designed to be used with figures may also have oldstyle versions.

Proportional Figures

Tag: pnum

Function: Replaces figure glyphs set on uniform (tabular) widths with corresponding glyphs set on glyph-specific (proportional) widths. Tabular widths will generally be the default, but this cannot be safely assumed. Of course this feature would not be present in monospaced designs. The user may apply this feature to get even spacing for lining figures used as dates in an all-cap headline.

Tabular Figures

Tag: tnum

Function: Replaces figure glyphs set on proportional widths with corresponding glyphs set on uniform (tabular) widths. Tabular widths will generally be the default, but this cannot be safely assumed. Of course this feature would not be present in monospaced designs. The user may apply this feature to get oldstyle figures to align vertically in a column.

Small Capitals From Capitals

Tag: c2sc

Function: Small Capitals From Capitals

Small Capitals

Tag: smcp

Function: This feature turns lowercase characters into small capitals. This corresponds to the common SC font layout. It is generally used for display lines set in Large & small caps, such as titles. Forms related to small capitals, such as oldstyle figures, may be included. The user enters text as mixed capitals and lowercase, and gets Large & small cap text.

Stylistic Alternates

Tag: salt

Function: Many fonts contain alternate glyph designs for a purely esthetic effect; these don't always fit into a clear category like swash or historical. As in the case of swash glyphs, there may be more than one alternate form. This feature replaces the default forms with the stylistic alternates. The user applies this feature to Industria to get the alternate form of g.

Discretionary Ligatures

Tag: dlig

Function: Replaces a sequence of glyphs with a single glyph which is preferred for typographic purposes. This feature covers those ligatures which may be used for special effect, at the user's preference. The glyph for ct replaces the sequence of glyphs c t, or U+322E (Kanji ligature for "Friday") replaces the sequence U+91D1 U+66DC U+65E5.

Sylistic Set 1

Tag: ss01

Function: In addition to, or instead of, stylistic alternatives of individual glyphs (see 'salt' feature), some fonts may contain sets of stylistic variant glyphs corresponding to portions of the character set, e.g. multiple variants for lowercase letters in a Latin font. Glyphs in stylistic sets may be designed to harmonise visually, interract in particular ways, or otherwise work together. Examples of fonts including stylistic sets are Zapfino Linotype and Adobe's Poetica. Individual features numbered sequentially with the tag name convention 'ss01' 'ss02' 'ss03' . 'ss20' provide a mechanism for glyphs in these sets to be associated via GSUB lookup indexes to default forms and to each other, and for users to select from available stylistic sets.

Sylistic Set 2

Tag: ss02

Function: In addition to, or instead of, stylistic alternatives of individual glyphs (see 'salt' feature), some fonts may contain sets of stylistic variant glyphs corresponding to portions of the character set, e.g. multiple variants for lowercase letters in a Latin font. Glyphs in stylistic sets may be designed to harmonise visually, interract in particular ways, or otherwise work together. Examples of fonts including stylistic sets are Zapfino Linotype and Adobe's Poetica. Individual features numbered sequentially with the tag name convention 'ss01' 'ss02' 'ss03' . 'ss20' provide a mechanism for glyphs in these sets to be associated via GSUB lookup indexes to default forms and to each other, and for users to select from available stylistic sets.

Sylistic Set 3

Tag: ss03

Function: In addition to, or instead of, stylistic alternatives of individual glyphs (see 'salt' feature), some fonts may contain sets of stylistic variant glyphs corresponding to portions of the character set, e.g. multiple variants for lowercase letters in a Latin font. Glyphs in stylistic sets may be designed to harmonise visually, interract in particular ways, or otherwise work together. Examples of fonts including stylistic sets are Zapfino Linotype and Adobe's Poetica. Individual features numbered sequentially with the tag name convention 'ss01' 'ss02' 'ss03' . 'ss20' provide a mechanism for glyphs in these sets to be associated via GSUB lookup indexes to default forms and to each other, and for users to select from available stylistic sets.

Unicase

Tag: unic

Function: This feature maps upper- and lowercase letters to a mixed set of lowercase and small capital forms, resulting in a single case alphabet (for an example of unicase, see the Emigre type family Filosofia). The letters substituted may vary from font to font, as appropriate to the design. If aligning to the x-height, smallcap glyphs may be substituted, or specially designed unicase forms might be used. Substitutions might also include specially designed figures. The user enters text as uppercase, lowercase or mixed case, and gets unicase text.

Glyph Composition/Decomposition

Tag: ccmp

Function: To minimize the number of glyph alternates, it is sometimes desired to decompose a character into two glyphs. Additionally, it may be preferable to compose two characters into a single glyph for better glyph processing. This feature permits such composition/decompostion. The feature should be processed as the first feature processed, and should be processed only when it is called. In Syriac, the character 0x0732 is a combining mark that has a dot above AND a dot below the base character. To avoid multiple glyph variants to fit all base glyphs, the character is decomposed into two glyphs...a dot above and a dot below. These two glyphs can then be correctly placed using GPOS. In Arabic it might be preferred to combine the shadda with fatha (0x0651, 0x064E) into a ligature before processing shapes. This allows the font vendor to do special handling of the mark combination when doing further processing without requiring larger contextual rules.

Capital Spacing

Tag: cpsp

Function: Globally adjusts inter-glyph spacing for all-capital text. Most typefaces contain capitals and lowercase characters, and the capitals are positioned to work with the lowercase. When capitals are used for words, they need more space between them for legibility and esthetics. This feature would not apply to monospaced designs. Of course the user may want to override this behavior in order to do more pronounced letterspacing for esthetic reasons. The user sets a title in all caps, and the Capital Spacing feature opens the spacing.

Kerning

Tag: kern

Function: Adjusts amount of space between glyphs, generally to provide optically consistent spacing between glyphs. Although a well-designed typeface has consistent inter-glyph spacing overall, some glyph combinations require adjustment for improved legibility. Besides standard adjustment in the horizontal direction, this feature can supply size-dependent kerning data via device tables, "cross-stream" kerning in the Y text direction, and adjustment of glyph placement independent of the advance adjustment. Note that this feature may apply to runs of more than two glyphs, and would not be used in monospaced fonts. Also note that this feature does not apply to text set vertically. The o is shifted closer to the T in the combination "To."

Mark Positioning

Tag: mark

Function: Positions mark glyphs with respect to base glyphs. In the Arabic script, positioning the Hamza above the Yeh.

Mark to Mark Positioning

Tag: mkmk

Function: Positions marks with respect to other marks. Required in various non-Latin scripts like Arabic. In Arabic, the ligaturised mark Ha with Hamza above it; can also be obtained by positioning these marks relative to one another.

Required Ligatures

Tag: rlig

Function: Replaces a sequence of glyphs with a single glyph which is preferred for typographic purposes. This feature covers those ligatures, which the script determines as required to be used in normal conditions. This feature is important for some scripts to insure correct glyph formation. The Arabic character lam followed by alef will always form a ligated lamalef form. This ligated form is a requirement of the script's shaping. The same happens with the Syriac script.

These fonts support the Basic Latin character set. Each font is Unicode™ encoded, and available in d

Tag: Basic Latin

Function: These fonts support the Basic Latin character set. Each font is Unicode™ encoded, and available in different formats. Please review the product information for each font to ensure it will meet your requirements.

These fonts support the Latin Extended character set. Each font is Unicode™ encoded, and available i

Tag: Latin Extended

Function: These fonts support the Latin Extended character set. Each font is Unicode™ encoded, and available in different formats. Please review the product information for each font to ensure it will meet your requirements.