Skip to content
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

Noto Sans Balinese what is latest version? 2.003 or 2.004 #37

Closed
Veerjee opened this issue Feb 2, 2024 · 9 comments
Closed

Noto Sans Balinese what is latest version? 2.003 or 2.004 #37

Veerjee opened this issue Feb 2, 2024 · 9 comments

Comments

@Veerjee
Copy link

Veerjee commented Feb 2, 2024

Defect Report

NotoSansBalinese-Regular.ttf

Noto fonts can be obtained from https://notofonts.github.io/
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".

Font

NotoSansBalinese-Regular.ttf

Where the font came from, and when

The version 2.003 is downloaded from the
https://fonts.google.com/noto/specimen/Noto+Sans+Balinese
However, repo gives me https://notofonts.github.io/ version 2.004

OS name and version

Windows 11

Application name and version

Word

Issue

The version of the font downloaded from the site is 2.003
The version of the font dowloaded from the repo is 2.004.

The shaping results are different using Word on Windows 11.
Windows 11: Word: Noto Sans Balinese 2.004
image

Windows 11: Word: Noto Sans Balinese 2.003
image

Copy paste following text in Word.
"ᬩ᭄ᬬᬶᬳ" "ᬩᬵᬳ"

Character data

"ᬩ᭄ᬬᬶᬳ" "ᬩᬵᬳ"

I think the issue is with the merger script.
When I merge the v2.003 with another font. I get overlapping results as shown in the image above.

If additional information is needed please do let me know here.

@simoncozens
Copy link
Contributor

2.004 is the latest version; we don't always onboard to Google Fonts immediately, it can take some time. I will check that these sequences work in 2.004

@Veerjee
Copy link
Author

Veerjee commented Feb 2, 2024

simoncozens thank you for the fast reply.

@simoncozens
Copy link
Contributor

The sequences work correctly in 2.004; you talked about a merger script, so the problem might be with that script. I don't think there's an issue with the font.

@miloush
Copy link

miloush commented Feb 5, 2024

While I agree this is most likely an issue with the merge script, note that this affects your releases as well. The 2.004 version from notofonts.github.io repo exhibits the issue. The 2.003 version from fonts.google.com seems to be immune to whatever the script does to it.

@simoncozens
Copy link
Contributor

OK, I see the problem. This is broken in the 2.004 release but it is fixed in the latest development builds. We need a new release, which I'll try and do soon.

@Veerjee
Copy link
Author

Veerjee commented Feb 5, 2024

This version latest development builds.

  • still has the hinting data for the font listed under unhinted. (Reported problem not fixed)
  • Version number in the name table is not increased, it should be bumped up if the problem is fixed.

@simoncozens
Copy link
Contributor

Version numbers are bumped on release. I'll look into the hinting issue.

@Veerjee
Copy link
Author

Veerjee commented Feb 5, 2024

Confirm this version
latest development builds.
is working as expected.

@simoncozens
Copy link
Contributor

OK, found it. The source file for Noto Sans Balinese contained a "ttfautohint options" custom parameter, so fontmake thought it should autohint everything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants