Bug#694323: Bug#694324: Bug#694323: [gsfonts] Fonts include copyrighted adobe fragment all right reserved

2012-12-03 Thread Ralf Stubner
On Thu, Nov 29, 2012 at 6:06 PM, Bastien ROUCARIES
roucaries.bast...@gmail.com wrote:
 On Thu, Nov 29, 2012 at 1:48 PM, Ralf Stubner ralf.stub...@gmail.com wrote:
 On Tue, Nov 27, 2012 at 11:58 PM, Norbert Preining prein...@logic.at wrote:
 Wait ... I am not sure either. Maybe fontfoge *also* contains and
 adds this code ... I just found the text in the sources of lmodern.

 For the record: Yes, fontforge does contain the code from Adobe.
 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).

 Could you relicence the URW-OtherSubrs.ps under a bsd license or even
 public domain ? It will help us to .

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.

 Moreover you entry are exactly the same of the last one of adobe code
 (Appendix 3: OtherSubrs Programs  p95)

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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#694323: Bug#694324: Bug#694323: [gsfonts] Fonts include copyrighted adobe fragment all right reserved

2012-11-29 Thread Ralf Stubner
On Tue, Nov 27, 2012 at 11:58 PM, Norbert Preining prein...@logic.at wrote:
 Wait ... I am not sure either. Maybe fontfoge *also* contains and
 adds this code ... I just found the text in the sources of lmodern.

For the record: Yes, fontforge does contain the code from Adobe.
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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#694324: Bug#694323: [gsfonts] Fonts include copyrighted adobe fragment all right reserved

2012-11-29 Thread Bastien ROUCARIES
On Thu, Nov 29, 2012 at 1:48 PM, Ralf Stubner ralf.stub...@gmail.com wrote:
 On Tue, Nov 27, 2012 at 11:58 PM, Norbert Preining prein...@logic.at wrote:
 Wait ... I am not sure either. Maybe fontfoge *also* contains and
 adds this code ... I just found the text in the sources of lmodern.

 For the record: Yes, fontforge does contain the code from Adobe.
 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).

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:
 Type Library uses the
OtherSubrsmechanism for thehint replacement function and the Flex function. 
These
OtherSubrs
procedures work by using some coordinated
Subrs
entries as well. All Adobe Type 1 font programs that use thesefunctions use 
them in precisely the same way. As a result, thesemantics of the PostScript 
language procedures included in the
OtherSubrs
array have stabilized to the point where the first four
OtherSubrs
entries and the first four
Subrs
entries have fixedmeanings. Some Type 1 font rasterization programs such as 
theAdobe Type Manager software product ignore the PostScript lan-guage 
definitions of the
OtherSubrs
entries, choosing internalcode for the particular functions according to the 
entry number.However, in order to work with the Type 1 BuildChar in 
Post-Script interpreters, some PostScript language implementation of the
OtherSubrs
entries must be included in any Type 1 font pro-gram that uses these 
functions. The PostScript language codeused in Adobe Type 1 font programs is 
listed in Appendix 3,“OtherSubrs Programs.”
OtherSubrs
entries beyond the first four are reserved for futureextensions. Each new
OtherSubrs
entry will be designed so thatit can be safely treated by an interpreter that 
does not understandits semantics. However, the first four
OtherSubrs
entries cannotbe so ignored; ignoring them will result in improper execution 
of the charstring.An
OtherSubrs
entry is invoked by the
callothersubr
command.This command takes (from the top of the Type 1 BuildChar oper-and 
stack down) the index number of the
OtherSubrs
entry, thenumber of arguments that entry expects, and the actual 
numericarguments.The complete calling sequence for an
OtherSubrs
procedure is:
arg1 arg2 . . . argn n othersubr#
callothersubr pop . . . pop

How do you cope with this by rewritting the program

 cheerio
 ralf


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#694324: Bug#694323: [gsfonts] Fonts include copyrighted adobe fragment all right reserved

2012-11-27 Thread Frank Kuester
Hi Bastien, hi Norbert,

Norbert Preining prein...@logic.at writes:

 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.:

 It is not a question of fontforge... THe lines mentioned come from
   pfcommon.dat
 which was inherited from metatype1.

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.

 Does that mean we have one more RC bug, namely that the sources are
 incomplete?  debian/copyright says:

 No. I don't consider the metatype sources necessary, because afterwards
 the fonts went through manual hinting and fixing.

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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#694323: [gsfonts] Fonts include copyrighted adobe fragment all right reserved

2012-11-27 Thread Norbert Preining
Hi Frank,

On Di, 27 Nov 2012, Frank Küster wrote:
  It is not a question of fontforge... THe lines mentioned come from
  pfcommon.dat
  which was inherited from metatype1.
 
 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.

Wait ... I am not sure either. Maybe fontfoge *also* contains and
adds this code ... I just found the text in the sources of lmodern.

 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?

I have no idea and I don't want to care about these things. I will not go
to the lenth of recreating the fonts at build time from any kind of
scripts.

Best wishes

Norbert

Norbert Preiningpreining@{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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#694323: [gsfonts] Fonts include copyrighted adobe fragment all right reserved

2012-11-25 Thread bastien ROUCARIES
Package: lmodern
Version: 2.004.2-1
Severity: serious
control: block -1 by 694308

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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#694323: [gsfonts] Fonts include copyrighted adobe fragment all right reserved

2012-11-25 Thread Norbert Preining

Hi Bastien,

so that was the outcome of the discussion on d-d ... you went ahead
with useless mass bug filing. Well done.

On So, 25 Nov 2012, bastien ROUCARIES wrote:
 % Copyright (c) 1987-1990 Adobe Systems Incorporated

Instead of digging around you *MIGHT* look for *WHERE* this comes from
to help everyone.

  This package include copyrighted font hinting from adobe. 
 
 Do I understand correctly that we're not supposed to do anything, but
 just wait until fontforge is fixed?  

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.

 | lm2.003mt1.zip -- Latin Modern source font files for the METATYPE1 package

It is alread lm2.004 ...

 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.:

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.

 Does that mean we have one more RC bug, namely that the sources are
 incomplete?  debian/copyright says:

No. I don't consider the metatype sources necessary, because afterwards
the fonts went through manual hinting and fixing.

Best wishes

Norbert

Norbert Preiningpreining@{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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org