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 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 choose
the way in the attached patch; to me, it looks simpler and less
redundant (only provided for t1lmtt.fd; the same modification could be
done for the other encodings, of course).
Could you enlighten me?
--- /usr/share/texmf/tex/latex/lm/t1lmtt.fd 2004-04-14 09:20:00.000000000 +0200
+++ t1lmtt.fd 2005-02-22 10:52:24.000000000 +0100
@@ -1,5 +1,8 @@
-\ProvidesFile{t1lmtt.fd}[2003/07/22 v1.1 Font defs for Latin Modern]
-\DeclareFontFamily{T1}{lmtt}{\hyphenchar [EMAIL PROTECTED]
+\ProvidesFile{t1lmtt.fd}[2005/02/22 v1.1-Debian.0 Font defs for Latin Modern]
+\DeclareFontFamily{T1}{lmtt}{\hyphenchar [EMAIL PROTECTED]
+ % Debian patch: set the stretchability and
+ % shrinkability of the interword space to zero.
+ [EMAIL PROTECTED]@}
\DeclareFontShape{T1}{lmtt}{m}{n}
{<-8.5> cork-lmtt8 <8.5-9.5> cork-lmtt9
<9.5-11> cork-lmtt10 <11-> cork-lmtt12
Also, even if the patch seems to work as it is, I don't really know if a
\relax could be needed after the "[EMAIL PROTECTED]": I know a bit about LaTeX
programming, but not yet raw TeX... Please check.
Thanks,
--
Florent
