[Pkg-fonts-bugs] Bug#662924: [Pkg-fonts-devel] Bug#662924: Bug#662924: ttf-freefont: What is Untitled1.ttf?
stevan.white at googlemail.com
Fri Mar 9 14:18:01 UTC 2012
Hi again Fabian,
On Fri, Mar 9, 2012 at 11:21 AM, Fabian Greffrath <fabian at greffrath.com> wrote:
> Am 09.03.2012 11:07, schrieb Steve White:
>> I'm not sure what you're talking about here.
> CUPS has switched to PDF-based printing. That means, roughly, if you want to
> print a raw text file, e.g. 'lp ~/.bashrc', it needs to get converted into a
> PDF file in one step of the process. A font is needed to render your text in
> the PDF file and this font is embedded into the PDF. Currently the filter
> that does this does not support CFF fonts.
> It will fail here:
Yes, but OpenType can contain either CFF or TrueType style glyphs.
>> What are you referring to with "embed OpenType fonts"? I did a
>> search, and found nothing about this.
> This README file might provide some explanation:
>> For example, one solution for the CUPs problem is for CUPSs to
>> maintain their own copy of FreeMono,
>> (in whatever form they prefer), but separate from the system fonts.
> This problem is already solved upstream (since yesterday). ;)
> cups-filters now merely needs one monospaced TrueType font installed on the
> system that it can use as a fallback for FreeMono or Courier or whatever. No
> need to carry around own copies of fonts.
My understanding, CUPS *requires* the presence of such a font, and
fails badly without it.
This is why the dependency existed in the first place.
However, system fonts ought to be the choice of the admin (or superuser).
This is why I proposed that it be bundled with a font it would always work with
(and that this font *not* be installed on the system).
However, if CUP can do the right thing (fail gracefully, informing the
user of the nature of
the problem and how to solve it), then I will agree with you.
Thanks for the explanations!
More information about the Pkg-fonts-bugs