notofonts / arabic Goto Github PK

notofonts/noto-source#115

Font: 'NotoSansArabic'
Version: latest

So I downloaded the font and installed it on my Nexus 5X via rooted iFont app. There is Tofu in the interface. Moreover, the spacing is so off for the parts where latin characters come that they are being cut off in the UI.

I know this is a very UI specific issue but shouldn't the font be designed in a way that the font and UI work in harmony.

Also, is there any way to combine the roboto and Noto Urdu in way that these issues can be resolved.

Link to screenshots:
https://goo.gl/photos/Zy8EkMzK9E2fs6nBA
https://goo.gl/photos/MB3NHWMji436Mdxt5
https://goo.gl/photos/T8zXpQ81xqiXuPVJ7
https://goo.gl/photos/qETY5zpCtVhUnnAU6

Also,
This font (Noto Sans Urdu) is readable, and can be understood, but only few number are in Arabic style Such as date 2016 digit 6 is in Arabic form and can be hard for normal readers to understand. It is easily read able.

I have an application. There is a user whose name is "Nargis". She is unable to type her name. When she types نرگس , it shows as نرگھس۔ When i wrote in notepad, it is showing correct but when i wrote in application or cope from notepad. It shows as نرگھس.

The word god (اللٌهُ) (alif, lam, lam, shadda, superscript (dagger) alif and ha) has some issues with placing diacritic. Apparently Noto Sans Arabic designed to automatically add the shaddah and superscript (dagger) on the top of the letter lam (second lam). This feature is fine and commonly used by other fonts, however, it should take care of the existing diacritic entered by writer to avoid overlapping or make it grammatically wrong. Keeping in mind this word is commonly used in the middle east (Arabic,Urdu etc. speakers).

Font

NotoSansArabic-Regular.ttf

Where the font came from, and when

Site: https://noto-website-2.storage.googleapis.com/pkgs/NotoSansArabic-unhinted.zip
Date: 2018-02-04

Font Version

Version 2.000;GOOG;noto-source:20170915:90ef993387c0

Issue

Noto Sans Arabic’s U+FDFB ARABIC LIGATURE JALLAJALALOUHOU glyph has a dot under the heh, on the left side. The dot should instead be under one of the jeems, on the right side.

Character data

ﷻ
U+FDFB ARABIC LIGATURE JALLAJALALOUHOU

Screenshot

Tested NotoNaskhArabicU on Android and noticed if I place more than one diacritic on the top of character or if diacritic placed on the top of hamza it will be clipped and not displayed correctly. This test case just an example and could be found in many other cases. I used NotoNaskhArabicUI Version 1.06 uh pulled from Android most recent build. String tested"أُوْلَئِكَ" on Keep App and on our personal tool.

Font

NotoSansArabic-Regular.ttf

Where the font came from, and when

Site: https://noto-website-2.storage.googleapis.com/pkgs/NotoSansArabic-unhinted.zip
Date: 2018-02-04

Font Version

Version 2.000;GOOG;noto-source:20170915:90ef993387c0

Issue

U+06D1 ARABIC LETTER YEH WITH THREE DOTS BELOW, a dual-joining character, has no glyphs for its initial and medial forms.

Character data

ۑۑـ
U+06D1 ARABIC LETTER YEH WITH THREE DOTS BELOW
U+06D1 ARABIC LETTER YEH WITH THREE DOTS BELOW
U+0640 ARABIC TATWEEL

Screenshot

Moved from googlei18n/noto-alpha#235
Imported from Google Code issue notofonts/noto-fonts#235 created by [email protected] on 2014-05-24T01:00:01.000Z:

We need support for the following two punctuation marks in the Arabic Naskh fonts, which are needed to support Sindhi:

U+2E41 REVERSED COMMA
U+204F REVERSED SEMICOLON

/cc @roozbehp
/cc @kmansourMT

In Noto Naskh Arabic, any diacritic over the letter ghain (063A), in its isolated form only (FECD), superimposes the dot instead of appearing above it. The diacritic appears correctly over the final ghain (FECE).
(Windows 10)

Hi,

There is one Ya (ی) in Arabic. the dots beneath, in"ي" represents not the word itself but an accent. Historically, it has had its own keyboard shortcut in Windows 1251 which is "Ctrl+X"; yet the notation is used even if it is not intended for normal Ya (keyboard key "D").

I think a fix can ensure that the dots act as an accent (eg. "D" then "Shift+") just like Fatha, Kasra, and Zama (respectively ـُــِــَ) and tanween counterparts. This both fixes searches for the character which is a hassle right now and the confusion while typing.

Thanks,

It shows it as its final form when it should be in initial form.

The character is important for Urdu.

Original issue reported on code.google.com by [email protected] on 15 Jul 2014 at 7:15

Font

NotoSansArabic-Regular.ttf

Where the font came from, and when

Site: https://noto-website-2.storage.googleapis.com/pkgs/NotoSansArabic-unhinted.zip
Date: 2018-02-04

Font Version

Version 2.000;GOOG;noto-source:20170915:90ef993387c0

Issue

U+FDF0 ARABIC LIGATURE SALLA USED AS KORANIC STOP SIGN ISOLATED FORM’s compatibility decomposition is U+0635 U+0644 U+06D2, but Noto Sans Arabic renders it as if the last character of the decomposition were U+064A.

Character data

ﷰ صلے
U+FDF0 ARABIC LIGATURE SALLA USED AS KORANIC STOP SIGN ISOLATED FORM
U+0020 SPACE
U+0635 ARABIC LETTER SAD
U+0644 ARABIC LETTER LAM
U+06D2 ARABIC LETTER YEH BARREE

Screenshot

Font

NotoSansArabic-Regular.otf and possibly other Noto Sans Arabic fonts.

Where the font came from, and when

From git master branch.

Issue

Many Arabic lam-alef combinations are either not ligated or not connected at all. They should all be ligated just like لا.

Character data

ڵآ ڶآ ڷآ ڸآ ݪآ ࢦآ ڵأ ڶأ ڷأ ڸأ ݪأ ࢦأ ڵإ
ڶإ ڷإ ڸإ ݪإ ࢦإ ڵا ڶا ڷا ڸا ݪا ࢦا ڵٱ ڶٱ
ڷٱ ڸٱ ݪٱ ࢦٱ لٲ ڵٲ ڶٲ ڷٲ ڸٲ ݪٲ ࢦٲ لٳ ڵٳ
ڶٳ ڷٳ ڸٳ ݪٳ ࢦٳ لٵ ڵٵ ڶٵ ڷٵ ڸٵ ݪٵ ࢦٵ لݳ
ڵݳ ڶݳ ڷݳ ڸݳ ݪݳ ࢦݳ لݴ ڵݴ ڶݴ ڷݴ ڸݴ ݪݴ ࢦݴ

Screenshot

They should all look like (with different dots etc. of course):

Font

NotoSansArabic-Regular.ttf

Where the font came from, and when

Site: https://noto-website-2.storage.googleapis.com/pkgs/NotoSansArabic-unhinted.zip
Date: 2018-01-14

Font Version

Version 2.000;GOOG;noto-source:20170915:90ef993387c0

Issue

U+06DF ARABIC SMALL HIGH ROUNDED ZERO and U+06E0 ARABIC SMALL HIGH UPRIGHT RECTANGULAR ZERO look confusingly similar. At normal text sizes, it is hard to tell which is which. U+06E0 should be taller.

Character data

ا۟ا۠
U+0627 ARABIC LETTER ALEF
U+06DF ARABIC SMALL HIGH ROUNDED ZERO
U+0627 ARABIC LETTER ALEF
U+06E0 ARABIC SMALL HIGH UPRIGHT RECTANGULAR ZERO

Screenshot

See:
https://bugs.freedesktop.org/show_bug.cgi?id=85873

The font should have a stopper rule to match mark1,CGJ,mark2 to stop ligation...

Defect Report

Use this template for filing a defect report. For feature requests and other matters, you can use part of the template and delete what you don't need.

Title

ARABIC THOUSANDS SEPARATOR (U+066C) is in the wrong place

Font

Full file name, for example 'NotoSansArmenian-Regular.ttf'.
You can upload the problem font here unless it is a Chinese, Japanese or Korean font (these are large).

Where the font came from, and when

Pre-installed on Pixel 2 phone

Font Version

• Mac - right mouse click on a font and try Preview to see version info.
• Win -- right mouse click on a font (Local Disc > Windows > Fonts) and see version info on Properties.
• Linux -- use (Gnome) Font Viewer: open a font and click on Info tab.

OS name and version

Android 8.1.0

Application name and version

No, it is reproducible in many apps.

Issue

ARABIC THOUSANDS SEPARATOR (U+066C) is in the wrong place.

1. Open an app
2. Enter a few numbers and a thousand separator.
3. Thousand separator appears right on the base line rather than toward head of digits.

Unicode chart, technical specs, shaping info, comparison with non-Noto fonts, comparison with earlier version of the same font (regression cases)

Character data

۶٬۶۷۸

Screenshot

Attached.

Tools for reporting bugs

Useful tools for reporting bugs are available at: https://github.com/googlei18n/

Harfbuzz hb-view and hb-shape

These are part of the HarfBuzz distribution and can help isolate if an issue is in the app/OS, shaping engine, or font.

• hb-view renders the text with the exact font (for example, to see how ligatured characters shape) using your installed version of HarfBuzz.

For example:

  hb-view --font-file {path to font} --text-file {path to text file} --output-file '{sample}.png'

• hb-shape shows glyph selection and positioning

Fontview

• Fontview displays the text.

Fontdiff

• Fontdiff displays the text using two versions of the font side by side.

The presence of the glyph in the Thaana font is forcing weird behavior in Android, causing the Thaana font to get selected for the colon in a sequence such as <ARABIC-INDIC DIGIT ONE, ALM, COLON>. Of course Android should know better (I'll file a separate bug for that), but the fonts should be cleaner too.

The Nastaliq font is not shipped on Android devices, but should have the glyph removed too.

PS: If there's a legitimate reason for Nastaliq and Thaana fonts to support ALM, then all fonts for scripts whose letters default to bidi=AL should have support ALM.

/cc @raphlinus

Android uses light/thin typeface on lockscreen and some other places, it would be nice if noto (or roboto?) had light Arabic-Indic and Persian digits or a complete light Arabic font support.

FDF2 الله ARABIC LIGATURE ALLAH ISOLATED FORM
≈ 0627  0644  0644  0647 

using HTML print the char "xFDF2"
Expected: see

the attachment.
Actual: it displayed as لله

Sue, this is a high priority bug. We want it to be fixed ASAP, better to be within a month.

The following string pattern causes the text to break apart for Noto Naskh Arabic v1.060 downloaded from https://www.google.com/get/noto/

On any given line, if the line contains an Alef with Hamza above أ or below إ and ends with a ligature followed by blank space, the entire line exhibits weird rendering issues.

Example problematic strings (note that they end with a blank space):

Example 1 (has Alef w/ Hamza above & ends with لا + space)

أرشيف المدرسة لا

Result on OS X 10.11.6 https://i.imgur.com/C00VRQ6.png
Result on iOS 9.3 https://i.imgur.com/qDte4yw.png

Example 2 (has Alef w/ Hamza above & ends with الله + space)

ونبدأ بسم الله

Result on OS X 10.11.6 https://i.imgur.com/eT99qe1.png
Result on iOS 9.3 https://i.imgur.com/ZApvMTA.png

Note the position of the caret-- goes to end of line.

A similar behavior is also present in Noto Nastaliq Urud & the Mirza font https://github.com/Tarobish/Mirza which I downloaded from fonts.google.com so I'm thinking maybe a problem with a common toolchain or OT code? Just guessing.

Thanks!

Font

Noto Sans Arabic

Where the font came from, and when

Site: https://noto-website-2.storage.googleapis.com/pkgs/Noto-hinted.zip
Date: 2017-12-19

Font Version

Version 2.0000

Issue

Some ligatures in Uyghur text is wrong, for example, چە (che) in ئۇيغۇرچە (uyghurche), ھە (he) in ھەر (her), گە (ge) in گەۋدىلىك (gewdilik).

Image

NotoSansArabic static font place diacritics lower than supposed, when it become to the alef with hamza diacritics will be placed under the hamza, for e.g. (U+0623 U+064F). Please check attached.

Font downloaded from https://github.com/googlei18n/noto-fonts/tree/master/alpha/from-pipeline/unhinted/ttf/sans

Comparing NotoNaskhArabicUI with NotoSansArabicUI and noticed the bottom baseline is higher for NotoNaskhArabicUI, this could cause some clipping problems and unaligned string when multiple script used in one sentence. Please check screenshot

SIL have made a list of language specific form for mark positioning and character variants:

Additionaly I found the letter ۇ has a variant in Uyghur, its diacritic should be comma shaped, not 9 shaped, if you go to Xinjiang, PR China, you will see it everywhere.

Font

NotoSansArabic-Regular.ttf

Where the font came from, and when

Site: https://noto-website-2.storage.googleapis.com/pkgs/NotoSansArabic-unhinted.zip
Date: 2018-01-14

Font Version

Version 2.000;GOOG;noto-source:20170915:90ef993387c0

Issue

The diacritics in U+FDFD are inconsistent and wrong. The sukun on the seen in the first line has a different shape from the sukun on the hah in the second line. It is odd for the first sukun to be above the tatweel as opposed to directly above the seen. All three of these alefs can take a wasla, so it is inconsistent that only the second has a wasla. There are a couple of harakat between the lines on the left side; I am not sure whether they were intended to be fathas or kasras, but either all the harakat should be included or none should be. There is a strange short vertical line below the yeh in the second line; perhaps it is supposed to be the superscript alef which is missing above the shadda in the first line.

Character data

﷽
U+FDFD ARABIC LIGATURE BISMILLAH AR-RAHMAN AR-RAHEEM

Screenshot

I noticed that Noto Naskh Arabic has trouble with the الله ligature, at least in Pages on Mac (OSX 10.12.1). Typing the word crashed the program, as did having it typed in one font, and then trying to change fonts to Noto Naskh Arabic. I was hoping the screenshot would capture the spinning-wheel of the mouse, but you can at least see that the font selection menu is stuck in gray. This is the point when Pages became unresponsive and I had to Force Quit.

When I browsing Wikipedia article Pentaglot Dictionary with Noto Nastaliq, I found several Arabic characters looks so different within text, see my screenshot.

Font

NotoNaskhArabic-Regular.ttf

Where the font came from, and when

Site: https://noto-website-2.storage.googleapis.com/pkgs/NotoNaskhArabic-unhinted.zip
Date: 2018-02-04

Font Version

Version 1.07 uh

Issue

The diacritics in U+FDFB are inconsistent and wrong. The glyph looks like it reads ⟨جَل جَّلُٰالُهُ⟩. The shadda–fatha combination should be above the first lam, not above a jeem. If one jeem has a fatha, so should the other. The second damma (above the lam) should be a fatha. Either the first damma (above the superscript alef) should be a madda, or the superscript alef and damma should be deleted; I am not sure a superscript alef can occur before an alef like that, so you should ask a native speaker of Arabic which fix is appropriate.

Character data

ﷻ
U+FDFB ARABIC LIGATURE JALLAJALALOUHOU

Screenshot

Noto Sans Arabic (alpha?) and Noto Naskh need Kashmiri GSUB lookups for digits. The digit forms used in Kashmiri are identical to the Urdu forms, so the GSUB information can simply be copied from Urdu.

This is very important for users in India, since Kashmiri is one of the scheduled/official languages of India.

Sindhi digits shapes are different from the Persian and Urdu digits shapes. So Noto Sans Arabic needs a separate GSUB lookup for Sindhi digits. The information in Noto Naskh Arabic is correct for Sindhi, so it could be copied to Noto Sans Arabic. (See also https://github.com/googlei18n/noto-fonts/issues/975.)

I expect that fonts in a path that contains the substring unhinted are really unhinted. However, some files do have bytecode, and what makes it really ugly is that this bytecode is invalid (i.e., causing endless loops).

Some affected fonts:

NotoSansArabic-*.ttf
NotoSansArmenian-*.ttf
NotoSansDisplay-BlackCond-*.ttf

etc., etc. – maybe an artifact from buggy font instance generation?

I don't have enough time to check all fonts, so I suggest that you call a tool (e.g., ttfautohint :-) ) to remove all hints from everything.

I am not professional in typeface design nor in Arabic, so excuse me if I'm wrong.

Font

Noto Sans Arabic

Where the font came from, and when

Site: https://noto-website-2.storage.googleapis.com/pkgs/NotoSansArabic-hinted.zip
Date: 2017-12-31

Font Version

2.000;GOOG;noto-source:20170915:90ef993387c0; ttfautohint (v1.7)

OS name and version

Windows 10, 1709

Application name and version

Microsoft Word, as well as Photoshop CC 2018

Issue

If I insert tashkils, such as FATHA (U+064E) and KARSA (U+0650), after the ligature LAM (U+0644) + ALEF WITH HAMZA (U+0623/U+0625), the tashkils are placed crossing the hamza rather than above/below it. However, the tashkils works well after standalone ALEF WITH HAMZA.

This problem is not found in Noto Naskh though.

Character data

لأَ لإِ

U+0644 ARABIC LETTER LAM
U+0623 ARABIC LETTER ALEF WITH HAMZA ABOVE
U+0625 ARABIC LETTER ALEF WITH HAMZA BELOW
U+064E ARABIC FATHA
U+0650 ARABIC KARSA (but other tashkils should do as well)

Screenshot

The Arabic ray symbol is نق (short of نصف القطر) but the current symbol in Noto Naskh Arabic and Noto Sans Arabic looks more like a stylised ق. This symbol is used in math where it will be used standalone with no much context and I have been told students (the main audience of Arabic math) have difficulty recognizing it.

I suggest adding a tooth to the horizontal stroke so it looks more like a dotless نق.

NotoSansArabicUI static and variable connect some letters that should stay disconnected, for example letter waw (U+0648) get connect with letter ain (U+0639). see the images below

@nizarsq : could you write the text for me so I can test it ? are there more letters that are connected but shouldn't be connected? Once you answer please assign it to me. Thank you.

Font

NotoSansArabic-Regular.ttf

Where the font came from, and when

Site: https://noto-website-2.storage.googleapis.com/pkgs/NotoSansArabic-unhinted.zip
Date: 2018-02-04

Font Version

Version 2.000;GOOG;noto-source:20170915:90ef993387c0

Issue

The three dots of U+08AE ARABIC LETTER DAL WITH THREE DOTS BELOW and U+08AF ARABIC LETTER SAD WITH THREE DOTS BELOW should point down, but in Noto Sans Arabic they point up.

Character data

ࢮࢯ
U+08AE ARABIC LETTER DAL WITH THREE DOTS BELOW
U+08AF ARABIC LETTER SAD WITH THREE DOTS BELOW

Screenshot

On android and Mac NotoSansArabic-GX, NotoSansArabicUI-GX have an issue with using diacritics. When any diacritics placed on a letter the next letter be pushed foreword (like there is space), in case letters are connected it will disconnect. Please see attached screenshots.

For example see the attached screen shot. It is properly placed for Lam but for Fah it is merged with the letter rather than being placed under it. "Screenshot_2.png" shows the correct placement of kasra with Fah.

Font

NotoSansArabic-Regular.ttf

Where the font came from, and when

Site: https://noto-website-2.storage.googleapis.com/pkgs/NotoSansArabic-unhinted.zip
Date: 2018-01-14

Font Version

Version 2.000;GOOG;noto-source:20170915:90ef993387c0

Issue

U+FC5B ARABIC LIGATURE THAL WITH SUPERSCRIPT ALEF ISOLATED FORM and U+FC5C ARABIC LIGATURE REH WITH SUPERSCRIPT ALEF ISOLATED FORM do not look like the sequences to which they decompose under NFKC: the superscript alefs should be above the base letters but are instead to the right.

Character data

ﱛﱜذٰرٰ
U+FC5B ARABIC LIGATURE THAL WITH SUPERSCRIPT ALEF ISOLATED FORM
U+FC5C ARABIC LIGATURE REH WITH SUPERSCRIPT ALEF ISOLATED FORM
U+0630 ARABIC LETTER THAL
U+0670 ARABIC LETTER SUPERSCRIPT ALEF
U+0631 ARABIC LETTER REH
U+0670 ARABIC LETTER SUPERSCRIPT ALEF

Screenshot

Noto Kufi Arabic doesn't render in Powerpoint on Windows.

After installing Onto Kufi Arabic, restarting Powerpoint and entering text with Noto Kufi Arabic selected, a default font appears instead of the expected font.

It does, however work as expected in:

• Word on Windows
• Powerpoint on Mac OS.

Office 365: version 16.0.8067.2115
OS: Windows 10 Enterprise

Font: NotoKufiArabic-Regular.ttf
From: https://raw.githubusercontent.com/googlei18n/noto-fonts/master/hinted/NotoKufiArabic-Regular.ttf
Date: 2017-05-30
Version: 1.04

azb: "تۆرکجه", lrc: "لۊری شومالی" and ug: "ئۇيغۇرچە" are names of Arabic script written languages which have characters Noto Nastaliq doesn't support ("ۆۊۇە"). Is it possible to add just this limited set of characters so language link(*) section of Urdu Wikipedia articles won't have broken text?

Thank you.

(*) Language link is a right side menu (left hand, on English Wikipedia) of Wikipedia pages which shows correspond pages of an article in other Wikipedia languages and it uses the native language name of that Wikipedia languages, e.g. an article on Urdu Wikipedia which in order to see the issue you should apply Noto Nastaliq Urdu manually there.

The hyphen characters in Noto Naskh Arabic UI fonts are too low. They are supposed to be vertically aligned with the horizontal stems of the Arabic letters (which is shifted up in Arabic UI fonts), but instead they are on the font baseline. They should be shifted up the same amount as the Arabic letters, so they would have the appearance of being on the baseline.

(Note that this only happens in the UI fonts. The non-UI fonts have both the baseline for the Arabic letters and the hyphens at the actual font baseline.)

Font

NotoNastaliqUrdu-Regular.ttf
NotoSansArabic-Regular.ttf

Where the font came from, and when

Site: https://noto-website-2.storage.googleapis.com/pkgs/NotoNastaliqUrdu-unhinted.zip
Site: https://noto-website-2.storage.googleapis.com/pkgs/NotoSansArabic-unhinted.zip
Date: 2018-02-04

Font Version

Noto Nastaliq Urdu: Version 1.02 uh
Noto Sans Arabic: Version 2.000;GOOG;noto-source:20170915:90ef993387c0

Issue

U+06D5 ARABIC LETTER AE, a right-joining character, has no glyph for its final form.

Character data

ئە
U+0626 ARABIC LETTER YEH WITH HAMZA ABOVE
U+06D5 ARABIC LETTER AE

Screenshot

Hyphen characters (U+002D and U+2010) are needed in fonts in scripts that use hyphenation. This would help creating a hyphen shape that's most appropriate for the script, and potentially apply kerning and such around the characters.

For example, both Armenian and Ethiopic use hyphens, while the Noto Sans Armenian and Noto Sans Ethiopic don't have any hyphen characters.

In Android, we are temporarily applying a hack to copy the hyphen from the LGC fonts, but that's not sustainable. (See internal bug b/21570828 for more information.)

    from nototools import coverage
    from nototools import fix_khmer_and_lao_coverage as merger

    FONTS = [
        'NotoSansArmenian-Regular.ttf',
        'NotoSansArmenian-Bold.ttf',
        'NotoSerifArmenian-Regular.ttf',
        'NotoSerifArmenian-Bold.ttf',
        'NotoSansEthiopic-Regular.ttf',
        'NotoSansEthiopic-Bold.ttf',
    ]

    HYPHENS = {0x002D, 0x2010}

    for font_name in FONTS:
        lgc_font_name = (font_name.replace('Armenian', '')
                                  .replace('Ethiopic', ''))

        chars_to_add = ((HYPHENS - coverage.character_set(font_name))
            & coverage.character_set(lgc_font_name))

        if chars_to_add:
            merger.merge_chars_from_bank(
                font_name,
                lgc_font_name,
                'with-hyphen/'+font_name,
                chars_to_add)

Assigning to Doug for now to figure out the list of scripts that need hyphens. A good starting point is the list of automatically-hyphenated languages from http://tug.org/svn/texhyphen/trunk/hyph-utf8/tex/generic/hyph-utf8/patterns/txt/.

/cc @raphlinus @brawer @roubert

Clipped diacritics noticed when NotoSansArabic-GX and NotoSansArabicUI-GX used, diacritics placed on either the top or the bottom of some characters (high- end and low-end boundaries characters) those diacritics will either partially clipped or fully clipped (disappeared). Tested this string "بليغٍ مسلمةٌ" on Android, FontView and Keep App and the results showing as the following:
1-FontView, diacritics on the top show clipping on the bottom appear to be fine.
2-Keep, shows clipping for both top and the bottom diacritics.
3-Personal tool, shows clipping for both top and the bottom diacritics.

Please check attached screenshots

The following Arabic sequences were reported as clipping in the NotoNaskhArabicUI font. They shouldn't be clipping.

U+0623 U+064E (common)
U+0623 U+064B (very rare)
U+0623 U+064F (common)
U+0623 U+064C (very rare)
U+0623 U+0652 (happens sometimes in Persian, possibly other languages too)
U+0625 U+0650 (common)

Five of the above go outside the vertical extent for the UI fonts:

أَ (170, 2231)
أً (170, 2314)
أُ (170, 2344)
أٌ (170, 2344)
أْ (170, 2285)
where vertical UI box is (2163, -555).

These sequences also have a problem with Noto Sans Arabic UI.

أً (0, 1219)
أُ (0, 1235)
أٌ (0, 1244)
أْ (0, 1199)
إِ (-430, 714)
where the vertical UI box is (1056, -270)

moved from https://github.com/googlei18n/noto-alpha/issues/278

Imported from Google Code issue notofonts/noto-fonts#278 created by [email protected] on 2015-01-15T01:32:27.000Z:

In the Naskh Bold font, two [classes of] glyphs stick out as inconsistent with the regular font, the initial form of Feh and the final form of Alef.

For the Feh, the design is very different from the regular font and appears to have a sharp corner at the bottom right side too.

For the Alef, the contrast between the bottom and the top is too much, again resulting in a appearance of it being a bit broken at the connection point to the horizontal stroke.

Note that other glyphs in the same families (initial Qaf, final Alef-Madda, etc) have the same issues as they share the outlines.

I'm attaching a sample comparing Regular and Bold. It shows the problem somehow, but the problem is much more visible when you see these in running text, such as the GMail app on Android. The initial Feh and Final Alef in the bold font really stick out there, especially in words containing both as فا.

Naskh (top) and Naskh Bold (bottom)

Geeza Pro on OS X has it, and so does Jameel Noori Nastaleeq.

Font

NotoNaskhArabic-Regular.ttf
NotoNastaliqUrdu-Regular.ttf

Where the font came from, and when

• Noto Naskh Arabic
  Site: https://noto-website-2.storage.googleapis.com/pkgs/NotoNaskhArabic-hinted.zip
  Date: 2018-01-10
• Noto Nastaliq Urdu
  Site: https://noto-website-2.storage.googleapis.com/pkgs/NotoNastaliqUrdu-unhinted.zip
  Date: 2016-10-27

Font Version

Noto Naskh Arabic: 1.07
Noto Nastaliq Urdu: 1.02 uh

OS name and version

Windows 10 v1709

Application name and version

LibreOffice 6.0.0.1 (This is already bundled Noto Naskh Arabic 1.06, but I replacing the Naskh font by newer version after installation)

Issue

If I insert Arabic subtending marks (U+0604, U+0601), they should placing a horizontal stroke under numbers. However is doesn’t appear with Noto Naskh Arabic and Noto Nastaliq Urdu, even if I insert RLO and PDF characters surrounding them as an instruction mentioned in this page. The usage of these subtending marks have documented in N3734.

Screenshot

In Regular, 06A4 06A6 06A8 08A4 (veh, peheh, qaf with three dots above, feh with dot below and three dots above) have initial forms that don’t match the initial forms of 0641 0642 (feh, qaf) while they do in Bold.

Here’s:
ققق ففف ڨڨڨ ڤڤڤ ࢤࢤࢤ ڦڦڦ