@embeddedt It seems the forum was quoted the wrong image. The second has large characters while in the original post the characters’ height are the same.
Anyway, it’s absolutely possible that the sizes has been changed.
In the old version if you set 18px height the converter adjusted the size internally to fit into a 18 px tall box.
However, in typography the meaning of font size it’s quite complex. If you set 18 px height it doesn’t include all ascents and descents. The new converter uses this more common but more complex approach. So now the fonts will have the same size as on PC in text editors but (usually) will be larger than the height you specify.
Regarding the quality, I think it’s an unlucky case. Could you try a 15px font? Probably the size won’t change much but hopefully, the extra pixel is enough to solve the quality issue.
In general, if we compare character by character, font converter v5.3 obtained much better results. For example, looking the underscore glyph ‘_’, it’s curious that it is not rendered as full color in most of the cases.
It seems that Freesans16 v6.0 is the one which looks better, although the size is bigger (not acceptable in my case). Besides, many characters add soft sourrunding pixels making glyphs widder.
I know it may be an special case for this configuration, but is there any possibility to use the old bitmaps with new approach?
We are planning to switch a component of the font converter back to the one that was used in 5.3 and prior versions. That will hopefully fix the majority of the issues that users are seeing with fonts in 6.0.