HS Future Sans font family


Designed by  Hasan Abu Afash
Abdulsamiea Rajab Salem
HS Future Sans is the sans serif version of HS Future. It has three weights and was converted to OpenType to support Arabic, Persian and Urdu to be compatible with the various operation systems and modern software. The smoothing of this font and the combination of straight and curved parts without the serif gave the user additional option beside HS Future family. It made it a beautiful typeface appropriate to the titles, and able to meet the desire of the user in the design of ads and modern designs of various types of audio and visual.

نص حكيم له سر قاطع وذو شأن عظيم مكتوب على ثوب أخضر ومغلف بجلد أزرق

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.
HS Future Sans


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














Technical details
OpenType outline flavour:
TTF - TrueType-Outlines
Technical font names:
File name: HSFutureSans-Bold.ttf
Windows menu name: HS Future Sans
PostScript name: , HSFutureSans-Bold
PostScript full name: , HS Future Sans Bold
Catalog number:
168409943
Characters:
387
US$ 59
Add to cart

Features

Languages

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.

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.

Initial Forms

Tag: init

Function: Replaces glyphs at the beginnings of words with alternate forms designed for this use. This is common in Latin connecting scripts, and required in various non-Latins like Arabic. In the typeface Ex Ponto, the default t in the word 'type' is replaced with the t.begin form.

Terminal Forms

Tag: fina

Function: Replaces glyphs at the ends of words with alternate forms designed for this use. This is common in Latin connecting scripts, and required in various non-Latins like Arabic. In the typeface Poetica, the default e in the word 'type' is replaced with the e.end form.

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.

Isolated Forms

Tag: isol

Function: Replaces the nominal form of glyphs with their isolated forms. In Arabic, if the Alef is followed by Lam, the default glyph for Alef is replaced with its isolated form.

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.

Medial Forms

Tag: medi

Function: Replaces glyphs in the middles of words (i.e. following a beginning and preceding an end) with alternate forms designed for this use. Note: This is different from the default form, which is designed for stand-alone use. This is common in Latin connecting scripts, and required in various non-Latins like Arabic. In the typeface Caflisch Script, the y and p in the word 'type' are replaced by the y.med and p.med forms.

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 Arabic script. Each font is Unicode™ encoded, and available in different for

Tag: Arabic

Function: These fonts support the Arabic script. 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.