Pema font family


Designed by  Markus Strümpel

Pema – a contemporary Tibetan sans serif encoded in the Unicode standard. This is the first Tibetan typeface influenced by western sans serif fonts. It was designed especially to match multilingual purposes. The rather calligraphic Tibetan scripts did not match with the design aesthetics of western and Indian fonts and so I came up with the idea to design a “modern” Tibetan sans serif. Pema comes in two weights, Regular and Bold, each equipped with almost 1.300 glyphs.

Pema Regular

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


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

Std / OT TTF

supports at least

21 languages.















Technical details
OpenType outline flavour:
TTF - TrueType-Outlines
Technical font names:
File name: Pema-Regular.ttf
Windows menu name: Pema
PostScript name: , Pema
PostScript full name: , Pema
Catalog number:
168555973
Characters:
1300
77.99 incl. VAT
Add to cart

Features

Languages

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.

Above-Base Mark Positioning

Tag: abvm

Function: Positions marks above base glyphs. In complex scripts like Devanagari (Indic), the Anuswar needs to be positioned above the base glyph. This base glyph can be a base consonant or conjunct. The base glyph and the presence/absence of other marks above the base glyph decides the location of the Anuswar, so that they do not overlap each other.

Above-Base Substitutions

Tag: abvs

Function: Substitutes a ligature for a base glyph and mark that's above it. In complex scripts like Kannada (Indic), the vowel sign for the vowel I which a mark, is positioned above base consonants. This mark combines with the consonant Ga to form a ligature.

Below-Base Mark Positioning

Tag: blwm

Function: The form that consonants appear below the base glyph. Consonants in below-base form appear in Bengali syllables after the ones that form the base glyph. Below-base forms are represented by the non-spacing mark glyph.

Below-Base Substitutions

Tag: blws

Function: Produces ligatures that comprise of base glyph and below-base forms. In the Malayalam script (Indic), the conjunct Kla, requires a ligature which is formed using the base glyph Ka and the below-base form of consonant La. This feature can also be used to substitute ligatures formed using base glyphs and below base matras in Indic scripts.

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.

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