[EMAIL PROTECTED] (Frank K�ster) wrote: > You are right, this is a drawback. We can still give lmodern.sty a new > version number, even if it is in fact the tfm files that have changed, > to ease debugging a little.
Yes. >> 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...). > > This would only be the case if lmodern.sty was included in the document > in a filecontents environment, wouldn't it? You're thinking LaTeX, but I'm discussing other formats here, such as plain TeX. Otherwise, there is no need to fiddle with the TFM files: as you said yesterday, for LaTeX users, it is sufficient to modify the fontdimens in lmodern.sty to fix the problem. But, in order to fix the problem for TeX users, we need to fix the TFM files. We were considering the possibility of leaving the original TFM files intact, and adding new ones with fontdimen3 and fontdimen4 fixed. So, the new files, e.g. cork-fmtt10.tfm, would be usable in plain TeX with stuff like \font\foobar=cork-fmtt10. I was objecting that a document containing such code would not compile on a system where cork-fmtt10.tfm doesn't exist. So, unless the fixed TFM files were somehow distributed out of Debian, this would encourage users to write non-portable (Debian-specific) documents. And even if they were distributed on CTAN, we would have to support these names just about forever or force people to again modify their documents once lmodern's upstream releases a fixed version... > I'll keep you informed. Thanks. -- Florent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
