Thanks for the additional clarifications. Unfortunately I'm still unable to reproduce, using the "Single Family TTF Package" / "Mono" downloads from GitHub. It's conceivable that the issue is specific to a particular version of the font, and the newest version has fixed it -- I do see that on the github page that you linked, the newest release has datestamp "last week" which is more recent than when you filed this bug. (Also, looking at the issues there, I see a recently-filed/fixed issue about the display of the font: https://github.com/be5invis/Sarasa-Gothic/issues/392 It mentions that [the brokenness is specific to the hinted version](https://github.com/be5invis/Sarasa-Gothic/issues/392#issuecomment-2106112924), which makes it feel likely related to this issue. Could you try updating to the latest release of the font and see if that fixes the issue for you?
Bug 1896276 Comment 15 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Thanks for the additional clarifications. Unfortunately I'm still unable to reproduce, using the "Single Family TTF Package" / "Mono" downloads from GitHub. It's conceivable that the issue is specific to a particular version of the font, and the newest version has fixed it -- I do see that on the github page that you linked, the newest release has datestamp "last week" which is more recent than when you filed this bug. Also, looking at the issues there, I see a recently-filed/fixed issue about the display of the font: https://github.com/be5invis/Sarasa-Gothic/issues/392 It mentions that [the brokenness is specific to the hinted version](https://github.com/be5invis/Sarasa-Gothic/issues/392#issuecomment-2106112924), which makes it feel likely related to this issue. Could you try updating to the latest release of the font and see if that fixes the issue for you?
Thanks for the additional clarifications. Unfortunately I'm still unable to reproduce, using the "Single Family TTF Package" / "Mono" downloads from GitHub. It's conceivable that the issue is specific to a particular version of the font, and the newest version (the version I'm testing) has fixed it -- I do see that on the github page that you linked, the newest release has datestamp "last week" which is more recent than when you filed this bug. Also, looking at the issues there, I see a recently-filed/fixed issue about the display of the font: https://github.com/be5invis/Sarasa-Gothic/issues/392 It mentions that [the brokenness is specific to the hinted version](https://github.com/be5invis/Sarasa-Gothic/issues/392#issuecomment-2106112924), which makes it feel likely related to this issue. Could you try updating to the latest release of the font and see if that fixes the issue for you?