Skip to content

Ligature issues. #19

Open
Open

Description

@abdelhaqueidali

IMG_20240206_120329

Defect Report

Noto fonts can be obtained from https://www.google.com/url?sa=t&source=web&rct=j&opi=89978449&url=https://fonts.google.com/noto/specimen/Noto%2BSans%2BTifinagh&ved=2ahUKEwjhx8_av96EAxXUhf0HHQLIA5kQFnoECBoQAQ&usg=AOvVaw2zS6-BLGqq9Rfa-rLX9wRM
If you find a problem with a released font, then please use this template to file a defect report.
Before filing your report, please check if the issue has been fixed in the latest development build. You can get development builds by finding the font family on https://notofonts.github.io/ and following the link to "Development builds".

Title

Should be brief but contain essential information.

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

For example:
Site: https://noto-website-2.storage.googleapis.com/pkgs/NotoSansArmenian-hinted.zip
Date: 2017-04-10 (preferred format)

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

This is especially important if the font came pre-installed.

Application name and version

If the issue is observed using a specific app.

Issue

Summarize the issue briefly -- one paragraph preferred

  1. Steps to reproduce
  2. Observed results
  3. Expected results
  4. Additional information

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

Character data

Please include real character data to illustrate your issue-- Unicode codepoints are helpful. This makes it possible for developers who don't know the language or script to copy/paste the text to reproduce the issue.

Screenshot

If possible, include a screenshot or an image illustrating the issue.
Annotations are also helpful.

Tools for reporting bugs

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.

Activity

  1. abdelhaqueidali commented on Mar 24, 2024

    @abdelhaqueidali
    Author

    For the previous ligature, it seems that right to left one is used instead of keeping it as it is for left to right. So it is mirrored in the new font while it is taken into consideration writing Left to right which is used for tifinagh now. Also some ligatures have some issues like ⵎ + ⴱ = ⵎ⵿ⴱ (looks exactly like ⴱ)
    ⵔ+ⴱ = ⵔ⵿ⴱ (the letter ⵔ contains letter ⵀ inside instead of ⴱ) as you may know neo-tifinagh has used letter ⵀ for Yah instead of Yab. So letter Yab is ⴱ, therefore the ligature should use ⴱ regardless of old tifinagh usage of letter ⵀ in this ligature, because that letter ⵀ is no longer the letter yab, it is yah. that ligature should be used for ⵔ+ⵀ and for ⵔ+ⴱ the shape of letter ⴱ should be the one inside ⵔ
    For ⵔ+ⴷ = ⵔ⵿ⴷ (letter ⴹ inside ⵔ) this legature should be resulted from ⵔ+ⴹ. And for the ⵔ+ⴷ it should give the letter ⴷ inside ⵔ this if there is a ligature for it.

  2. changed the title [-]Hello, I found an issue with a ligature, it is mentioned in the file attached[/-] [+]Ligature issues.[/+] on May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions