aminabedi68 / estedad Goto Github PK
View Code? Open in Web Editor NEWSans Serif Arabic-Latin text typeface
Home Page: https://aminabedi68.github.io/Estedad/
License: SIL Open Font License 1.1
Sans Serif Arabic-Latin text typeface
Home Page: https://aminabedi68.github.io/Estedad/
License: SIL Open Font License 1.1
سلام و عرض ادب و احترام خدمت جناب عابدی،
امکانش هست الف مقصوره را کمی کشیدهتر نمایید تا بهتر قابل تشخیص باشد؟
مثل فونت وزیرمتن، یک نسخه با نقطههای گرد برا این فونت بسازید
سلام وقت بخیر
لطفا مثل فونت میخک امکان تغییر شکل نقطه ها را به صورت وریبل اضافه کنید
باتشکر
سلام آقای عابدی،
من عاشق زیبایی و خوانایی قلم استعداد شما هستم، خودم هم یک مقدار برای دل خودم قلم درست کردهام که البته حرفهای نیستند.
میخواستم ببینم آیا امکانش هست برایتان که نسخهی رنگی این قلم زیبا را هم فراهم کنید تا حرکات فتحه و کسره و ضمّه و سکون و تشدید و تنوینها مثلاً آبی یا قرمز باشند؟ شاید اگر نقاط حروف هم رنگی شوند خوب باشد، مثل کاری که در نقاشیخطها انجام میدهند. اگر نه آیا به من اجازه میدهید این کار را بکنم؟
من برای این کار از برنامهی scfbuild استفاده میکنم.
سلام
ممنون بابت این فونت بسیار خوب
به نظرم فاصله خطوط زیاد است. به نظرم اگر فاصله خطوط حداقل مقدار ممکن باشد بهتر است چون در هر نوع استفاده از فونت میتوان به راحتی فاصله خطوط را افزایش داد و فاصلهی کم مشکلساز نیست ولی کاهش فاصله خطوط یا سخت است یا مشکلساز.
While there are both slashed and unslashed zero variants for the lining figures, the oldstyle figures only have a slashed zero. This makes it difficult to use oldstyle figures in text, since the slashed zero looks so technical. Do you have plans to add an unslashed oldstyle zero?
I really love the v5 Latin alphabet design, so this would be a great addition for me!
Hi, First, thanks for the awsome font and your work
I am maintaining a package on Arch Linux AUR for some of your fonts estedad-fonts and mikhak-fonts
Your recent release tags and changing font directories in releases without increasing or changing the version is making it hard for me (and possibly others) to keep doing this work, my question is: Not increasing the point number of the release and retagging with the same version again is for what? Any specific reason for that? to be more clear, why 5.0(2) and not 5.1?
It would be great to keep the zip URL consistent with the version
${url}/releases/download/${pkgver}/Estedad-V${pkgver}.zip"
With this (2) I should check manually for the release zip URL and add a (2) after $pkgver to generate the correct URL.
Again thanks for your great work again :)
This problem also exists on Mikhak font, but I will not open another issue there <3
uni06F6(Farsi six) to uni0666.tnum(Arabic tabular six) is wrong
سلام و عرض ادب و احترام،
از قلم استعداد شما خیلی استفاده میکنم و از بابت طراحی و نشر رایگان آن از شما خیلی متشکرم، ولی چون قلم لاتین آن به نظرم خیلی با فرم شاد قلم استعداد سازگار نبود، الآن بابت متون انگلیسی در داخل متن فارسی مجبور شدهام قلم Cavolini را با قلم استعداد همراه کنم و مثلاً در فایل CSS خودم بنویسم:
font-family: Cavolini, Estedad;
در این یکی دو روزه که متوجه شدم شما وبسایت دارید و با قلمهای دیگرتان هم آشنا شدم، دیدم که گلیفهایی که برای انگلیسی قلم میخک ساختهاید با قلم استعداد خیلی خوب جفت میشود. حالا میخواستم ببینم آیا امکان دارد که:
۱. این گلیفهای لاتین جایگزین گلیفهای فعلی لاتین برای قلم استعداد هم بشود
۲. اگر نمیشود، آیا میشود گلیفهای فارسی و لاتین دو قلم استعداد و میخک به صورت جداگانه هم عرضه شوند تا هر کسی بتواند گلیفهای فارسی و لاتین آن دو را به سلیقهی خودش در کنار هم به کار ببرد؟
با تشکر
As mentioned, here is the complete bug report from Google Fonts’ tooling about Estedad.
You may ignore the first two items about file name and glyph coverage, although they are only four missing characters, so I will not be angry if you added them ;)
If you have any questions about any of the items, please do let me know.
Thank you.
Fontbakery version: 0.8.7.dev11+g266bdf1a
--- Rationale --- A font's filename must be composed in the following manner: <familyname>-<stylename>.ttf - Nunito-Regular.ttf, - Oswald-BoldItalic.ttf Variable fonts must list the axis tags in alphabetical order in square brackets and separated by commas: - Roboto[wdth,wght].ttf - Familyname-Italic[wght].ttf
--- Rationale --- Google Fonts expects that fonts in its collection support at least the minimal set of characters defined in the `GF-latin-core` glyph-set.
🔥 FAIL Missing required codepoints:
0x2039 (SINGLE LEFT-POINTING ANGLE QUOTATION MARK)
0x203A (SINGLE RIGHT-POINTING ANGLE QUOTATION MARK)
0x2044 (FRACTION SLASH)
And 0x2215 (DIVISION SLASH)
[code: missing-codepoints]
--- Rationale --- Traditionally version 0 'gasp' tables were set so that font sizes below 8 ppem had no grid fitting but did have antialiasing. From 9-16 ppem, just grid fitting. And fonts above 17ppem had both antialiasing and grid fitting toggled on. The use of accelerated graphics cards and higher resolution screens make this approach obsolete. Microsoft's DirectWrite pushed this even further with much improved rendering built into the OS and apps. In this scenario it makes sense to simply toggle all 4 flags ON for all font sizes.
🔥 FAIL Name Table entry: Copyright notices should match a pattern similar to: "Copyright 2019 The Familyname Project Authors (git url)"
But instead we have got:
"Copyright (c) 2020 by Amin Abedi (@aminabedi68)-www.fontamin.com,
with Reserved Font Name Estedad.
This Font Software is licensed under the SIL Open Font License, Version 1.1." [code: bad-notice-format]
--- Rationale --- There have been bugs rendering variable fonts with nested components. Additionally, some static fonts with nested components have been reported to have rendering and printing issues. For more info, see: * https://github.com/googlefonts/fontbakery/issues/2961 * https://github.com/arrowtype/recursive/issues/412
Use -F or --full-lists to disable shortening of long lists. [code: found-nested-components]
--- Rationale --- This setup is meant to ensure consistent rendering quality for fonts across all devices (with different rendering/hinting capabilities). Below is the snippet of instructions we expect to see in the fonts: B8 01 FF PUSHW 0x01FF 85 SCANCTRL (unconditinally turn on dropout control mode) B0 04 PUSHB 0x04 8D SCANTYPE (enable smart dropout control) "Smart dropout control" means activating rules 1, 2 and 5: Rule 1: If a pixel's center falls within the glyph outline, that pixel is turned on. Rule 2: If a contour falls exactly on a pixel's center, that pixel is turned on. Rule 5: If a scan line between two adjacent pixel centers (either vertical or horizontal) is intersected by both an on-Transition contour and an off-Transition contour and neither of the pixels was already turned on by rules 1 and 2, turn on the pixel which is closer to the midpoint between the on-Transition contour and off-Transition contour. This is "Smart" dropout control. For more detailed info (such as other rules not enabled in this snippet), please refer to the TrueType Instruction Set documentation.
gftools fix-nonhinting
script. [code: lacks-smart-dropout]--- Rationale --- There are some entries on the name table that may include more than one line of text. The Google Fonts team, though, prefers to keep the name table entries short and simple without line breaks. For instance, some designers like to include the full text of a font license in the "copyright notice" entry, but for the GFonts collection this entry should only mention year, author and other basic info in a manner enforced by com.google.fonts/check/font_copyright
--- Rationale --- Some designers adopt the "Reserved Font Name" clause of the OFL license. This means that the original author reserves the rights to the family name and other people can only distribute modified versions using a different family name. Google Fonts published updates to the fonts in the collection in order to fix issues and/or implement further improvements to the fonts. It is important to keep the family name so that users of the webfonts can benefit from the updates. Since it would forbid such usage scenario, all families in the GFonts collection are required to not adopt the RFN clause. This check ensures "Reserved Font Name" is not mentioned in the name table.
This Font Software is licensed under the SIL Open Font License, Version 1.1.") contains "Reserved Font Name". This is an error except in a few specific rare cases. [code: rfn]
--- Rationale --- Check that particle names and values on STAT table match the fallback names in each axis entry at the Google Fonts Axis Registry, available at https://github.com/google/fonts/tree/main/axisregistry
--- Rationale --- Most variable fonts should include an avar table to correctly define axes progression rates. For example, a weight axis from 0% to 100% doesn't map directly to 100 to 1000, because a 10% progression from 0% may be too much to define the 200, while 90% may be too little to define the 900. If the progression rates of axes is linear, this check can be ignored. Fontmake will also skip adding an avar table if the progression rates are linear. However, we still recommend designers visually proof each instance is at the desired weight, width etc.
--- Rationale --- All fonts on the Google Fonts collection should have OS/2.fsSelection bit 7 (USE_TYPO_METRICS) set. This requirement is part of the vertical metrics scheme established as a Google Fonts policy aiming at a common ground supported by all major font rendering environments. For more details, read: https://github.com/googlefonts/gf-docs/blob/main/VerticalMetrics/README.md Below is the portion of that document that is most relevant to this check: Use_Typo_Metrics must be enabled. This will force MS Applications to use the OS/2 Typo values instead of the Win values. By doing this, we can freely set the Win values to avoid clipping and control the line height with the typo values. It has the added benefit of future line height compatibility. When a new script is added, we simply change the Win values to the new yMin and yMax, without needing to worry if the line height have changed.
--- Rationale --- A font's winAscent and winDescent values should be greater than the head table's yMax, abs(yMin) values. If they are less than these values, clipping can occur on Windows platforms (https://github.com/RedHatBrand/Overpass/issues/33). If the font includes tall/deep writing systems such as Arabic or Devanagari, the winAscent and winDescent can be greater than the yMax and abs(yMin) to accommodate vowel marks. When the win Metrics are significantly greater than the upm, the linespacing can appear too loose. To counteract this, enabling the OS/2 fsSelection bit 7 (Use_Typo_Metrics), will force Windows to use the OS/2 typo values instead. This means the font developer can control the linespacing with the typo values, whilst avoiding clipping by setting the win values to values greater than the yMax and abs(yMin).
--- 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. 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:
exclamdown (component exclam)
hookabovecomb (component ogonek)
questiondown (component question)
uni018E (component E)
uni01DD (component e)
uni020A (component breve)
uni020B (component breve)
uni020E (component breve)
uni020F (component breve)
uni0212 (component breve)
uni0213 (component breve)
uni0216 (component breve)
uni0217 (component breve)
uni0238 (component uniE00F)
uni0245 (component V)
uni0250 (component a)
uni029E (component k)
uni063D (component uniE037)
uni063D.fina (component uniE037)
uni063D.init (component uniE037)
uni063D.init.Extended_1 (component uniE037)
uni063D.init.Extended_2 (component uniE037)
uni063D.medi (component uniE037)
uni063D.medi.Extended_1 (component uniE037)
uni063D.medi.Extended_2 (component uniE037)
uni0657 (component uniE032)
uni065B (component uniE037)
uni065E (component Arabic_Single_Dot)
uni065E (component Arabic_Single_Dot)
uni066A (component uni0660)
uni066A (component uni0660)
uni06BD (component uniE019)
uni06BD.fina (component uniE019)
uni06C9 (component uniE037)
uni06EE (component uniE037)
uni06EE.fina (component uniE037)
uni06EF (component uniE037)
uni06EF.fina (component uniE037)
uni06FF (component uniE037)
uni06FF.fina (component uniE037)
uni06FF.init (component uniE037)
uni06FF.medi (component uniE037)
uni0755 (component uniE037)
uni0755.fina (component uniE037)
uni0755.init (component uniE037)
uni0755.init.Extended_1 (component uniE037)
uni0755.init.Extended_3 (component uniE037)
uni0755.medi (component uniE037)
uni0755.medi.Extended_1 (component uniE037)
uni0755.medi.Extended_3 (component uniE037)
uni0758 (component uniE019)
uni0758.fina (component uniE019)
uni075A (component uniE037)
uni075A.fina (component uniE037)
uni077E (component uniE037)
uni077E.fina (component uniE037)
uni077E.init (component uniE037)
uni077E.medi (component uniE037)
uni08B2 (component uniE037)
uni08B2.fina (component uniE037)
uni1D6B (component uniE00D)
uniFBE2 (component uniE037)
uniFBE3 (component uniE037)
[code: transformed-components]
--- Rationale --- The dotted circle character (U+25CC) is inserted by shaping engines before mark glyphs which do not have an associated base, especially in the context of broken syllabic clusters. For fonts containing combining marks, it is recommended that the dotted circle character be included so that these isolated marks can be displayed properly; for fonts supporting complex scripts, this should be considered mandatory. Additionally, when a dotted circle glyph is present, it should be able to display all marks correctly, meaning that it should contain anchors for all attaching marks.
Use -F or --full-lists to disable shortening of long lists. [code: unattached-dotted-circle-marks]
🔥 FAIL Space and non-breaking space have differing width: The space glyph named space is 400 font units wide, non-breaking space named (uni00A0) is 900 font units wide, and both should be positive and the same. GlyphsApp has "Sidebearing arithmetic" (https://glyphsapp.com/tutorials/spacing) which allows you to set the non-breaking space width to always equal the space width. [code: different-widths]
💔 ERROR | 🔥 FAIL | ⚠ WARN | 💤 SKIP | ℹ INFO | 🍞 PASS | 🔎 DEBUG |
---|---|---|---|---|---|---|
0 | 15 | 6 | 106 | 8 | 88 | 0 |
0% | 7% | 3% | 48% | 4% | 39% | 0% |
Note: The following loglevels were omitted in this report:
درود و تشکر بابت فونت استعداد که به نظرم زیباترین و خواناترین فونت فارسی برای UI هست.
به دلیل خوانایی بهتر این فونت، من اونو روی بع عنوان فونت دیفالت مرورگز و سیستمعامل گذاشتم. ولی فاصلهی زیاد بالای حروف و پایین حروف باعث میشه وقتی کنار برای فونت رو به فونت سیستم عامل ست میکنیم (در ubuntu یا Android) خود به خود فاصله خطوط تقریبا دو برابر میشوند.
این مشکل در توسعه وبسایت هم وجود داره ولی اونجا با تنظیم مقدار line-height میشه تا حدی برطرفش کرد. ولی وقتی برای فونت یک نرمافزار یا کل سیستمعامل قرار میدیم کنترلی روی لاینهایت نداریم.
میدونم فونتهای فارسی به خاطر حروفش همه این مشکل (ویژگی؟) رو دارن ولی در فونتهای دیگر کمتر هست. در تصویر زیر با جندتا فونت دیگه مقایسه شده.
البته کوچکتر بودن حروف فونت استعداد نسبت به سایر فونت کمی این مسئله رو بیشتر میکنه.
چند نمونه مقایسه از جاهایی که این موضع به چشم میاد:
باز هم ممنون از زحمات شما
Hello,
I've been commissioned with onboarding Estedad and Mikhak to Google Fonts, so the following question applies to both typefaces.
I’m wondering how to proceed with this practically: Whether to make the changes necessary to meet our specifications and PR them back to you, or whether to fork the repository on continue from there.
As far as I can tell as the moment, the changes include:
Copyright 2015 The Estedad Project Authors (https://github.com/aminabedi68/Estedad)
STAT
and avar
tablesOS/2.fsSelection
bit 7 needs to be set (Use Typo metrics)I haven't looked at Mikhak yet, but I'm expecting a similar set of changes.
Please let me know whether you are comfortable with the proposed changes to your repo or not.
Thank you.
لطفا امکان تغییر اعداد انگلیسی به فارسی توسط font-feature-settings اضافه کنید، در نسخه وب بسیار کاربردی میباشد
can you put the instructions on how to build the font on unix like operating systems? thanks.
امین جان اگر اجازه بدید قصد دارم جهت بهتر شدن و هماهنگی بیشتر حروفها در تایپ فیس تون نکاتی رو خدمتتون مطرح کنم؟
یا میتونید تو تلگرام هم انجامش بدیدم تا سریع تر میشه. من خیلی از یکسری فرمها خوشم اومد حیف است که در تغییرات اونها از دست بره :)
شما هم مثل فونت وزیرمتن یک درگاه پرداخت برای حمایت مالی درست کنید که بتونیم در حد توانمون برای رشد و ارتقا این پروژه کمکی کرده باشیم
سلام. ممنون بابت انتشار این فونت زیباتون یه سوال داشتم از اونجایی که آشنایی با فونت و اینها ندارم منظور از
HelveticaLT-Light Glyphs
چی هستش؟
طبق این توئیت:
https://twitter.com/aminabedi68/status/1278807849670451200
ادوبی با اعراب گزاری روی ترکیب جایگزین شدۀ چندتایی عربی مشکل داره، باید از روش جایگزینی تکی استفاده بشه.
با تشکر از سعید کاوندی
ممنونم فونت بسیار خوبی هست.
فقط یک مشکلی که وجود داره این هست که برای اعداد فارسی و انگیسی فونت های جدا وجود داشته باشه خیلی بهتر میشه.
مثلا یک فونت FaNum باشه و یکی فقط با اعداد انگیسی.
مثل فونت دانا و ایران سنس که این فیچر رو دارند.
الان برای وب باید برای هر عددی که میخوام فارسی نمایش بدم یه فانکشن بفنویسم و نمایش اون رو به کاراکتر های فرسی تغییر بدم. اگه فونت این رو ساپورت کنه همه این ها حل میشه :)
سلام و تشکر بابت این فونت عالی که طراحی کردید.
لطفا نسخه بدون لاتین این فونت را نیز قرار دهید.
و به نظرم برخی حروف بعد از حرف «ر» نیاز به کمی فشردگی بیشتر دارند و در کاراکتر «لا» اگر الف پایینتر باشد زیباتر است و اگر نسخهای با نقطههای گرد هم قرار دهید فونت زیباتر میشود.
نمیدانم چرا یک دمو براش نساختی امین جان، اما بد نیست براش بسازی :)
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.