Madera™ font family


Designed by  Malou Verlomme in 2018

Madera Thin

Desktop fonts are designed to
be installed on a computer for
use with applications.
Licensed per computer.
Web fonts are used with the CSS
@font-face rule. They are licensed
for a set number of page views with
no time limitation.
Mobile App Fonts can be embedded in your mobile application. Each app requires a separate license. The license is based on the number of app installations.
Electronic Publication Fonts can be
embedded in an eBook, eMagazine or
eNewspaper. Fonts are licensed 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.
Select the number of computers
on which the font will be installed.
Select the amount of page views
that you can use over time. We’ll let
you know when you’re running low.
Select the number of app
installations you want to license.
Some mobile app fonts allow an
unlimited number of installations.
Further information
Select the number of electronic publications
you intend to embed the font in. Each license
is valid for one issue for the life of that issue.
Select the total number of core
CPUs of the servers on which
the font will be installed.
A license has a term of 1 year.
Page views/month: Please select the
number of monthly page views
anticipated. The license has no time
limit and does not need to be replaced.
You only pay for additional page views
if your site gets more traffic than expected.
Please select the desired number of ad impressions. We’ll let
you know when you’re running low.
Select technical format and
language support of the font.
Select the language support of
the font: W1G (98 languages),
COM (56 languages),
PRO (33 languages) or
STD (21 languages).
Language versions the web font is
available in. These differ in contained
characters and file size. You get all
available versions with your license.
Test-drive Madera™ Thin in Typecast.

Typecast is a web-based tool to create visual and semantic designs. Check for readability, rendering and beauty then share a working prototype of your design.

Tip: Add fonts to your Favorites, then test your custom selection in Typecast!

Fonts

Desktop

Web

Digital Ads

App

ePub

Server
Desktop fonts are designed to be installed on a computer for use with applications. Licensed per computer.
Web fonts are used with the CSS @font-face rule. They are licensed for a set number of page views with no time limitation.
Web fonts are used with the CSS rule @font-face used. The license has no time limit.
Mobile App Fonts can be embedded in your mobile application. Each app requires a separate license. The license is based on the number of app installations.
Electronic Publication Fonts can be embedded in an eBook, eMagazine or eNewspaper. Fonts are licensed 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.
You can use this type of license to embed web fonts in digital ads, such as ads created in HTML5. The licenses are valid for a specific number of ad impressions without time limit.
Madera


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

Pro / OT TTF

supports at least

33 languages.















Technical details
OpenType outline flavour:
TTF - TrueType-Outlines
Technical font names:
File name: Madera-Thin.ttf
Windows menu name: Madera Thin
PostScript name: Madera-Thin
PostScript full name: Madera Thin
Catalog number:
168495069
Characters:
652
US$ 49
Add to cart
Activate Quick Checkout

Save on additional license types when you buy 2 or more

US$ 98


US$ 88.20

US$ 49


US$ 49


US$ 49


More options
Add to favorites

Features

Languages

Case-Sensitive Forms

Tag: case

Function: Shifts various punctuation marks up to a position that works better with all-capital sequences or sets of lining figures; also changes oldstyle figures to lining figures. By default, glyphs in a text face are designed to work with lowercase characters. Some characters should be shifted vertically to fit the higher visual center of all-capital or lining text. Also, lining figures are the same height (or close to it) as capitals, and fit much better with all-capital text. The user selects a block of text and applies this feature. The dashes, bracketing characters, guillemet quotes and the like shift up to match the capitals, and oldstyle figures change to lining figures.

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.

Standard Ligatures

Tag: liga

Function: Replaces a sequence of glyphs with a single glyph which is preferred for typographic purposes. This feature covers the ligatures which the designer/manufacturer judges should be used in normal conditions. The glyph for ffl replaces the sequence of glyphs f f l.

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.

Ordinals

Tag: ordn

Function: Replaces default alphabetic glyphs with the corresponding ordinal forms for use after figures. One exception to the follows-a-figure rule is the numero character (U+2116), which is actually a ligature substitution, but is best accessed through this feature. The user applies this feature to turn 2.o into 2.o (abbreviation for secundo).

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.

Scientific Inferiors

Tag: sinf

Function: Replaces lining or oldstyle figures with inferior figures (smaller glyphs which sit lower than the standard baseline, primarily for chemical or mathematical notation). May also replace lowercase characters with alphabetic inferiors. The application can use this feature to automatically access the inferior figures (more legible than scaled figures).

Superscript

Tag: sups

Function: Replaces lining or oldstyle figures with superior figures (primarily for footnote indication), and replaces lowercase letters with superior letters (primarily for abbreviated French titles). The application can use this feature to automatically access the superior figures (more legible than scaled figures) for footnotes, or the user can apply it to Mssr to get the classic form.

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.

Contextual Alternates

Tag: calt

Function: In specified situations, replaces default glyphs with alternate forms which provide better joining behavior. Used in script typefaces which are designed to have some or all of their glyphs join. In Caflisch Script, o is replaced by o.alt2 when followed by an ascending letterform.

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.

Subscript

Tag: subs

Function: The "subs" feature may replace a default glyph with a subscript glyph, or it may combine a glyph substitution with positioning adjustments for proper placement. Recommended implementation: First, a single or contextual substitution lookup implements the subscript glyph (GSUB lookup type 1). Then, if the glyph needs repositioning, an application may apply a single adjustment, pair adjustment, or contextual adjustment positioning lookup to modify its position.

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.

Sylistic Set 4

Tag: ss04

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 5

Tag: ss05

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 6

Tag: ss06

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 7

Tag: ss07

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 8

Tag: ss08

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.

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.

Alternate Annotation Forms

Tag: nalt

Function: Replaces default glyphs with various notational forms (e.g. glyphs placed in open or solid circles, squares, parentheses, diamonds or rounded boxes). In some cases an annotation form may already be present, but the user may want a different one. The user invokes this feature to get U+3200 (the circled form of 'ga') from U+3131 (hangul 'ga').

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.

-

Tag: Screen optimized

SkyFonts loading...