MacOS Validation Report (1 Issue) #14

New Issue

adam · 2025-12-30T01:29:07+01:00

adam commented

2025-12-30 01:29:07 +01:00

Originally created by @NaoPross on GitHub (Nov 13, 2025).

Originally assigned to: @sayyadirfanali on GitHub.

I downloaded the latest file from the main branch

$ sha1sum ./Myna.otf
f8b1a86e32912453d7503d62fe55ab203e9ed312  ./Myna.otf

Not sure what it means but on MacOS I get this warning. It does not prevent me from installing the font or using it.

Originally created by @NaoPross on GitHub (Nov 13, 2025). Originally assigned to: @sayyadirfanali on GitHub. I downloaded the latest file from the main branch ``` $ sha1sum ./Myna.otf f8b1a86e32912453d7503d62fe55ab203e9ed312 ./Myna.otf ``` Not sure what it means but on MacOS I get this warning. It does not prevent me from installing the font or using it. <img width="612" height="609" alt="Image" src="https://github.com/user-attachments/assets/9f2a9fad-59d3-4daa-a6ce-2b809c5589a7" />

adam added the bug documentation labels 2025-12-30 01:29:07 +01:00

adam closed this issue

2025-12-30 01:29:08 +01:00

adam commented

2025-12-30 01:29:09 +01:00

@sayyadirfanali commented on GitHub (Nov 14, 2025):

@NaoPross thanks for reporting this.

i’ve corrected the name table entries which should resolve this issue.

there may still be minor validation warnings on macOS, as FontForge fonts sometimes fail strict metadata checks but these should not affect the font’s functionality.

please check if it works now.

feel free to drop suggestions for better distribution on MacOS. i'm afraid i'm not at all familiar with the MacOS ecosystem. i'm working to add this to homebrew-cask as suggested in #11. maybe that should make it easier to install?

@sayyadirfanali commented on GitHub (Nov 14, 2025): @NaoPross thanks for reporting this. i’ve corrected the name table entries which should resolve this issue. there may still be minor validation warnings on macOS, as FontForge fonts sometimes fail strict metadata checks but these should not affect the font’s functionality. please check if it works now. feel free to drop suggestions for better distribution on MacOS. i'm afraid i'm not at all familiar with the MacOS ecosystem. i'm working to add this to `homebrew-cask` as suggested in #11. maybe that should make it easier to install?

adam commented

2025-12-30 01:29:09 +01:00

@NaoPross commented on GitHub (Nov 14, 2025):

Yep, that fixed it! With regards to homebrew, I don't really know how the packaging process works. I could test it a some point if necessary, though I did not find the current releases difficult to install.

@NaoPross commented on GitHub (Nov 14, 2025): Yep, that fixed it! With regards to homebrew, I don't really know how the packaging process works. I could test it a some point if necessary, though I did not find the current releases difficult to install.

adam commented

2025-12-30 01:29:09 +01:00

@jubilatious1 commented on GitHub (Dec 7, 2025):

I hit the same issue, trying the simplest install method (downloading then double-clicking on the otf file opens FontBook which reports the same name validation error).

Is it possible to push another release? Thx.

@jubilatious1 commented on GitHub (Dec 7, 2025): I hit the same issue, trying the simplest install method (downloading then double-clicking on the `otf` file opens FontBook which reports the same `name` validation error). Is it possible to push another release? Thx.

adam commented

2025-12-30 01:29:10 +01:00

@sayyadirfanali commented on GitHub (Dec 9, 2025):

@jubilatious1 there are several fonts inside the fonts/ folder. is the validation error shown for all the files or some particular one.

@sayyadirfanali commented on GitHub (Dec 9, 2025): @jubilatious1 there are several fonts inside the `fonts/` folder. is the validation error shown for all the files or some particular one.

adam commented

2025-12-30 01:29:10 +01:00

@jubilatious1 commented on GitHub (Dec 10, 2025):

Hello, I get the exact same image displayed as @NaoPross .

So my guess is that it's only the "Regular" font that's having a problem?

FYI, When I download your 1.0 Release I get a single .otf file object, not a folder.

The size is 190,228 bytes.

Thanks!

@jubilatious1 commented on GitHub (Dec 10, 2025): Hello, I get the exact same image displayed as @NaoPross . So my guess is that it's only the "Regular" font that's having a problem? FYI, When I download your 1.0 Release I get a single .otf file object, not a folder. The size is 190,228 bytes. Thanks!

adam commented

2025-12-30 01:29:10 +01:00

@sayyadirfanali commented on GitHub (Dec 10, 2025):

@jubilatious1 i've not updated the release after fixing this in fa3d37b491.

can you please install from the latest version in main branch directly and check with one of the files?

@sayyadirfanali commented on GitHub (Dec 10, 2025): @jubilatious1 i've not updated the release after fixing this in https://github.com/sayyadirfanali/Myna/commit/fa3d37b491967e39d9ea28aef7883d6b5040331e. can you please install from the latest version in main branch directly and check with one of the files?

adam referenced this issue

2025-12-30 01:29:13 +01:00

Please add a True Type Font of Myna in releases #18

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/Myna#14