Bug#295368: lmodern: Typewriter fonts are not monospaced

2005-02-24 Thread Frank Küster
Florent Rougon [EMAIL PROTECTED] schrieb: All in all, it seems people would feel more comfortable if only text files such as .fd files were patched. OK. This is easier for me, and I currently only use the LaTeX format, so... I looked at Walter's patch but I don't understand why he didn't

Bug#295368: lmodern: Typewriter fonts are not monospaced

2005-02-24 Thread Florent Rougon
[EMAIL PROTECTED] (Frank Küster) wrote: He said that he just didn't know that this was sufficient. Therefore, if you have checked that it fixes the problem, and does it for all font shapes, yours is better. Well, the LaTeX Companion (1st edition, p. 200) clearly documents that it should work:

Bug#295368: lmodern: Typewriter fonts are not monospaced

2005-02-22 Thread Florent Rougon
Hi, So, according to Walter, it is not worth the risk or lack of traceability patching the TFM files, because very few people would be using plain TeX with T1 encoding and these fonts, and he expects Hans Hagen to write a ConTeXt-specific patch if he cared about the problem, etc. All in all, it

Bug#295368: lmodern: Typewriter fonts are not monospaced

2005-02-16 Thread Frank Küster
Florent Rougon [EMAIL PROTECTED] schrieb: [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

Bug#295368: lmodern: Typewriter fonts are not monospaced

2005-02-16 Thread Florent Rougon
[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

Bug#295368: lmodern: Typewriter fonts are not monospaced

2005-02-15 Thread Frank Küster
Hallo Florent, Frank Küster [EMAIL PROTECTED] schrieb: Walter Schmidt, who is a real TeX font expert, answered: , | indeed, the Latin Modern typewriter fonts are broken: | the metrics exhibit non-zero values of \fontdimen3 and \fontdimen4, | so that the inter-word space becomes

Bug#295368: lmodern: Typewriter fonts are not monospaced

2005-02-15 Thread Florent Rougon
[EMAIL PROTECTED] (Frank Küster) wrote: Hallo Florent, Hallo, and thanks for the report. Maybe this can be changed in the afm files, and the tfm files regenerated with afm2tfm? I wouldn't feel comfortable with that. I would prefer using tftopl on the tfm files, modifying the fontdimens in

Bug#295368: lmodern: Typewriter fonts are not monospaced

2005-02-15 Thread Frank Küster
Florent Rougon [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] (Frank Küster) wrote: Hallo Florent, Hallo, and thanks for the report. Maybe this can be changed in the afm files, and the tfm files regenerated with afm2tfm? I wouldn't feel comfortable with that. I would prefer using tftopl on

Bug#295368: lmodern: Typewriter fonts are not monospaced

2005-02-15 Thread Florent Rougon
[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.