The problem is not a bug in the texttopdf filter and so not a bug to be fixed in the cups package. The bug is in the FreeMono font which is provided by the ttf-freefont package. See e-mail cited below (Hin-Tak was mentor of the Google Summer of Code student who wrote texttopdf, Steve is upstream developer of the FreeMono font).
Moving to ttf-freefont ...
----------
Date: Sat, 23 Jan 2010 15:20:58 -0800 (PST)
From: Hin-Tak Leung <hintak_leung at yahoo dot co dot uk>
Subject: Bug in FreeMono - it is not monospace (Re: texttopdf has problems under CUPS 1.4.x)
To: Steve White <stevan dot white at googlemail dot com>
Cc: Till Kamppeter <till dot kamppeter at gmail dot com>
Hi Steve,
It appears that a change you committed to FreeMono about 2 years ago:
Date: Sat, 12 Apr 2008 19:39:46 +0000
More fiddling with Greek accents
Made quotes "bent"
has resulted in FreeMono no longer being monospace - some character spacing becomes wider/narrower. See screenshot attached (before and after) - note in the before part, every glyph lines up vertically, which is no longer the case in the after. I don't quite get the details of your change, but that's what it appears to ftview, one of freetype's viewing tools.
This problem probably isn't noticeable in mixed-font usage, but only when using FreeMono as a monospace font to typeset text and make certain assumptions about per-character-width to fit per page.
Till (of Ubuntu) passed me one of the bugs from texttopdf which was a written as a Google Summer of Code project under my guidance a year and half ago - I narrowed it down to this particular cvs change and the fact that texttopdf needs on FreeMono when typesetting in utf-8 locale, and FreeMono has changed since the project completed. I believe at the moment, the bug happens because the code assumes one width for spacing and another for fitting with a page, although I haven't found out where that assumptions are yet.
I hope you have some idea about this anomaly, and can provide a fix soon.
The problem is not a bug in the texttopdf filter and so not a bug to be fixed in the cups package. The bug is in the FreeMono font which is provided by the ttf-freefont package. See e-mail cited below (Hin-Tak was mentor of the Google Summer of Code student who wrote texttopdf, Steve is upstream developer of the FreeMono font).
Moving to ttf-freefont ...
----------
Date: Sat, 23 Jan 2010 15:20:58 -0800 (PST)
From: Hin-Tak Leung <hintak_leung at yahoo dot co dot uk>
Subject: Bug in FreeMono - it is not monospace (Re: texttopdf has problems under CUPS 1.4.x)
To: Steve White <stevan dot white at googlemail dot com>
Cc: Till Kamppeter <till dot kamppeter at gmail dot com>
Hi Steve,
It appears that a change you committed to FreeMono about 2 years ago:
Date: Sat, 12 Apr 2008 19:39:46 +0000
More fiddling with Greek accents
Made quotes "bent"
has resulted in FreeMono no longer being monospace - some character spacing becomes wider/narrower. See screenshot attached (before and after) - note in the before part, every glyph lines up vertically, which is no longer the case in the after. I don't quite get the details of your change, but that's what it appears to ftview, one of freetype's viewing tools.
This problem probably isn't noticeable in mixed-font usage, but only when using FreeMono as a monospace font to typeset text and make certain assumptions about per-character-width to fit per page.
Till (of Ubuntu) passed me one of the bugs from texttopdf which was a written as a Google Summer of Code project under my guidance a year and half ago - I narrowed it down to this particular cvs change and the fact that texttopdf needs on FreeMono when typesetting in utf-8 locale, and FreeMono has changed since the project completed. I believe at the moment, the bug happens because the code assumes one width for spacing and another for fitting with a page, although I haven't found out where that assumptions are yet.
I hope you have some idea about this anomaly, and can provide a fix soon.
Cheers,
Hin-Tak