[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:
Normally, changes apply to a whole family; for example, you may want
to prohibit hyphenation for all words in the typewriter family. In
this case, the third argument of \DeclareFontFamily should be used. If
the changes should only apply to a specific font shape group, you have
to use the sixth argument of \DeclareFontShape. In other words, when a
font is loaded, NFSS first applies the argument of \DeclareFontFamily
and then the sixth argument of \DeclareFontShape, so that it can
override the load options specified for the whole family if necessary.
I checked with the attached .tex file, and it does work.
\documentclass[a4paper,11pt,draft]{article}
\usepackage[T1]{fontenc}
\usepackage[latin1]{inputenc}
\usepackage[nohead,scale={0.4,0.9}]{geometry}
\DeclareTextSymbol{\Lbracket}{T1}{91}
\DeclareTextSymbol{\Rbracket}{T1}{93}
\newcommand{\FontTest}[3]{%
\section{#1/#2/#3}
\fontfamily{#1}\fontseries{#2}\fontshape{#3}\selectfont
fontdimen2: \the\fontdimen2\font\\
fontdimen3: \the\fontdimen3\font\\
fontdimen4: \the\fontdimen4\font
uuu\Lbracket xxxx\Rbracket abcdefg\Lbracket dfdfdf\Rbracket
\{dddccc\}bbbbbbbbbbmm\\
\mbox{}\ \ \ \Lbracket xxxx\Rbracket abcdefg\Lbracket dfdfdf\Rbracket
\{dddccc\}bbbbbbbbbbmm\\
\mbox{}\ \ \ \ \ \ \ \ \ abcdefg\Lbracket dfdfdf\Rbracket
\{dddccc\}bbbbbbbbbbmm}
\begin{document}
\setlength{\parindent}{0pt}%
\setlength{\parskip}{\baselineskip}%
%
\FontTest{cmtt}{m}{n}
\FontTest{lmtt}{m}{n}
\FontTest{lmtt}{m}{it}
\FontTest{lmtt}{m}{sl}
\FontTest{lmtt}{m}{sc}
\FontTest{lmtt}{bx}{n}
\FontTest{lmtt}{bx}{it}
\FontTest{lmtt}{bx}{sl}
\end{document}
[ I ended up throwing away the Verbatim environment because I couldn't
get it to work in a command definition with the contents *also* in the
command definition... ]
> No, David Kastrup explained why it isn't needed. He wrote, I'm
> translating:
[...]
Good. Then I'll apply the patch as included in my previous mail,
extended to all encodings.
> (He didn't say why, I guess because there's no minus in [EMAIL PROTECTED])
That I cannot say.
Thanks to you and the de.comp.text.tex contributors!
--
Florent
