aliftype / mada

Mada (مدى) is a geometric, low-contrast Arabic typeface

Mada

Mada (مدى) is a modernist, low contrast Arabic typeface based largely on the typeface seen in Cairo metro old signage which was designed by Professor Fathi Gouda of the Faculty of Applied Arts, Helwan University.

Mada is characterised by low descenders, open contours and low contrast forms making it suitable for small point sizes, user interfaces, signage or low resolution settings.

Mada can work also as a display typeface giving modernist and simplistic feeling.

Mada is variable font that has all the font weights in the same file, and allow dynamic changes of the font weight. Font weights supported by Mada range from Extra Light to Black.

The Latin part of Mada taken from Source Sans by Paul D. Hunt.

Building

You need GNU Make and a few Python packages. To install the Python requirements, run:

pip install -r requirements.txt

Then to build the fonts:

make ttf

mada's Issues

Broken diacritics

Love this font but it seems like it's screwing up certain diacritics. Here's an example in Google Docs...

And how it should look (using Verdana here)...

The problem is the little diagonal accent called a kasra, utf16 char \u0650. I'm not sure if other accents also have problems.

---

Here's the selectable text if that's any help...

الرِّياضَة

Also: Looking around, i get the same problem in Google Fonts and Adobe AIR. In LibreOffice the kasra doesn't show at all.

Wrong glyph for U+2094 LATIN SUBSCRIPT SMALL LETTER SCHWA

The glyph of U+2094 LATIN SUBSCRIPT SMALL LETTER SCHWA is a superscript schwa. The glyph should lowered and/or reassigned to U+1D4A MODIFIER LETTER SMALL SCHWA.

Make Faa more like a Faa than Qaaf

Its more like غوغل درايڨ thank غوغل درايڤ, or I think I just got that to my eye.

ڻ‍ shows as black box in some positions

http://www.unics.uni-hannover.de/nhtcapri/sindhi-alphabet.html

Overlap issuse

Hi Khaled,

There is an overlap issue in Latin Cap 'A'

Gaps between connected glyphs

The famous rasterisation rounding error. We need some overlap, but not always (e.g. no overlap before س).

New release?

Many commits since last release :)

Wrong glyph for U+0281 LATIN LETTER SMALL CAPITAL INVERTED R

The glyph for U+0281 LATIN LETTER SMALL CAPITAL INVERTED R looks like a turned ⟨ʀ⟩, but it should look like an upside-down ⟨ʀ⟩.

U+06AD ARABIC LETTER NG Missing

U+06AD ARABIC LETTER NG Missing // ڭ

example: Good
Egypt/Morocco: ڭود / چود

build with gftools builder?

@khaledhosny instead of using fontmake in the make file, can you use gfools builder? It would close some fails about the hinting and the STAT table.

config.yml would be pretty straightforward:

sources:
    - Mada.glyphs
buildOTF: false
familyName: Mada

and the command should be:
gftools builder config.yml

Fontbakery report

Fontbakery version: 0.8.11

[1] Family checks

ℹ INFO: Check axis ordering on the STAT table. (com.google.fonts/check/STAT/axis_order)

• ℹ INFO From a total of 1 font files, 0 of them (0.00%) lack a STAT table.

  And these are the most common STAT axis orderings:
  ('wght', 1) [code: summary]

[20] Mada.ttf

🔥 FAIL: Checking file is named canonically. (com.google.fonts/check/canonical_filename)

• 🔥 FAIL Expected "Mada[wght].ttf. Got Mada.ttf. [code: bad-filename]

🔥 FAIL: Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering? (com.google.fonts/check/gasp)

• 🔥 FAIL Font is missing the 'gasp' table. Try exporting the font with autohinting enabled.
  If you are dealing with an unhinted font, it can be fixed by running the fonts through the command 'gftools fix-nonhinting'
  GFTools is available at https://pypi.org/project/gftools/ [code: lacks-gasp]

🔥 FAIL: Font enables smart dropout control in "prep" table instructions? (com.google.fonts/check/smart_dropout)

• 🔥 FAIL The 'prep' table does not contain TrueType instructions enabling smart dropout control. To fix, export the font with autohinting enabled, or run ttfautohint on the font, or run the gftools fix-nonhinting script. [code: lacks-smart-dropout]

🔥 FAIL: Check a font's STAT table contains compulsory Axis Values. (com.google.fonts/check/STAT)

• 🔥 FAIL Compulsory STAT Axis Values are incorrect:

Name	Axis	Current Value	Current Flags	Current LinkedValue	Expected Value	Expected Flags	Expected LinkedValue
ExtraLight	wght	N/A	N/A	N/A	200.0	0	None
Light	wght	N/A	N/A	N/A	300.0	0	None
Regular	wght	N/A	N/A	N/A	400.0	2	700.0
Medium	wght	N/A	N/A	N/A	500.0	0	None
SemiBold	wght	N/A	N/A	N/A	600.0	0	None
Bold	wght	N/A	N/A	N/A	700.0	0	None
ExtraBold	wght	N/A	N/A	N/A	800.0	0	None
Black	wght	N/A	N/A	N/A	900.0	0	None
[code: bad-axis-values]

🔥 FAIL: Check if the vertical metrics of a family are similar to the same family hosted on Google Fonts. (com.google.fonts/check/vertical_metrics_regressions)

• 🔥 FAIL Mada Regular: OS/2 sTypoAscender is 950 when it should be 900 [code: bad-typo-ascender]
• 🔥 FAIL Mada Regular: OS/2 sTypoDescender is -350 when it should be -300 [code: bad-typo-descender]
• 🔥 FAIL Mada Regular: hhea Ascender is 950 when it should be 900 [code: bad-hhea-ascender]
• 🔥 FAIL Mada Regular: hhea Descender is -350 when it should be -300 [code: bad-hhea-descender]

🔥 FAIL: Validate STAT particle names and values match the fallback names in GFAxisRegistry. (com.google.fonts/check/STAT/gf_axisregistry)

• 🔥 FAIL STAT table is missing Axis Value Records [code: missing-axis-values]

🔥 FAIL: Glyph names are all valid? (com.google.fonts/check/valid_glyphnames)

• 🔥 FAIL The following glyph names do not comply with naming conventions: hamza-ar, highhamza-ar, alef-ar, alef-ar.fina, alef-ar.fina.1, behDotless-ar, behDotless-ar.fina, behDotless-ar.medi, behDotless-ar.init, hah-ar and 360 more.

Use -F or --full-lists to disable shortening of long lists.

A glyph name must be entirely comprised of characters from the following set: A-Z a-z 0-9 .(period) (underscore). A glyph name must not start with a digit or period. There are a few exceptions such as the special glyph ".notdef". The glyph names "twocents", "a1", and "" are all valid, while "2cents" and ".twocents" are not. [code: found-invalid-names]

🔥 FAIL: Ensure soft_dotted characters lose their dot when combined with marks that replace the dot. (com.google.fonts/check/soft_dotted)

• 🔥 FAIL The dot of soft dotted characters used in orthographies must disappear in the following strings: i̊ i̋ i̍ i̐ i̓ j̀ j́ j̃ j̄ j̈ į̀ į́ į̂ į̃ į̄ į̌ ɨ̀ ɨ́ ɨ̂ ɨ̃ ɨ̄ ɨ̈ ɨ̋ ɨ̌ ɨ̏ ɨ̧̀ ɨ̧́ ɨ̧̂ ɨ̧̌ ɨ̱̀ ɨ̱́ ɨ̱̈ ị̀ ị́ ị̂ ị̃ ị̄

The dot of soft dotted characters should disappear in other cases, for example: i̅ i̇ i̒ i̦̅ i̦̇ i̦̊ i̦̋ i̦̍ i̦̐ i̦̒ i̦̓ i̧̅ i̧̇ i̧̊ i̧̋ i̧̍ i̧̐ i̧̒ i̧̓ i̩̅ [code: soft-dotted]

🔥 FAIL: STAT table has Axis Value tables? (com.adobe.fonts/check/stat_has_axis_value_tables)

• 🔥 FAIL STAT table has no Axis Value tables. [code: no-axis-value-tables]

⚠ WARN: Glyphs are similiar to Google Fonts version? (com.google.fonts/check/production_glyphs_similarity)

• ⚠ WARN Following glyphs differ greatly from Google Fonts version:
  • .notdef
  • AE
  • Acircumflex
  • Aring
  • Eth
  • Euro
  • ampersand
  • cent and oslash

⚠ WARN: Name table strings must not contain the string 'Reserved Font Name'. (com.google.fonts/check/name/rfn)

• ⚠ WARN Name table entry contains "Reserved Font Name" for a family name ("Source") that differs from the currently used family name (Mada), which is fine. [code: legacy-familyname]

⚠ WARN: Ensure fonts have ScriptLangTags declared on the 'meta' table. (com.google.fonts/check/meta/script_lang_tags)

• ⚠ WARN This font file does not have a 'meta' table. [code: lacks-meta-table]

⚠ WARN: Detect any interpolation issues in the font. (com.google.fonts/check/interpolation_issues)

• ⚠ WARN Interpolation issues were found in the font: - Contour order differs in glyph 'command': [0, 1] in <fontTools.ttLib.ttGlyphSet._TTGlyphSetGlyf object at 0x11fe828b0>, [1, 0] in <fontTools.ttLib.ttGlyphSet._TTGlyphSetGlyf object at 0x11fe2b280>. [code: interpolation-issues]

ℹ INFO: Show hinting filesize impact. (com.google.fonts/check/hinting_impact)

• ℹ INFO Hinting filesize impact:

	Mada.ttf
Dehinted Size	190.0kb
Hinted Size	190.0kb
Increase	-24 bytes
Change	-0.0 %
[code: size-impact]

ℹ INFO: Font has old ttfautohint applied? (com.google.fonts/check/old_ttfautohint)

• ℹ INFO Could not detect which version of ttfautohint was used in this font. It is typically specified as a comment in the font version entries of the 'name' table. Such font version strings are currently: ['Version 1.000'] [code: version-not-detected]

ℹ INFO: EPAR table present in font? (com.google.fonts/check/epar)

• ℹ INFO EPAR table not present in font. To learn more see fonttools/fontbakery#818 [code: lacks-EPAR]

ℹ INFO: Familyname must be unique according to namecheck.fontdata.com (com.google.fonts/check/fontdata_namecheck)

• ℹ INFO The family name "Mada" seems to be already in use.
  Please visit http://namecheck.fontdata.com for more info. [code: name-collision]

ℹ INFO: Check for font-v versioning. (com.google.fonts/check/fontv)

• ℹ INFO Version string is: "Version 1.000"
  The version string must ideally include a git commit hash and either a "dev" or a "release" suffix such as in the example below:
  "Version 1.3; git-0d08353-release" [code: bad-format]

ℹ INFO: Font contains all required tables? (com.google.fonts/check/required_tables)

• ℹ INFO This font contains the following optional tables:

  • loca

  • GPOS

  • GSUB [code: optional-tables]

ℹ INFO: List all superfamily filepaths (com.google.fonts/check/superfamily/list)

• ℹ INFO . [code: family-path]

Summary

💔 ERROR	🔥 FAIL	⚠ WARN	💤 SKIP	ℹ INFO	🍞 PASS	🔎 DEBUG
0	9	4	101	8	120	0
0%	4%	2%	42%	3%	50%	0%

Note: The following loglevels were omitted in this report:

• SKIP
• PASS
• DEBUG

Autohint the fonts

I need to run both AFDKO’s autohint and ttfautohint on the fonts. Need to figure out the right settings for both.

TTFs

Please provide TTFs :)

Our ss01 clashes with Soure Sans one

Support automatic fractions

HarfBuzz enables fraction for 111⁄222 or ١١١⁄٢٢٢ automatically, but we need to include the features in the font.

some italic fonts not working

hello,
the following files are not working properly somehow:

• extra light italic
• light italic
• italic

neither macOS nor fontexplorer X (latest versions of both) seem to be able to preview nor install them.

and google fonts does not provide italics at all? :-/

thanks in advance, looking forward to some insight about this

letters connecting issues?

and i think the issue is with the anchor on U-FEF2 & U-FEF0

Uyghur and Kazakh variant for ۇ

The letter ۇ has a special shape in Uyghur and Kazakh texts, in this case dammah looks like comma.

Build a variable font

Persian and Urdu digits

connecting bug with yeh fina

basically this is the only bug i came across while testing mada

Small things in mada-0.3.zip

• In mada-0.3.zip there are 3 font files in OTF and TTF:
• mada-black.otf
• mada-medium.otf
• mada-thin.otf

These should have the filenames

• Mada-Black.otf
• Mada-Regular.otf
• Mada-Thin.otf

and same for the TTFs. I made some notes on this in https://github.com/googlefonts/gf-docs/blob/master/ProjectChecklist.md#instance-and-file-naming

• The head.fontRevision is 0.29999 but this should be 1.x because some systems will reject fonts with a version less than 1.0. I made some notes on this in https://github.com/googlefonts/gf-docs/blob/master/ProjectChecklist.md#versioning

• In Black, the macStyle bold bit should not be set.

• The copyright notice in the fonts is currently

  Portions copyright © 2015-2016, Khaled Hosny (<[email protected]>). Portions copyright 2010, 2012, 2014 Adobe Systems Incorporated (http://www.adobe.com/), with Reserved Font Name 'Source'.

This string should be ascii, and since there are multiple copyright holders,

Please set it up like https://github.com/NDISCOVER/Arima-Font

• In that release zip, the README is blank
• The name table is not set up for Black and Thin to work on Windows GDI, which is a core requirement :) https://github.com/googlefonts/gf-docs/blob/master/ProjectChecklist.md#instance-and-file-naming has details
• Mada-Thin.ttf os/2 usWeightClass is 100 but should be 120
• Mada-Thin 'hmtx' '.notdef' lsb should be 0 but is 33
• Mada-Regular.ttf fsType expected 0 but is 8
• Mada-Regular.ttf 'hmtx' '.notdef' should be 0 but is 33

Fix underline position

Duplication of Regular font by different names: Mada.otf and Mada-Regular.otf

Two fonts are available with Regular style, one needs to be removed

Wrong mark position under جِ

Minor things

Thin

Technical Problems: Points are sometimes missing at extrema

Design Mistakes: uni00AD ( this glyph is not meant to contain a shape or have a width ), /Euro (shape seems to be a mistaken interpolation or something.) having /guillemotleft/guillemotright but not /guilsinglleft/guilsinglright seems odd, brokenbar (the gap is too small), /underscore (this should no have gaps - the opposite in fact - it should overlap itself when set)

Suggestions for improvement: yen ( stokes closer together than is ideal now - move them apart), /asciicircum (a little taller please), please include /ellipsis/bullet/emdash/endash

Medium

as above but also - Euro missing

Black

as above but also - Euro missing

U+03C6 and U+03D5 are swapped

The glyphs of U+03C6 GREEK SMALL LETTER PHI and U+03D5 GREEK PHI SYMBOL are swapped: U+03D5 should have the ascender.

Source for documentation

Are the sources for https://github.com/khaledhosny/mada/blob/master/documentation/mada-table.pdf in the repo?

Strange rendering of the 'A' in all caps 900 weight

Hello,

Thanks for a beautiful font! I just want to make sure this is not intentional but the all caps A character is rendering with some artifact when using as web font. Inside Photoshop, font renders as expected. The issue is most noticeable in the 900 weight in all cups. Please attached.

Thank you.

Addition of Arabic Presentation Forms

Would it be possible to add the characters from Arabic Presentation Forms-B (https://en.wikipedia.org/wiki/Arabic_Presentation_Forms-B) and the applicable characters from Arabic Presentation Forms-A (https://en.wikipedia.org/wiki/Arabic_Presentation_Forms-A)?

Example from Arial Unicode MS

Use fontmake to build the final fonts

Instead of calling ufo2ft directly, just prepare the master UFOs then process them with fontmake.

Why is final yeh disconnected by default?

Repeating #10 and #24, I spoke with Gaber about this, and neither of us understand why the default is not a smooth connection with the baseline, while ss01 is designed to be smooth and connecting.

Could you explain why you prefer having the default and ss01 designs this way, and if you would consider inverting them? :)

Designspace file is out-dated

It lists Medium as a master, whereas in reality Regular is a master.

Self-intersecting glyphs

Some glyphs intersect themselves in such a way that, at least in Chrome and Firefox, the overlaps appear white. Examples include U+0041 LATIN CAPITAL LETTER A, U+0472 CYRILLIC CAPITAL LETTER FITA, and U+0030 DIGIT ZERO with 'ss05'. Not all self-intersecting glyphs have this problem.

Arabic letters (Meem and Khah)

Arabic letters issues (Meem and Khah)

OS: Ubuntu (Linux/Unix-like)
App: File Manager
Font version: 1.3
Font type: TTF
Font size: 10px

Meem: meem end show like meem begin.
Khah: khah dot continue (Show like a line)

Mada font

Segoe UI font (same conditions)

Dots overlap in final/islated چ

We need an alternate glyph without the lower stroke.