View Single Post
Old 02-11-2009, 06:08 PM   #63
murraypaul
Interested Bystander
murraypaul ought to be getting tired of karma fortunes by now.murraypaul ought to be getting tired of karma fortunes by now.murraypaul ought to be getting tired of karma fortunes by now.murraypaul ought to be getting tired of karma fortunes by now.murraypaul ought to be getting tired of karma fortunes by now.murraypaul ought to be getting tired of karma fortunes by now.murraypaul ought to be getting tired of karma fortunes by now.murraypaul ought to be getting tired of karma fortunes by now.murraypaul ought to be getting tired of karma fortunes by now.murraypaul ought to be getting tired of karma fortunes by now.murraypaul ought to be getting tired of karma fortunes by now.
 
Posts: 3,725
Karma: 19728152
Join Date: Jun 2008
Device: Note 4, Kobo One
I've tracked down a bit more on this.
When is happening is that the Tm command triggers a font update. Part of this update checks that the substituted font is roughly the same width as the intended font, and scales it if not. For the paragraphs in question the getGlyphAdvance call is returning a value greater than 1 (which shouldn't be possible), causing the font to be dramatically over-shrunk.
This can be worked around by changing SplashOutputDev.cc, line 1177, to add a check for w2 <= 1.
murraypaul is offline   Reply With Quote