Hi there!
I created my own monospaced ttf. All works perfectly in the Win2000 environment, but when I use it under QNX(RTOS) the behaviour is strange.
The “space” glyph is a bit higher then all other glyphs but it should to be the same. The width is ok! Are there any settings which affect the height(resp. ascender/descender) of a glyph but isn’t used by Win2000? And if, why are all other glyphs but the “space” rendered ok?
additional information:
when I draw for instance a little rectangle in the “space” glyph this point is shown by test tool but not in qnx. is it possible that qnx creates its own space and if how can I avoid that?
thx a lot!
Marcus
I don’t know what QNX(RTOS) is, but I do know fonts!! (A little anyway).
I’m confused by what you say
The “space” glyph is a bit higher then all other glyphs but it should to be the same.
Since in Windows all glyphs share height and depth characteristics (Win Ascent/Win Descent), but not width, one of them shouldn’t stick out above all others. Since it works in Win2000, you have built it correctly apparently.
Certain applications deal with fonts in a “non-traditional way”, perhaps QNX(RTOS) is one.
If your question is QNX(RTOS), this is the wrong forum?
Good luck,
Dick Pape
Hi Dick Pape!
Let me try to make it more clear.
For instance there is a glyph in my font with the metrics of 1000 in height. It is just a simple filled “black” rectangle. The ascent and descent are 750 resp. -250. The glyph is sticked to these values thus it is positioned correctly.
Let’s suppose this glyph is presented by a ‘X’, then following should give a black frame with a white space in the middle of it.
XXX
X X
XXX
But unfortunately between the first and the second line is a small white line. This is just the case in QNX(RTOS Real Time Operating System) and when I take the space-glyph as middle point.
Hope it’s now a bit clearer!
Marcus
This is most definitely an issue of QNX. It treats the space character in a non-standard way, perhaps by using the space key as an indication of leading (that’s the horizontal space between lines, originally a sheet of lead between rows of type). The only way there could be any confusion is if your font somehow has vertical metrics, and unless you started with an oriental font, I can’t think of a way that would happen.
primel OK now here’s the deal … I read that as two problems 1. the white space between two lines and 2. the different sized space. I hope that’s right so far.
- I believe you eliminate the white space (line) between lines of text by making the difference between the (win ascent + win descent) to be the same as the glyph boundaries. That is, to have the character fill up the alloted space which is the same as having the alloted space the same size as the character.
If you were to make those special glyphs the maximum size as the win descent - win ascent there is no room between lines. I’ve tried it in a couple of fonts successfully (in Windows).
- Perhaps you could design a character which has no curves (displays as blank) but has the same glyph metrics as the “X” character. Map it to anything but a Space. Use it in lieu of the space you enter on the second line.
This seems like it might work, but it is limited if you also use Y and Z characters which are different sizes. By not calling it a “space” maybe that fakes out your application.
Good luck.
Dick