[Pkg-fonts-devel] How to deal with fontlint warnings? (Was: font checking tools?)

Paul Wise pabs at debian.org
Sun Nov 22 01:06:12 UTC 2015

On Sat, 2015-11-21 at 18:51 +0100, Gioele Barabucci wrote:

> Well, sometimes it makes sense. Suppose for a second that libfreetype is
> used for 100% of the font pipeline, from opening and reading the files
> to generating the bitmaps to be sent to the display. If you have
> integration tests (a la autopkgtest) in every font, then, when you want
> to update libfreetype, you can check whether this update breaks any font
> somehow: either the tables are not read properly or in your architecture
> the sub-pixel hinting is wrong. At that point you can chose to skip that
> update. You can do this only if you have tests integrated in the each
> font package.

FreeType is indeed most of the font pipeline on Debian these days. The
problem is that detecting the issues is basically impossible, the best
you can do is detect differences in the rendering, but of course there
could be legitimate changes. This is done by the Debian installer team
by the way.

> I understand that. But my counter question is: how you do intend to
> proceed with fonts that incorrectly have their embedding bits set?
> Asking the upstream to fix the files and re-release or changing directly
> the OTF/TTF files?

If upstream has text-based source files (like SFD, UFO, Glyphs etc)
then we can send them a patch for their source. For the rest I would
talk to upstream about the situation. For packages with no upstream,
I would probably ignore the problem until there is one.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-fonts-devel/attachments/20151122/9b225359/attachment.sig>

More information about the Pkg-fonts-devel mailing list