On Thu, Nov 29, 2012 at 1:48 PM, Ralf Stubner <[email protected]> wrote: > On Tue, Nov 27, 2012 at 11:58 PM, Norbert Preining <[email protected]> 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 [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
