Hi, thanks, well i want to use TTF over Bitmaps because of the large choice of fonts, and simplicity to use everywhere.
The .fontdef are correctly parsed(the manual is still using .fontdef), i' m using Ogre 1.6 atm, i can change to .
font, np.
btw there is no char_width parameter...

---
I start to believe it is a bug when Ogre is generating the texture/UVs, however if someone could confirm me he got the same problem with the brooklyn
font i linked previously, that would be great!
(that
font is working just fine in the Gimp or Blender)
---
This is definitly a bug when Ogre is generating the texture, strange that nobody spotted this before...
here are the glyphs within the generated texture(+an overlay ABCDEF...):

---
Ok, i got it somehow fixed for now...

If someone has this problem while waiting for a better solution, in OgreFont.cpp, loadResource() there is a variable named char_spacer which is set to 5 for some reason, you can play with this value so that characters aren't eating each others in the generated texture, then you need to modify u2/v2 in the setGlyphTexCoords call later. However this is not the good way to fix this...