Wrong baseline?

[htdag]

Just compare fontbm vs BMFont vs Hiero, chars: A Á Â Ấ Ắ Ễ Ỗ
From image, I found some issues

• Glyph rendered, not good as Hiero (freetype).
• The baseline seem wrong
  BMFont: size=-48, lineHeight=56 base=44
  fontbm: size=48, lineHeight=57 base=36

[vladimirgamalyan]

Fixed and released, thank you and sorry for the late reply =)
(baseline is still different from BMFont version, the last one slightly crops some glyphs, for example Consolas Ỗ as you can see on your screenshot)

[htdag]

Thanks, but it still not correct (char g).

[vladimirgamalyan]

I guess you use common/lineHeight parameter for your canvas height, so bottom of 'g' doesn't fit into the picture. Actually lineHeight means how far the cursor should be moved vertically when moving to the next line (see http://www.angelcode.com/products/bmfont/doc/render_text.html). To calculate required canvas height you can get the maximum value out of all yoffset + height.

[vladimirgamalyan]

I added the --extra-info flag, it adds a common/totalHeight value that you can use as total canvas height to fit any glyphs from the font.

[htdag]

I use lineHeight
But, it displays correctly for bmfont.

[vladimirgamalyan]

BMFont uses TEXTMETRIC.tmAscent as common/base value (without TEXTMETRIC.tmInternalLeading) and crops top of glyphs above this value:

As result of this cropping - you could fit your text in lineHeight.

fontbm uses distance from topmost possible pixel (for all font glyphs) to baseline as common/base, so it is not the same value as BMFont, and rendered text looks below a bit (to fit all accent marks and other diacritical characters), but in this case lineHeight is not enough to fit all the glyphs and should be used only as distance between baselines.

[vladimirgamalyan]

The last release generates more similar base values, maybe this will suit your case.