aliftype / aref-ruqaa Goto Github PK

when you use Microsoft word everything is OK, but in print lam alef letters appear separate ... in illustrator, it appears separate all the time as the image attached

Blocked on https://forum.glyphsapp.com/t/allow-color-palette-indices-in-color-layer-colors/20937

Hello! I want to thank you for creating such a beautiful and proportional Aref Ruqaa font!
I am a native speaker of the Crimean Tatar language and the Crimean Tatars actively used the handwriting "hand". There is one letter in the Crimean Tatar alphabet that is not in your font - the letter ڭ. (By the way, this letter is also in the Ottoman alphabet). This is a mandatory letter, and I miss it so much when I write in Crimean Tatar in your font!
I ask you to add this letter to your font.
The letter should look like this:

مرحبًا! أود أن أشكركم على إنشاء خط عارف الرقعة الجميل والمتناسب!
أنا متحدث أصلي للغة تتار القرم وكان تتار القرم يستخدمون بنشاط خط اليد "رقعة". هناك حرف واحد في الأبجدية التتار القرم ليس في الخط الخاص بك - الحرف ڭ. (بالمناسبة ، هذا الحرف موجود أيضًا في الأبجدية العثمانية). هذه رسالة إلزامية ، وأفتقدها كثيرًا عندما أكتب بلغة تتار القرم بالخط الخاص بك!
أطلب منك إضافة هذه الرسالة إلى الخط الخاص بك.
يجب أن تبدو الرسالة كما يلي:

![Снимок экрана (1468)](https://user-images.githubusercontent.com/113206717/189544807-ae922516-3d63-47e7-a97e

-c76872827ab3.png)

Which makes such words look a bit out of place, especially as many layouts don't work with such variance in word heights. I'm sure it's part of the Ruqaa style, but I hope it can be reduced a bit.

See how high the meem is compared to the letters in the succeeding word.

Other than that (and some minor diacritic collisions) the font is wonderful.

Font version 0.8

Could you fix the Alef alignment... i think it should be bit down. the one in the gree is right way, i guess

Arabic Letter Ain with Three Dots Above that prefixes the کا and کل ligatures (and other variants of Keheh) has its dots overlap with the Keheh's top stroke.

But other letters that adjoins before the کا and کل ligatures seems to join fine.

Hi Khaled,

I'm commissioned to onboard Aref Ruqaa Ink to Google Fonts.

Before I can even check the provided files, I need to ask you to please provide TTF files in the repository. Sadly I couldn't get anything to build:

(aref) yanone@Yanones-MBP aref-ruqaa % make ttf            
   BUILD  ArefRuqaa-Regular.ttf
/Users/yanone/Projekte/Google/Onboarding/aref-ruqaa/aref/bin/python3: No module named fontmake

Thank you.

dear Khaled,

could you please fix this small flaw in Aref-Ruqaa: it is a shadda on a sin participating to a ya+sin+meem+alif marbuta
ligature. It occurs twice in this title, and it is the main title of the text I'm typesetting, so it really needs to get fixed…

Thanks in advance!

Have you considered using SFDir?

google/fonts#1015 reports an issue with layout

1. Start a Google Docs document. Example: https://docs.google.com/document/d/119Ecj3CocpfK2G49rfxNQ1_SHLjDDReMO3UFROTvIUk/edit?usp=sharing
2. type a lot of spaces with the Aref Ruqaa font
   1. it is easier to see if the spaces are at the beginning or middle of the string
3. Notice how the cursor lags behind

It is hard to describe verbally, but it acts like the display-width of a space is about twice the position-width.

يرجى دعم اخر إصدار من اجهزة ابل حيث ان الخط يظهر كما في الشكل الذي في الصورة

في الاصدار التجريبي الثالث وبالأخص في الخط السميك , حرف ال "ط" يختفي عبد كتابته بعد حرف "ل" مثل الطبيب , الطبيعي ....

السلام عليكم
هناك مشكلة ظهرت لي في الشدّة على نظامي (ios&mac)، حيث تظهر الشدّة أسفل الحرف وليس أعلاه.

• ios: تظهر المشكلة في متصفحي سفاري وكروم أيضاً
• macOS: تظهر المشكلة في متصفح سفاري فقط

'ss06' (“Tailed Sheen”) has no effect: IgnoreMarks is set but one of the input glyphs is a mark glyph.

When 'ss04' is enabled, initial kaf (and related letters) overlaps final or medial gaf (and related letters). Should it do that? For example, here is ⟨كک⟩ (U+0643 ARABIC LETTER KAF, U+06A9 ARABIC LETTER KEHEH):

Hi Pal,

The font design doesn't have very important three Arabic letters...

1. ى - (Ya) - Is same as { ي } BUT without dots at the bottom and this letter always come at the end of the word. - Example { أقصى }

2. ئ - Is same as { ى } BUT it has { Hamza } above - Example { سيئ }

3. ة - (Circled - Ta) Is same as { ه } BUT it has two dots above - Example { شجرة }

Thanks for your great font.

Noticed some connecting bugs the following is an example

Testing latest release (Jan 21)
testing on Adobe indesign cc 2017
testing the font on both weights
noticed many tashkeel marks positioning bugs as the following examples

Hello, trying to write LA (lam-alef) but not success, am using ver 0.8

Perhaps you could add Jawi letters to this font. It looks beautiful.

Many commits since last release :)

When 'jalt' is enabled, the marks above U+0626 ARABIC LETTER YEH WITH HAMZA ABOVE and U+06AC ARABIC LETTER KAF WITH DOT ABOVE are misplaced.

Since this font doesn’t implement 'numr' or 'dnom', digits adjacent to U+2044 FRACTION SLASH are full-sized, so uni2044 should not have negative side bearings. For example, here is ⟨3⁄5⟩:

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

.في برنامج وورد مافيش مشاكل ، إنما المشكلة بتظهر مع أي إصدار من برامج أدوبي زي الفوتوشوب مثلاً

Please include an OFL.txt with the https://github.com/khaledhosny/aref-ruqaa/blob/master/tools/build.py#L30-L32 output on 1 line, as line 1 :)

السلام عليكم

iOS انا استخدم هذا الخط في تطبيق على نظام
الخط يعمل بشكل جيد في جميع الانظمة السابقة الى ان تم اصدار النسخة التجريبية من الاصدار ١٣
لم يتبقى على اصدار النسخة النهائية من هذا النظام سوى اقل من ١٠ ايام ولا تزال المشكلة موجودة, بلغت ابل على وجود مشكلة في رسم الخطوط لكن لم يتم الرد حتى الان.

ايضا "macOS Catalina" لم اتاكد اذا كانت المشكلة في نظام الماك الجديد
لكن على الاغلب تكون موجودة نفس المشكلة

هذه صورة للخط يمكنكم ملاحضة التكسرات الحاصلة

اتمنى قراة ملف البي دي اف لانه فيه مشاكل واقتراحات للخط

مستند Microsoft Word جديد (5).pdf
`

The Greek range is missing many letters. The glyphs of U+03D5 GREEK PHI SYMBOL and U+03C6 GREEK SMALL LETTER PHI are swapped. The glyph epsilon1, presumably for U+03F5 GREEK LUNATE EPSILON SYMBOL, is not mapped to any code point. Since this is not a Greek font, it would be reasonable to just remove the Greek glyphs, because no support is better than sketchy support.

Hi Khaled,

analogue to Amiri, this is the last remaining issue (inverted outline direction):

>> com.google.fonts/check/transformed_components
    Ensure component transforms do not perform scaling or rotation.
    with /Users/yanone/Downloads/ArefRuqaa-1.005/ttf/ArefRuqaaInk-Regular.ttf

      Rationale:                                                                
                                                                                
      Some families have glyphs which have been constructed by using            
      transformed components e.g the 'u' being constructed from a flipped 'n'.  
                                                                                
      From a designers point of view, this sounds like a win (less work).       
      However, such approaches can lead to rasterization issues, such as having 
      the 'u' not sitting on the baseline at certain sizes after running the    
      font through ttfautohint.                                                 
                                                                                
      Other issues are outlines that end up reversed when only one dimension is 
      flipped while the other isn't.                                            
                                                                                
      As of July 2019, Marc Foley observed that ttfautohint assigns cvt values  
      to transformed glyphs as if they are not transformed and the result is    
      they render very badly, and that vttLib does not support flipped          
      components.                                                               
                                                                                
      When building the font with fontmake, the problem can be fixed by adding  
      this to the command line:                                                 
                                                                                
      --filter DecomposeTransformedComponentsFilter                             
                                                                                

     FAIL The following glyphs had components with scaling or                   
          rotation or inverted outline direction:                               
                                                                                
           • glyph00457 (component uni060C)                                     
           • glyph00459 (component uni061B)                                     
                                                                                
          [code: transformed-components]  

Hi,

Using this font: https://fonts.google.com/specimen/Aref+Ruqaa?subset=arabic

On iOS latest version has a certain issue in one of the forms of the letter ك
Check the codepen link on any iphone to see what I'm talking about: https://codepen.io/malkhuzayyim/pen/ExjBKwy?editors=1100

Thank you in advance for looking into this.

Sometimes Tashkeels overlaps with the letters. could you fix that?

هناك مشكلة في حرفين اللام والألف عندما يجتمعان معاً في برنامج الفوتوشوب
مثلاً جملة: لا تترك الصلاة
:هكذا تظهر في برامج أدوبي فوتوشوب بجميع إصداراته وإعداداته

في برنامج وورد مافيش مشاكل ، إنما المشكلة بتظهر مع أي إصدار من برامج أدوبي زي الفوتوشوب مثلاً.

Peace to you! Can you add this form for the letters ڬ, ڭ, ك as an alternative?

Thanks!

I'm curious why you're not using a 1,000 UPM?

cf https://github.com/khaledhosny/aref-ruqaa/blob/master/tools/build.py#L10

While typing الفتاح in Microsoft Word, The (أ) seems to get separated from (ت) after typing the (ح).

By the way the problem of Alef & Laam is not fixed by using contextual alternatives option in OpenType settings either in Photoshop or Illustrator