[Pkg-fonts-devel] Bug#665334: Bug#694308: non-DFSG postscript embedded in fontforge

Bastien ROUCARIES roucaries.bastien at gmail.com
Mon Dec 28 12:55:48 UTC 2015


On Mon, Dec 28, 2015 at 7:18 AM, Hideki Yamane <henrich at debian.or.jp> wrote:
> Hi,
>
>>The originals of several of these functions seem to appear (with
>>non-DFSG-free licensing) in the appendices of
>>http://partners.adobe.com/public/developer/en/font/5015.Type1_Supp.pdf
>>
>>In particular, the licensing says:
>>
>>>>> This code, as well as the code in the following appendices, is copyrighted by
>>>>> Adobe Systems Incorporated, and may not be reproduced except by
>>>>> permission of Adobe Systems Incorporated. Adobe Systems Incorporated
>>>>> grants permission to use this code in Type 1 font programs, as long as the
>>>>> code is used as it appears in this document, the copyright notice remains
>>>>> intact, and the character outline code included in such a font program is
>>>>> neither copied nor derived from character outline code in any Adobe Systems
>>>>> font program.
>
>
>>> https://github.com/fontforge/fontforge/blob/master/fontforge/othersubrs.c
>
> This code seems to be based on
> https://github.com/adobe-type-tools/afdko/tree/master/FDK/Tools/Programs/public/lib/source/t1write/t1write_flexothers.*
> and now Adobe Font Development Kit for OpenType (AFDKO) is licensed under
> Apache-2.0 license. Fontforge is licensed under GPL-3, so it's not a
> problem to embedded it.
>
> Thanks, Read and other folks in Adobe :)
> Bug#665334 "non-DFSG postscript embedded in fontforge" is solved.
>
>
>
> However, I don't know it is okay for other pfb files with license conflicts.
> Apache-2.0 conflicts with GPL-2, at least, and it may conflict with
> other license,
> too.
>
> Just "type 1 fonts include Adobe all right reserved code" is not a problem, but
> if those type 1 fonts would be licensed under certain license like GPL-2 that
> conflict with Apache-2.0...?

If it is GPL-2+ it is not a problem but a few fonts file are released
under GPL-2 only... It is quite a mess.

> And, how can I think about fontforge copies snippet to generate those
> *.pfb files?

Could you modify comment on this code to add some fontforge comment ?
Like for instance "inserted by  fontforge (debian someversion)". I
could teach lintian to check if font are regenerated.
What do you think?

Bastien
>
> It's for Bug#694308.
>



More information about the Pkg-fonts-devel mailing list