There are a number of different issues here, some are easier to address than others.<br><br><br><div class="gmail_quote">On Fri, Mar 23, 2012 at 11:55 AM, Daniel Kahn Gillmor <span dir="ltr"><<a href="mailto:dkg@fifthhorseman.net">dkg@fifthhorseman.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Package: fontforge<br>
Severity: serious<br>
<br>
On 03/03/2012 07:48 AM, Nicholas Bamber wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
We have a package libimager-perl where we have had to remove a few<br>
adobe-related test files as being non-DFSG. See<br>
<a href="http://cpansearch.perl.org/src/TONYC/Imager-0.88/adobe.txt" target="_blank">http://cpansearch.perl.org/<u></u>src/TONYC/Imager-0.88/adobe.<u></u>txt</a> .<br>
<br>
However given a comment in the latest version's changelog:<br>
<br>
" - note that the generator of the apparently non-DFSG-free postscript<br>
in MMOne.pfb is a Debian package."<br>
<br>
by which he means fontforge. I intend to email to the author and assure<br>
him that this is a purely precautionary measure on our part and that the<br>
functionality of the package is not inhibited.<br>
<br>
However since fontforge has been roped into the issue I wonder what you<br>
guys think.<br>
</blockquote>
<br>
Hi Nicholas--<br>
<br>
Thank you for raising this issue. I just did a bit of research to try to figure out what this is about.<br>
<br>
In fontforge, it appears that this code is embedded in fontforge/othersubrs.c<br>
<br>
The originals of several of these functions seem to appear (with non-DFSG-free licensing) in the appendices of<br>
<a href="http://partners.adobe.com/public/developer/en/font/5015.Type1_Supp.pdf" target="_blank">http://partners.adobe.com/<u></u>public/developer/en/font/5015.<u></u>Type1_Supp.pdf</a><br>
<br>
In particular, the licensing says:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This code, as well as the code in the following appendices, is copyrighted by<br>
Adobe Systems Incorporated, and may not be reproduced except by<br>
permission of Adobe Systems Incorporated. Adobe Systems Incorporated<br>
grants permission to use this code in Type 1 font programs, as long as the<br>
code is used as it appears in this document, the copyright notice remains<br>
intact, and the character outline code included in such a font program is<br>
neither copied nor derived from character outline code in any Adobe Systems<br>
font program.<br>
</blockquote></blockquote></blockquote>
<br>
This license looks pretty non-DFSG-free to me, and it applies at least to the makeblendedfont array in fontforge/othersubrs.c.<br>
<br>
Even more depressing, the makeblendedfont array in othersubrs.c actually has a modified comment (correcting a mistakenly copy/pasted buggy comment from the code in the PDF!) which potentially means that it is itself in violation of Adobe's restrictive license.<br>
<br></blockquote><div><br>This is not such big issue in that it is just a matter of getting Adobe to produce a corrected version - could you state exactly what change needs to be made.<br><br><br> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I'm not really sure what to do about this other than to open an RC bug against fontforge, which this e-mail should do :(<br>
<br>
We could probably make a new dfsg-free "clean" upstream tarball that is still capable of building fontforge binaries by ripping out big chunks of this file (i haven't tried it yet), but i don't know what that would do to fontforge's ability to do Type1 font generation.<br>
<br></blockquote><div><br>I someone could try this its worth see what the resulting difference is.<br> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Another approach would be to move fontforge from the main archive to the non-free archive; but it seems like that would relegate many of our font packages to contrib, due to build-dependencies. :(<br>
<br></blockquote><div><br>In the past I have seen US and NUS versions of fontforge. The solution would therefore seem to produce a dfsg free version of fontforge which stays in main, albeit with somewhat reduced. <br><br>
<br><br>John<br><br></div><div> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I'm open to other suggestions; i would be overjoyed, in fact, to hear other suggestions. Does anyone have any proposals?<br>
<br>
--dkg<br>
<br>
______________________________<u></u>_________________<br>
Pkg-fonts-devel mailing list<br>
<a href="mailto:Pkg-fonts-devel@lists.alioth.debian.org" target="_blank">Pkg-fonts-devel@lists.alioth.<u></u>debian.org</a><br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-fonts-devel" target="_blank">http://lists.alioth.debian.<u></u>org/cgi-bin/mailman/listinfo/<u></u>pkg-fonts-devel</a><br>
</blockquote></div><br>