[EMAIL PROTECTED] (Frank Küster) wrote: > Ralf Stubner has suggested a different approach in de.comp.text.tex: We > could add the corrected tfm files with names changed, and patch > lmodern.sty to use these changed tfm files. plain TeX users would have > to do it themselves, but they could do it.
That's an interesting idea. I'm not sure if it is better than directly modifying the original TFM files, however. Plain TeX users would have to modify their documents to use the new TFM names and modify them again when the font is fixed (or we would have to keep them for backward-compatibility). Moreover, the new documents would not compile on non-Debian systems where the modified TFM files would not exist (except maybe if they were distributed on CTAN...). >> Original file | After a round-trip conversion >> ------------------------------------------------ >> FontSpecific | FONTSPECIFIC >> LMTypewriter10 | LMTYPEWRITER10 [...] > I think "fix the conversion programs". But I don't even know how to > prettyprint web files... I guess we can consider it lossless. FWIW, it seems to be at least a convention to have the second text field (LMTypewriter10, here) in capitals (judging from a few random TFM files from teTeX 3 and http://www.math.umd.edu/~asnowden/comp-cont/tfm.html#header), so that might be a feature of tftopl to convert the text to uppercase. However, for the first field (the encoding), even though the majority I've seen are in capitals, a few of them are not, some of which (like cmtt10.tfm) were probably written by Knuth himself. Since noone protested about the fact that the fields are not all-capitals in current lmodern TFM files, it probably doesn't break many things. Therefore, if font experts tell me it's a bug that the encoding field is not all-capitals, I'm willing to change it; otherwise (if the chosen fix is to modify the TFM files, of course) I think I'll manually restore the original case in the TFM files obtained from pltotf. Anyway, since the discussion seems to be active in de.c.t.t, I'll wait one a few days in case better ideas come up from there (that doesn't mean I read it! ;-). Upstream might even say a word about how and when they will deal with the problem in the meantime... -- Florent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
