Kerning Pairs (monospace image font) can affect the kerning of subsequent characters, off by one pixel about godot HOT 9 CLOSED

If I hit those 3 bins and reimport, your issue is fixed for me (Linux, v4.3.beta1 or github tip).

from godot.

I thought you also needed the *.fnt file for kerning the bitmap files? No?

You can manually specify kernings and custom glyph offsets/advanced in the image import settings, importer should be renamed it was monospace when it was first added, but this is no longer the case. The source image is expected to be uniform character grid (you can't specify arbitrary rect for the character), but the font itself is not monospaced.

from godot.

The issue seems to be how HarfBuzz apply kerning, half is applied to the previous glyph advance, half to the next glyph offset. This works with normal fonts, but with 1px kerning it will result in 0.5 pixel offsets and rounding errors.

from godot.

@bruvzg thanks for working on such quick fixes for this feature! As someone relatively new to Godot, I really appreciate it!

from godot.

@capnm That deletes the kerning pairs, thus removing character specific kerning entirely. This bug report is about the usage of the kerning pairs feature itself.

from godot.

@capnm That deletes the kerning pairs, thus removing character specific kerning entirely. This bug report is about the usage of the kerning pairs feature itself.

Kerning pairs for monospace fonts? This is IMO a bug – you shouldn't use kerning here at all.

from godot.

Kerning pairs for monospace fonts? This is IMO a bug – you shouldn't use kerning here at all.

The datatype will probably be renamed to bitmap image fonts or such since this feature allows them to no longer be exclusively monospace.

from godot.

I thought you also needed the *.fnt file for kerning the bitmap files? No?

from godot.

I guess that's then the implemented spec...

bmfont -> Block type 5: kerning pairs

https://calligro.ideasalmanac.com/

from godot.