[Pkg-fonts-devel] fsType!=0 license violations with embedded binary copies

Paul Sladen pkg-fonts at paul.sladen.org
Thu Jul 21 18:54:20 UTC 2011

On Thu, 21 Jul 2011, Nicolas Spalinger wrote:
> > Can you explain more about the embedding bits and what each one means?
> a better script could be written, maybe something using fonttools?

During the bootstrapping and beta process for the Ubuntu Font Family;
we kept getting alpha drops of the .ttfs with the fstype bits != 0; eg:

  "Technical: Metadata: set OS/2.fsType=0 (Installable Embedding)"

There is now a fairly-simple fonttools script at the start of the
package build process that errors out if the bits are set, or the
Licence is incorrect:


There's also an equally simple script with a 'do_remove_drm()' here:

  http://bazaar.launchpad.net/~sladen/ubuntu-font-family/midstream/view/head:/midstream/patch-truetype.py --remove-drm

which could be passed on to upstream.  These scripts are GPLv3, anyone
and everyone is welcome to adapt or use them if it's useful!


(Kudos goes to Nicholas telling me about this in the first place
last year).

More information about the Pkg-fonts-devel mailing list