You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The affected glyphs have codepoints in the range U+F137 to U+F69C.
The phenomenon occurs in the Terminal application in Mac OS (observed in macOS Big Sur 11.6.4, with both Hanazono Mincho Ex A1 and A2).
The glyphs corresponding to those non-Unicode characters are displayed significantly off-center, running over and overlapping with the next character (or a Latin letter) to their right. I can provide screenshots.
I used both fonts in order to properly display IDS decompositions of characters.
Under Windows 10 the same glyphs in Notepad are placed correctly.
I would love to test this behavior in Cygwin mintty terminal and also in GVIM, Unfortunately, the two fonts are not monospaced. Can we expect a release of your excellent fonts in monospaced versions too? That would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
The affected glyphs have codepoints in the range U+F137 to U+F69C.
The phenomenon occurs in the Terminal application in Mac OS (observed in macOS Big Sur 11.6.4, with both Hanazono Mincho Ex A1 and A2).
The glyphs corresponding to those non-Unicode characters are displayed significantly off-center, running over and overlapping with the next character (or a Latin letter) to their right. I can provide screenshots.
I used both fonts in order to properly display IDS decompositions of characters.
Under Windows 10 the same glyphs in Notepad are placed correctly.
I would love to test this behavior in Cygwin mintty terminal and also in GVIM, Unfortunately, the two fonts are not monospaced. Can we expect a release of your excellent fonts in monospaced versions too? That would be greatly appreciated.
The text was updated successfully, but these errors were encountered: