-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question] Possible to define a standard tadpole-like (or curly) comma/quotation mark for Noto Sans series? #411
Comments
I think you can ignore the Source Sans-derived shapes in Noto CJK, as that family is a fork of Source Han Sans |
Yeah I agree, and maybe not from N'Ko which came from Noto Naskh too. Personally I think the first from left in Noto Sans Arabic would be a good fit, or the fourth from left with slight modification.
…________________________________
发件人: Adolfo Jayme-Barrientos ***@***.***>
发送时间: 2023年4月1日星期六 19:38
收件人: notofonts/latin-greek-cyrillic ***@***.***>
抄送: NFSL2001 ***@***.***>; Author ***@***.***>
主题: Re: [notofonts/latin-greek-cyrillic] [Question] Possible to define a standard tadpole-like (or curly) comma/quotation mark for Noto Sans series? (Issue #411)
which of these would be the designer/Noto team's choice?
I think you can ignore the Source Sans-derived shapes in Noto CJK, as that family is a fork of Source Han Sans
―
Reply to this email directly, view it on GitHub<#411 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AH7LUSLZHWV3Q2K5QWWYWRTW7AHTVANCNFSM6AAAAAAWPQ7T2M>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
The 9 and 6 forms for U+02BB, U+02BC, U+0313, U+0315 or reversed for U+2BD, U+0313 are much better considering the scope of the Noto fonts. Some languages need to have a clear distinction between l̓ and ĺ or m̓ and ḿ or even ʼ and ´ / ’. |
@moyogo May I know which glyph you're referring to for the new Greek hard and soft spirits? The below is U+0486 and U+0343 left to right. I don't think both are suitable to replace the comma if needed. |
I don't think that "Naskh" is a good source fitting for borrowing glyphs into N'Ko. "Naskh" is designed with an oblique style for its diacritics (also slighly shifted to the left when above, or to the right when below), matching the way base letters are joining together (the Arabic Naskh diacritics strokes may also be slightly slanted about 30 degrees anti-clockwise compared to standard horizontal Arabic, independantly of the existence of an "italic" style applicable to both base letters and diacritics, plus some gylyph-to-glyph relative positioning for stacking glyphs may need to be rotated as they don't strictly align horizontally when side-by-side or vertically when on top of each other). And this does not apply to N'Ko which should then be based on standard Arabic glyphs, with its horizontal joining and alignment for letters and vertical alignment for stocking on top of each other. Other scripts to consider are: Coptic, Deseret, Cherokee, Lisu, modern Georgian (Mkhedruli/Mtavruli), plus Maths symbols and CJK fixed-width variants. They all have letters also derived or borrowed directly from Latin/Greek/Cyrillic shapes, with just minor adaptations of glyph metrics. |
Currently, the design of Noto Sans uses a wedge-like shape for commas, semicolons, and quotation marks as follow. Most other languages under Noto Sans also follows this choice.
However, there are quite a few languages supported by Noto that included (or replaced) commas, semicolons, and/or quotation marks with a tadpole-like (or curly) style instead of the wedge style in Noto Sans (LCG). Here are a list of scripts that uses the tadpole-like comma and the closest match to other fonts (if applicable).
Question: If Noto Sans is to support a tadpole-like comma shape, which of these would be the designer/Noto team's choice? Is it possible for the Noto team to decide on a sample glyph for the tadpole-like comma and apply it across all the aformentioned script fonts?
The text was updated successfully, but these errors were encountered: