Closed sven-oly closed 2 years ago
@sven-oly : Thank you for the reminder.
2016 June 21: Unicode® 9.0.0 was published. It had the first specification of Adlam --- : until the next date there was a design phase where Barry brothers were consulted 2016 August 24: Design phase is completed --- : until the next date there was a script implementation phase based on the design from 2016 August 24 was started from that date 2017 January 10: Noto Sans Adlam sources are published and font was built --- : Since that time, Barry brothers changed the following:
IMHO, the first Unicode standard (9.0) for Adlam was published prematurely. We will commission an update to Noto Sans Adlam when the new Unicode 13.0 standard is published (it's a Noto policy to publish only scripts after Unicode standard is officially PUBLISHED). I expect Unicode 13.0 to be published in the first half of 2020. Please expect a new Noto adhering to it soon thereafter.
Noto Sans Adlam 3.0 now follows the proposed forms. For example:
$ shape NotoSansAdlam-Regular.ttf -u 1e912,1e912,1e912
[u1E912.fina=2+833|u1E912.medi=1+833|u1E912.init=0+585]
Defect Report
Use this template for filing a defect report. For feature requests and other matters, you can use part of the template and delete what you don't need.
Title
Noto Sans Adlam needs refresh
Font
NotoSansAdlam*.ttf.
Where the font came from, and when
Font Version
OS name and version
All
Application name and version
Issue
The representative font for Adlam script in the Unicode standard will be updated soon. Noto Sans Adlam's style should be updated to be more in line with the original intent of the script, which is much better represented by the new font Ebrima/Kigelia (coming in Windows 10), which will soon be part of the Unicode Standard's page.
Here is the current Unicode page for Adlam: http://www.unicode.org/charts/PDF/U1E900.pdf
Character data
Screenshot
Tools for reporting bugs
Useful tools for reporting bugs are available at: https://github.com/googlei18n/
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.
For example:
Fontview
Fontdiff