Botanica Schriftfamilie


Entworfen von  Elena Genova (2015)

Botanica Sans

Desktop-Fonts sind für die Installation auf einem Computer und die Nutzung mit Anwendungen konzipiert. Diese Fonts werden pro Computer lizenziert.
Pay-as-you-go-Webfonts sind für eine bestimmte Anzahl von Seitenaufrufen lizenziert.
Webfonts werden mit der CSS-Regel @font-face verwendet. Die Lizenz ist zeitlich unbegrenzt.
Die App-Lizenzierung ermöglicht die Einbettung von Fonts in Ihre Apps. Die Lizenz kann sich auf die Anzahl der verschiedenen Apps oder aber die Anzahl der Installationen einer App beziehen.
Electronic Publication Fonts sind für die Einbettung in eBooks, eMagazines oder eNewspapers bestimmt. Diese Fonts werden pro Ausgabe lizenziert.
Server-Fonts können auf einem Server installiert und z.B. von Prozessen zur Erstellung von Objekten verwendet werden. Eine Lizenz gilt pro Server Core CPU pro Jahr.
Eine Digital Ads-Lizenz ermöglicht es Ihnen, Webfonts in digitale Anzeigen einzubetten, wie beispielsweise in mit HTML5 erstellte Anzeigen. Diese Lizenz basiert auf der Anzahl der Ad Impressions.
Botanica


Wählen Sie das technische
Format und den Sprachausbau.
world-map map

Std / OT CFF

supports at least

21 Sprachen.















Technische Details
OpenType-Kurven-Typ:
CFF - PostScript-Outlines
Technische Font-Namen:
Dateiname: BotanicaSans-Regular.otf
Windows-Menü-Name: Botanica Sans
PostScript-Name: BotanicaSans-Regular
Langer PostScript-Name: Botanica Sans
Katalognummer:
167461264
Characters:
332
US$ 7
In den Warenkorb

Besonderheiten

Sprachen

Localized Forms

Tag: locl

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

Stylistic Alternates

Tag: salt

Funktion: 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

Funktion: 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

Funktion: 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

Funktion: 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

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

Mark to Mark Positioning

Tag: mkmk

Funktion: 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

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