-
Notifications
You must be signed in to change notification settings - Fork 1
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
Improvements for Noto Sans Syloti Nagri #4
Comments
@Sagir8453 This is a comment about the upcoming changes to Noto Sans Syloti Nagri, showing examples of what's changed . The second part of this comment is about questions I've had where I'm unsure and require answers. I wish to note that showing individual graphemes for what needs addressing/changing makes it easier to assess what's being talked about rather than images involving a group of characters. Also, it would be helpful to have characters referred to by unicode values than naming convention like 'SHO' and 'BHO'. Conjuncts are easier to identify and locate by using uniXXXX_uniXXXX (eg. 'DU' would be written as 'uniA816_uniA825'). Thanks Changes yet to be uploaded
QUESTIONS
DU is tricky in that I'm prioritising avoiding clashes with adjacent characters, which limits the length of the DU's out-stroke. The image below shows character pairs which I believe are too close to each other (coloured light blue) when the tail stroke is made long. Please inform me if character sequences occur where uniA816_uniA825 is followed by characters with the VOWEL SIGN U (U+A825). If so, I'll do more extensive clashing tests. Clashes are marked pink with close clashes marked light blue.
|
@simoncozens A new commit has been pushed to improve Syloti Nagri. Please read the following to understand what's been altered:
Major changes
Image below shows the vowel sign on all bases and ligated forms:
The following is an image of possible clashes when the prior character supports the U (i.e BASE + U, followed by DU). Uncertain if this text chain ever occurs. Pink shows clashes, blue shows characters too close to one another. Further notes
The following ligatures remain unaltered (marked red in Glyphs source): |
@Sagir8453, the plan is to update the conjuncts and I'm requesting your help to do so. The current design of the conjuncts follows what was established in the Syloti base form—which have now been updated. If updating the conjuncts is a simple matter of rolling the new changes into the conjuncts then it's an easy task. However, if the conjuncts' designs drastically differ let me know as I'd love your help. |
Defect Report
Many characters in the Noto sans Syloti Nagri font are wrong or not in order.
Font
NotoSansSylotiNagri-Regular.ttf.
Where the font came from, and when
Font Version
The current one available on GitHub.
Issue
As shown in the image below, some characters need improvements. An alternative glyph for the character "A" is needed, the alternative form is more common and less confusing with the character "RO". The shape of the character "I" should be improved, the top part.
Now the consonants.
"TTHO" should be like "6" as in the image. The "DDHO" should also look different. The "DO" 's bottom part should be longer. The "DHO" should have an alternative form. The "NO"'s front part should be connected little bit billow from the top of the vertical line. The "BHO" should be improved, it looks too similar to the "NO" in the current font. The "LO" should have an alternative form. The "SHO" also needs improvements.
Now the diacritics.
The "E", "DVISVARA" and the top part of the vowel sign "OO" should be separated from the horizontal line. And the "U" diacitic should be separate from the letters and it should be longer also.
The "DU" (DO + U diacitic) should be like in the image.
Will talk about the conjunct consonants issue later when they are supported.
Screenshot
Syloti Nagri alphabet from manuscripts. The letter "ddo" is missing here.
A font that I'm making. It's currently in alpha state. Will try to post an improved version later.
Base of my font.
Another manuscript page.
The "DU"
The text was updated successfully, but these errors were encountered: