Cartograph CF font family


Designed by  Connary Fagen

Cartograph® CF is a handsome monospaced font family featuring lush italics, code-friendly ligatures, and a proportional set accessible via OpenType. With warmth and character, Cartograph excels in both code and prose. Also includes Powerline symbols and Greek, Cyrillic, and Japanese Katakana scripts.


Cartograph® CF is designed to stand on its own, but will also pair well with contrasting typefaces, particularly text-friendly typefaces like Artifex CF, Artifex Hand CF, and Addington CF.


All typefaces from Connary Fagen include free updates, including new features, and free technical support.

Cartograph CF Regular 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.
Cartograph CF


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

STD / OT CFF

supports at least

21 languages.















Technical details
OpenType outline flavour:
CFF - PostScript-Outlines
Technical font names:
File name: CartographCF-RegularItalic.otf
Windows menu name: Cartograph CF
PostScript name: , CartographCF-RegularItalic
PostScript full name: , Cartograph CF Regular Italic
Catalog number:
167706821
Characters:
1034
41.99 incl. VAT
Add to cart

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.

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.

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).

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.

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.

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 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.

Vertical Writing

Tag: vert

Function: Replaces default forms with variants adjusted for vertical writing when in vertical writing mode. While most CJKV glyphs remain vertical when set in vertical writing mode, some take a different form (usually rotated and repositioned) for this purpose. Glyphs covered by this feature correspond to the set normally rotated in low-end DTP applications. In vertical writing mode, the opening parenthesis (U+FF08) is replaced by the rotated form (U+FE35).

Vertical Rotation

Tag: vrt2

Function: Replaces some fixed-width (half-, third- or quarter-width) or proportional-width glyphs (mostly Latin or katakana) with forms suitable for vertical writing (that is, rotated 90 degrees clockwise). Note that these are a superset of the glyphs covered in the vert table. ATM/NT 4.1 and the Windows 2000 OTF driver impose the following requirements for an OpenType font with CFF outlines to be used for vertical writing: the vrt2 feature must be present in the GSUB table, it must comprises a single lookup of LookupType 1 and LookupFlag 0, and the lookup must have a single subtable. The predecessor feature, vert, is ignored. A rotated glyph must be designed such that its top side bearing and vertical advance as recorded in the Vertical Metrics ('vmtx') table are identical to the left side bearing and horizontal advance, respectively, of the corresponding upright glyph as recorded in the Horizontal Metrics ('hmtx') table. (The horizontal advance of the rotated glyph may be set to any value, since the glyph is intended only for vertical writing use. The vendor may however set it to head.unitsPerEm, to prevent overlap during font proofing tests, for example.) Thus, proportional-width glyphs with rotated forms in the vrt2 feature will appear identically spaced in both vertical and horizontal writing. In order for kerning to produce identical results as well, developers must ensure that the Vertical Kerning (vkrn) feature record kern values between the rotated glyphs that are the same as kern values between their corresponding upright glyphs in the Kerning (kern) feature. Proportional- or half-width Latin and half-width katakana characters are rotated 90 degrees clockwise for vertical writing.

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.

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.