[Bug]: Monolisa 2.013 Character Spacing not shown correctly on Terminal App

[Pyre909]

Edition

Plus

What version are you using?

2.013

What type of weights are you using?

Default (non-customized)

Operating system

Windows 10 Pro 22H2

Program

Putty(Terminal)

Display resolution

3840x2160

What happened?

Installed font and used in Terminal(Putty) and the character spacing is abnormally long in the terminal. Screenshots attached from how the font displays text on the Editor and the Terminal where the issue is seen.

[Pyre909]

This is happening for every font variation as well.

[bebraw]

I have trouble reproducing this under MacOS so I imagine it might be a Windows specific issue to debug.

Can you see the issue in other terminals under Windows?

[Pyre909]

Looks like this might be specific to Putty. Font displays normal rendering using Command Prompt or Windows Terminal. I should note that this didn't happen on 2.012

[bebraw]

I wonder what changed in between. Maybe it's some difference in font metadata or so.

[bebraw]

When you have time, can you check if the latest prerelease has the issue? When downloading, make sure to choose prerelease channel.

[Pyre909]

Hi , Same issue on the pre-release version when used in putty.

[bebraw]

Thanks for testing! Maybe we still missed something (cc @MarcusSterz).

[mekkablue]

There’s a bug in Glyphs 3.2 where OS/2.xAvgCharWidth is always exported as 0, but should be 640. Fixed in the upcoming version (both app and font).

[bebraw]

@Pyre909 There's a new version with the fix to test now.

[Pyre909]

@bebraw just tested the pre-release version issue still persists.

[bebraw]

@Pyre909 Thanks for testing!

@mekkablue Could something be off in the current prerelease version? Note that the issue is visible only within Terminal(Putty) under Windows.

[MarcusSterz]

As @mekkablue wrote it's a current bug in Glyphs. Once that's fixed we can ship a version that works in Putty. Until then please use v2.012.

[bebraw]

@Pyre909 We applied the Glyphs side fix. When you have a good moment, please give the prerelease a go.

[Pyre909]

@bebraw The fix worked. Thanks!

[bebraw]

Fixed in 2.014.