[Pkg-fonts-devel] license violations with embedded binary copies of GNU FreeFont?

[Nicolas Spalinger]

On 10/06/11 05:07, Paul Wise wrote:
> On Fri, Jun 10, 2011 at 4:40 AM, Nicolas Spalinger wrote:
> 
>> From the names of the subsets, even if there are variations and the
>> added suffixes ?
> 
> How do you even get the font names?

AFAICT pdffonts reads it from the PDF file structure directly.

>>> On that topic, I wonder if we need a lintian complaint for fonts in
>>> main that have restrictive bits enabled; no embedding/modifying etc.
>>
>> Yeah, great idea!  That would be really helpful.
> 
> This would need to be in perl and using the perl font libs, so not
> something I know how to do. Perhaps you could think up exactly what we
> need to look for and write the long description for the warnings?
> 
>> Along with a little python script using fonttools or fontforge to output
>> the fsType as an extra item in the report for each font in the review to
>> help with what already in the archive?
> 
> Does fontaine output embedding information? Maybe we could just
> package and backport that. Or can we modify one of our existing
> scripts?

It seems fontaine doesn't do this, so until we dive into the lintian
check I suggest we simply plug the little fontembedding python fontforge
script into our review:

I committed the script in my people/ folder (it's on
http://utilities.open-fonts.org/ as well) and the small mods on our
review scripts.

Could you please test/improve/deploy?

Thanks,



-- 
Nicolas Spalinger,
SIL NRSI volunteer - http://scripts.sil.org
Debian fonts task force -  http://pkg-fonts.alioth.debian.org
Open font community - http://planet.open-fonts.org