[Pkg-fonts-devel] Bug#665334: proposed plan to resolve fontforge non-dfsg-freeness

Daniel Kahn Gillmor dkg at fifthhorseman.net
Wed Aug 29 20:05:12 UTC 2012

Just wanted to note that in this message:


i proposed a way that we might be able to resolve the non-dfsg-free
issue with fontforge (#665334):

The code in question appears to be collected and emitted during
generation of Type1 fonts, as part of fontforge's DefaultOtherSubrs()
function.  Fontforge also allows the user to replace this data with the
OtherSubrsFile configuration.

What if we did the following:

  0) ripped out the adobe code

  1) made DefaultOtherSubrs() raise some sort of error

  2) made the UI for type1 export default to requesting an
OtherSubrsFile, and had it look in a standard place in the filesystem

  3) posted the Adobe-owned data in an OtherSubrsFile-compatible format
somewhere *not* as part of the fontforge package (for debian,
potentially in a package in non-free that placed the file in the
standard place in the filesystem)

I haven't had time to work on this proposal, but if someone wants to
give it a shot, that would be great.

Unfortunately, i haven't seen any feedback on it specifically, so i
don't know if anyone else thinks it's feasible.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1030 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-fonts-devel/attachments/20120829/578b1d7f/attachment.pgp>

More information about the Pkg-fonts-devel mailing list