[Pkg-fonts-devel] license violations with embedded binary copies of GNU FreeFont?
pabs at debian.org
Fri Jun 10 03:07:22 UTC 2011
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?
>> 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
> Yes, hopefully that can be the next step when the script is good enough
> (it still balks on various pdfs). Although I'm not sure how best
> to do that at this stage and I'll probably ask for your help there.
Generate a simple source package to URL mapping in YAML and ask the
PTS devs to add links on the side. You can probably reuse the patch
for the fonts link.
More information about the Pkg-fonts-devel