[latexrefman] it switches from one encoding to another with the @code{\selectfont} or @code{\fontencoding} command

[Vincent Belaïche]

Any feedback (I will replace « or » by « and » in my next commit to
[en], last notice before doing that by end of this week, ok we can
still undo if I am wrong) ?

  V.

Le lun. 6 sept. 2021 à 11:41, Vincent Belaïche
<vincent.belaiche at gmail.com> a écrit :
>
> Dear Karl,
> I did some experiment (attached). If you pass options to fontenc in
> the order OT1, T1, the two last rows will output <|> instead of ¡—¿.
> This shows that without \selectfont the encoding is not activated.
>
> Le dim. 5 sept. 2021 à 00:16, Karl Berry <karl at freefriends.org> a écrit :
> >
> >     My understanding is the \fontencoding does no immediate switching as
> >     such,
> >
> > Yes it does. Maybe not at the user level, I'm not sure what the
> > visible result is, but in the code the switch is made in \fontencoding.
> >
> >     it just sets the encoding to which the next \selectfont will
> >     switch. So ``or'' should be replaced by ``and''.
> >
> > No it shouldn't.
> >
> > When I look at the actual definition of \fontencoding (in ltfssbas.dtx),
> > the "text-setting" commands from \DeclareFontEncoding are executed:
> >
> > \DeclareRobustCommand\fontencoding[1]{%
> > ..
> >   \csname T@\f at encoding\endcsname
> > ..
> > }
> >
> > The \csname T@\f at encoding\endcsname cs is where the "text-setting"
> > commands were saved.
> >
> > At a glance, I do not see them being executed as being part of
> > \selectfont.
> >
> > So I suggest doing some experiments to find out the actual facts.
> > Failing that, I suggest leaving it alone. -k