Forum Bugs

ConcertOne font rendered with wrong top offset

ledestin
Hi,

I've noticed that Chrome render and Prince render are different for the attached document. Prince renders text using Concert One font lower than Chrome.

Thanks.
  1. concert_one_bug.html4.0 kB
    Source HTML
mikeday
Sorry for the delay, I'm having difficulty reproducing this issue with Prince 10 and comparing with Firefox and Chrome output. Can you attach a screenshot or PDF of the output you are getting?
ledestin
Chrome - https://monosnap.com/file/54WGgE99J62jIV3IbxH4nVFspeAf9Q
PDF - https://monosnap.com/file/7sFylUQLiDHxLXzo5O0ARi8xQGeBoy

I can confirm that when I change font from Concert One to Roboto, Prince produces output same as Chrome.
mikeday
The font appears to have inconsistent font metrics: the ascender height is reported as 2005 units in one table but 1638 units in a different table. It appears that Prince and web browsers on Linux use the first value while web browsers on Windows use the second value.

It is a bit awkward to fix this as it is technically a bug in the font.

Edit: oops, maybe Prince uses the second value and Windows uses the first value. Same problem, though.

Edited by mikeday

mikeday
My mistake: the values are consistent, but the font descender value is positive, when it is supposed to be negative, and different systems may handle this situation in a different way. We will investigate further.
mikeday
We can emulate the Windows behaviour by negating the font descender if it is positive, we may do this in a future release of Prince.
ledestin
Thanks mikeday
mikeday
We have made this change in the Prince latest builds, thanks for letting us know about the issue.