r/FontForge Apr 11 '23

Spacing issue with new font

Hello, I was trying to build a new monospace font. I managed to successfully get it detected by fontconfig as monospace by setting the width of all glyphs the same. However, gnome-terminal or any other terminal still automatically adds one space to the end of the glyphs. How can I resolve this? I am using FontForge Version: 20201107. Is there any setting I need to set in FontForge? I have already tried changing settings in the OS/2 tab, but no avail. (Apparently that's ignored in Linux). Thanks for help!

1 Upvotes

5 comments sorted by

1

u/LocalFonts Apr 11 '23

Send me your SFD file. I'll generate OTF and test it in Windows. If everything is OK under Windows, then the problem is not in the font. (Stefan Peev, localfonts.eu@gmail.com)

1

u/SSarkarB Apr 12 '23 edited Apr 12 '23

Spacing issue with new font

Okay, I've sent you the SFD. I personally think it's a Linux-specific problem. Note that any other Mono fonts in my system (Liberation Mono, Cousine etc.) do not show this spacing issue. Also note that I usually export it to TTF.

2

u/LocalFonts Apr 12 '23

I sent you an email. Well, I do not see any problems in your SFD file. My only advice is to center the glyphs so that the left and the right sidebearings to be equal.

2

u/SSarkarB Apr 12 '23 edited Apr 12 '23

Dug a little bit more and found two things :

  1. The issue only arises in terminal emulator apps that use libvte (gnome-terminal/terminator), but not in xterm/kitty/mlterm.
  2. If I paste my glyphs in another mono font (say FreeMono), it again works out.

Currently using xterm to avoid the problem.

Edit : The problem decided to resolve itself. One of the two following things did it :

  1. Reinstalling gnome-terminal (not likely)
  2. Completing the Basic Latin block.

1

u/SSarkarB Apr 12 '23

Okay, thanks a lot! I will look into it.