This package include copyrighted font hinting from adobe.
t1disasm /usr/share/fonts/X11/Type1/lmr10.pfb | grep -i -A 10 adobe
%!PS-AdobeFont-1.0: LMRoman10-Regular 2.004
%%CreationDate: 7th October 2009
% Generated by MetaType1 (a MetaPost-based engine)
% Copyright 2003--2009 by B. Jackowski and J.M. Nowacki (on behalf of TeX USERS GROUPS).
% Supported by CSTUG, DANTE eV, GUST, GUTenberg, NTG, and TUG.
% METATYPE1/Type 1 version by B. Jackowski & J. M. Nowacki
% from GUST (http://www.gust.org.pl).
% This work is released under the GUST Font License.
% For the most recent version of this license see
% This work has the LPPL maintenance status `maintained'.
% The Current Maintainer of this work is Bogus\l{}aw Jackowski and Janusz M. Nowacki.
--
% Copyright (c) 1987-1990 Adobe Systems Incorporated
% All Rights Reserved.
% This code to be used for hint replacement only
/OtherSubrs
[ { } { } { }
{
systemdict /internaldict known not
{ pop 3 }
{ 1183615869 systemdict /internaldict get exec
dup /startlock known
{ /startlock get exec }
Thanks
bastien ROUCARIES <roucaries.bastien@gmail.com> writes: just wait until fontforge is fixed? Hm, I'm wondering: Although lmodern's readme says ,---- | The package consists of the files in the directories conforming | to the TeX Directory Structure (v. 1.1), splitted into three archives: | | lm2.003-bas.zip -- basic set; the directories contain: | [...] | lm2.003mt1.zip -- Latin Modern source font files for the METATYPE1 package `---- The Debian orig.tar.gz doesn't seem to contain the source archive's contents. I'm not familiar with font generation, but it seems to me that, in order to be able to generate corrected Type1 files with a fixed fontforge version, we would need the contents of lm2.003.mt1.zip, e.g.: $ ls fonts/source/public/lm/lmr10* fonts/source/public/lm/lmr10.mp fonts/source/public/lm/lmr10.mph fonts/source/public/lm/lmr10.mpm fonts/source/public/lm/lmr10.mpg fonts/source/public/lm/lmr10.mpl $ cat fonts/source/public/lm/lmr10.mp %%%% This file belongs to the Latin Modern package. The work is released %%%% under the GUST Font License. See the MANIFEST-Latin-Modern.txt and %%%% README-Latin-Modern.txt files for the details. For the most recent version of %%%% this license see http://www.gust.org.pl/fonts/licenses/GUST-FONT-LICENSE.txt %%%% or http://tug.org/fonts/licenses/GUST-FONT-LICENSE.txt % LATIN MODERN font: a driver file for lmr10 input fontbase; vardef cm_pal = "cmr10" enddef; input comm_mac; % common defs, CM params input comm_mph; % common header input lmr10.mpm; % metric data input lmr10.mph; % PS-oriented header beginfont input lmr10.mpg; % ``frozen'' glyphs input comm_mpg; % common glyphs (mainly diacritics) if known generating: % optimize proofing time input lmr10.mpl; % ligatures and kerns fi endfont %%%% EOF $ Does that mean we have one more RC bug, namely that the sources are incomplete? debian/copyright says: The following TeX Live packages were downloaded from http://www.ctan.org/tex-archive/systems/texlive/tlnet/archive/ and merged into one orig.tar.gz file: lm.tar.xz lm.doc.tar.xz lm-math.tar.xz lm-math.doc.tar.xz These are files prepared by TeXLive, not the original lmodern authors. In this directory, there is an additional lm.source.tar.xz file. It seems to me we should include its contents, too, shouldn't we? Does the same apply to TeX-Gyre? Regards, Frank
Hi Bastien,
so that was the outcome of the discussion on d-d ... you went ahead
with useless mass bug filing. Well done.
Instead of digging around you *MIGHT* look for *WHERE* this comes from
to help everyone.
Frank, for now please don't do anything. We will see how this
develops. This was a mass bug filing (probably to make release
cycles more enjoyable) and there is no agreement how to deal with
it, at least what I saw on d-d mailing list.
It is alread lm2.004 ...
It is not a question of fontforge... THe lines mentioned come from
pfcommon.dat
which was inherited from metatype1.
I will contact the GUST people about that.
the fonts went through manual hinting and fixing.
Best wishes
Norbert
------------------------------------------------------------------------
Norbert Preining preining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live & Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
POGES (pl.n.)
The lumps of dry powder that remain after cooking a packet soup.
--- Douglas Adams, The Meaning of Liff
Hi Bastien, hi Norbert, Norbert Preining <preining@logic.at> writes: If this is right, then it is wrong to block the bug by the fontforge bug, isn't it? Bastien, I'm not sure enough about this to remove the blocking myself, please do it. How ist that done? I thought it was done with fontforge scripts - I understand this is not the case? Did they really open the font files in interactive fontforge, adjust and safe? Regards, Frank
Hi Frank,
Wait ... I am not sure either. Maybe fontfoge *also* contains and
adds this code ... I just found the text in the sources of lmodern.
to the lenth of recreating the fonts at build time from any kind of
scripts.
Best wishes
Norbert
------------------------------------------------------------------------
Norbert Preining preining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live & Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
HUTTOFT (n.)
The fibrous algae which grows in the dark, moist environment of
trouser turn-ups.
--- Douglas Adams, The Meaning of Liff
However, it is already possible now to use different code for OtherSubrs. That's what I have done in my FPL fonts. See URW-OtherSubrs.ps and the ReadOtherSubrsFile statement in the pe-files in <URL:http://dante.ctan.org/tex-archive/fonts/fpl/source/>. I expect that the code will not work out of the box with current fontforge versions, but the principles should still apply. Hence the fontforge bug for containing the OtherSubrs code from Adobe does in no way block the corresponding bug in various font packages, even if they were edited with fontforge. The feature to define OtherSubrs was introduced in 2005 (cf <URL: http://comments.gmane.org/gmane.comp.fonts.fontforge.devel/861>). cheerio ralf
Could you relicence the URW-OtherSubrs.ps under a bsd license or even public domain ? It will help us to . Moreover you entry are exactly the same of the last one of adobe code (Appendix 3: OtherSubrs Programs p95) Last but not least according to fonty book: How do you cope with this by rewritting the program
On Thu, Nov 29, 2012 at 6:06 PM, Bastien ROUCARIES <roucaries.bastien@gmail.com> wrote: I cannot do that, since the code has been taken from one of the original URW++ fonts and is therefore covered by their copyright and released under GPL. Meanwhile the original URW++ fonts have been also released under LPPL. I am not sure if this would allow one to relicense the OtherSubrs code under a different license. Actually, I am not sure if it is even possible to wirte working hint replacement code that is not equivalent to the one published by Adobe. cheerio ralf
Hi Karen,
At the Cambridge BSP (Jan 27/28 2017) we have been looking at the
following bugs pertaining to non-DFSG compliance with fonts embedded
with non-free code:
* http://bugs.debian.org/665334
opened 23 Mar 2012, last update 01 Aug 2016 modulo spam
* http://bugs.debian.org/694320
opened 25 Nov 2012, last update 30 Aug 2014
blocked by #665334
* http://bugs.debian.org/694323
opened 25 Nov 2012, last update 30 Aug 2014
blocked by #665334
Synopsis:
Type 1 fonts that are made using the package FontForge include font
hinting code which is marked "copyright Adobe all rights reserved".
This issue logically extends to every package that contains fonts that
have been made using FontForge.
Current State
Reading #665334 it appears that FontForge historically contained
fragments of code with Adobe asserted rights. We believe that this is
now resolved with "autohint code is now all open source". The github
repo is top licensed Apache 2.0 [1]
It is our belief that this is sufficient; that the package FontForge,
and type 1 fonts generated by this package are now DFSG compliant
because Apache 2.0 is GPL2+ compatible.
* Is our understanding of the above correct? i.e. Does the github
repository top-licensing (to Apache) of the Adobe 'hinting' properly apply?
* Are the font hinting fragments, that are Adobe copyright, embedded
into fonts produced in FontForge, the same code as in the above
repository (we *think* that this is the case)?
* Thus, are these fonts (generated by the above) now covered by Apache 2.0?
* And, consequently: are the fonts in the Debian archive, produced by
FontForge, now to be considered under Apache 2.0; and is this sufficient
to cover the embedded fragments under Apache 2.0?
Assuming the above is all correct then, in order to resolve this issue,
we believe that all packages that contain fonts that are generated using
FontForge should contain an appropriate licence text for the font. A
Mass bug filing could then be made against these packages requesting the
appropriate update to the licence file.
However we see this a potential minefield, and therefore seek
clarification and advice before we continue.
/Andy
PP Debian BSP Cambridge Jan 2017 [2]
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665334#168
[2] https://wiki.debian.org/BSP/2017/01/gb/Cambridge
The FSF believes that Apache 2.0 is only compatible with GPLv3+ not GPLv2. https://www.gnu.org/licenses/license-list.html#apache2 https://www.apache.org/licenses/GPL-compatibility.html
Well Paul you are entirely correct. Would you believe that pretty much everyone here missed that one - despite the fact that nearly every person did proof this :-) OK so what does that mean? GPL2 stuff could be problematic but ultimately the suggested action(s) would still appear valid... Karen your thoughts on this would be greatly appreciated.... /Andy
Perhaps unsurprisingly, I agree with the FSF. But it is also technically correct to say that it's compatible with GPLv2+, because you can take GPLv2+ works under GPLv3. There have been fascinating discussions about this somewhat recently, as LLVM had an exception drafted to Apache 2.0 by Heather Meeker to deal with the incompatibility. I'd be happy to discuss more in a nonpublic venue and get more information about the situation. Unfortunately, I'm headed out to Campus Party Brasil today, and headed straight to Brussels for FOSDEM from there, and won't free up until after February 7. karen
As pointed out Adobe has relicensed the PS code under Apache License v2. Please document the license in the package's copyright file to address this bug.
On 11/25/2012 3:04 PM, bastien ROUCARIES wrote: Hello, In the latest pfb files, that (C) statement is missing. Do we have to update c/copyright? hille@rasppi3:~/devel/TeXLive/github/lmodern/fonts/type1/public/lm $ for i in *.pfb; do strings $i|strings|grep -i adobe ; done %!PS-AdobeFont-1.0: LMRomanDemi10-Regular 2.004 %!PS-AdobeFont-1.0: LMRomanDemi10-Oblique 2.004 %!PS-AdobeFont-1.0: LMMathSymbols10-Bold 1.200 %!PS-AdobeFont-1.0: LMMathSymbols5-Bold 1.200 %!PS-AdobeFont-1.0: LMMathSymbols7-Bold 1.200 %!PS-AdobeFont-1.0: LMRoman10-Bold 2.004 %!PS-AdobeFont-1.0: LMRoman12-Bold 2.004 %!PS-AdobeFont-1.0: LMRoman5-Bold 2.004 %!PS-AdobeFont-1.0: LMRoman6-Bold 2.004 <snip>
Please use t1disasm to find the string. The Copyright string is not included in plaintext that would be printed by the strings program. The latest upstream version still contains the Adobe code.
On 10/27/2025 5:20 PM, Bastian Germann wrote: Hello, Correct. Sorry for missing this. Hilmar
We believe that the bug you reported is fixed in the latest version of
lmodern, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 694323@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Hilmar Preuße <hille42@debian.org> (supplier of updated lmodern package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Sat, 20 Jun 2026 11:10:10 +0200
Source: lmodern
Architecture: source
Version: 2.005-2
Distribution: unstable
Urgency: medium
Maintainer: Debian TeX Task Force <debian-tex-maint@lists.debian.org>
Changed-By: Hilmar Preuße <hille42@debian.org>
Closes: 694323
Changes:
lmodern (2.005-2) unstable; urgency=medium
.
* Add a statement, that the Postscript code of the fonts is on
Apache 2.0 license (Closes: #694323).
* We are back on salsa.
* dh'rize the d/rules file.
* Move "tex-common" from "Build-Depends-I" to "Build-Depends", to fix
build on Salsa pipeline.
* Lintian: old-fsf-address-in-copyright-file. More minor things.
* Bump Standards version, no changes needed.
Checksums-Sha1:
f3b19f9b99eb4df08216fe328a7c5ec2fb0200c7 1619 lmodern_2.005-2.dsc
dec4d050c37cdf061e6d4973d22ea318d5eedb3d 19180 lmodern_2.005-2.debian.tar.xz
ce86ae931553e8aa4ac5196d9b3c9329656a798b 5125 lmodern_2.005-2_source.buildinfo
Checksums-Sha256:
ab791413e14b8ec1b1e0751a54f85efae128359ca5582fb4b6c2931f2a9e7b99 1619 lmodern_2.005-2.dsc
ba7c01ef694374e264d1e1c752cff093aec23ec9138433c4bd9a130f6245d962 19180 lmodern_2.005-2.debian.tar.xz
b029cf41b6420a8cb93302ad5af9e8be817a705b3f0f28c1a4dfb8f05cbe3595 5125 lmodern_2.005-2_source.buildinfo
Files:
2843afd475c8daadfc19bb5a7c7ff890 1619 fonts optional lmodern_2.005-2.dsc
0baee63e5b2032a65b6787d22fe9a4ab 19180 fonts optional lmodern_2.005-2.debian.tar.xz
fab6594b23d4a9e3bc5e699712f9aa9f 5125 fonts optional lmodern_2.005-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iNUEARYKAH0WIQRKnq6Z0VRDf4bMmAn98EQ6ARgcNAUCajZZIl8UgAAAAAAuAChp
c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0NEE5
RUFFOTlEMTU0NDM3Rjg2Q0M5ODA5RkRGMDQ0M0EwMTE4MUMzNAAKCRD98EQ6ARgc
NFMBAQDwMXmDJiEVGpGc8gCl1vEmwg8NhpQkddKcmV8nCHR/HwD9F4ydvw2gZpFJ
4uOx7nwFUPtOnSaaKmEMDS/AjgnVYA4=
=uf/A
-----END PGP SIGNATURE-----