On Fri, Aug 26, 2022 at 10:20:08PM +0200, pertu...@free.fr wrote:
> On Fri, Aug 26, 2022 at 06:37:08PM +0100, Gavin Smith wrote:
> >
> > The LaTeX output will still use variable-width for @var unconditionally and
> > not subject to configuration. Hence there will be an inconsistency between
> >
On Fri, Aug 26, 2022 at 06:37:08PM +0100, Gavin Smith wrote:
>
> The LaTeX output will still use variable-width for @var unconditionally and
> not subject to configuration. Hence there will be an inconsistency between
> LaTeX output and texinfo.tex in this area, until after the next release.
>
> What I propose is making it the default for the next release, and
> stating in the manual and release notes that it will be changed in
> the subsequent release. That way we give people a chance to set it
> if they want to to avoid this change. After the next release we
> make @clear
On Fri, Aug 26, 2022 at 02:14:27PM +, Werner LEMBERG wrote:
>
> > I've added this as '@set txicodevaristt'. I've tested it with
> > texi2pdf -t '@set txicodevaristt'.
>
> Thanks, this works. Please document it in `texinfo.texi` :-)
>
>
> Werner
>
>
> PS: I still vote for making
> I've added this as '@set txicodevaristt'. I've tested it with
> texi2pdf -t '@set txicodevaristt'.
Thanks, this works. Please document it in `texinfo.texi` :-)
Werner
PS: I still vote for making `txicodevaristt` the default at least for
the next version.
On Sun, Aug 21, 2022 at 07:59:17PM +, Werner LEMBERG wrote:
>
> > It would be easy to add a switch to texinfo.tex that would switch
> > on/off the old behaviour. It would be used like "@set
> > txicodevarttsl" (probably with a better name).
>
> OK.
I've added this as '@set txicodevaristt'.
On Sun, Aug 21, 2022 at 11:14:16PM +0200, pertu...@free.fr wrote:
> On Sun, Aug 21, 2022 at 06:28:11PM +0100, Gavin Smith wrote:
> >
> > It wouldn't do anything for any other output formats, so there shouldn't
> > need to be any changes to texi2any, or any new commands to be added. My
> >
On Sun, Aug 21, 2022 at 06:28:11PM +0100, Gavin Smith wrote:
>
> It wouldn't do anything for any other output formats, so there shouldn't
> need to be any changes to texi2any, or any new commands to be added. My
> preference for this switch to be limited to texinfo.tex, as we shouldn't
> force
On Sun, Aug 21, 2022 at 07:59:17PM +, Werner LEMBERG wrote:
>
> > It wouldn't do anything for any other output formats, so there shouldn't
> > need to be any changes to texi2any, or any new commands to be added.
>
> Mhmm. I must admit that I haven't checked how HTML output was before
> and
> It would be easy to add a switch to texinfo.tex that would switch
> on/off the old behaviour. It would be used like "@set
> txicodevarttsl" (probably with a better name).
OK.
> It wouldn't do anything for any other output formats, so there shouldn't
> need to be any changes to texi2any, or
On Sun, Aug 21, 2022 at 04:54:36PM +, Werner LEMBERG wrote:
>
> >> However, using a Texinfo configuration as suggested in another
> >> e-mail would be a much friendlier solution for than that, which
> >> could even be issued using `texi2pdf`'s `--command` option or using
> >> a `texinfo.cnf`
>> However, using a Texinfo configuration as suggested in another
>> e-mail would be a much friendlier solution for than that, which
>> could even be issued using `texi2pdf`'s `--command` option or using
>> a `texinfo.cnf` file.
>
> Maybe, but it won't allow to use code + metaness in some
On Sun, Aug 21, 2022 at 03:02:56PM +, Werner LEMBERG wrote:
>
> >> Honestly, I don't like that – what I want *does* transport
> >> metaness! Using `@t` would demote this to a 'fancy font change to
> >> make the author happy', which is not true.
> >
> > You want meta-mess and also formatting
>> Honestly, I don't like that – what I want *does* transport
>> metaness! Using `@t` would demote this to a 'fancy font change to
>> make the author happy', which is not true.
>
> You want meta-mess and also formatting as code. So, you could
> define a @macro for that, like
>
> @macro
>> Two meta-ness levels meet in things like
>>
>> ```
>> Add command line option @code{--jobs @var{n}}, where @var{n} ...
>> ```
>
> Here @var{n} outputs in two different font styles.
Yes, and I think this is correct. Talking about a variable has a
different metaness in comparison to a
On Sun, Aug 21, 2022 at 11:24:56AM +, Werner LEMBERG wrote:
>
> > Another option is to change your document to use @t{@slanted{...},
> > which produces the slanted typewriter font.
>
> Honestly, I don't like that – what I want *does* transport metaness!
> Using `@t` would demote this to a
On Sun, Aug 21, 2022 at 11:24:56AM +, Werner LEMBERG wrote:
>
> [CCing `bug-texinfo` – this was lost by accident, right?]
Yes.
> Two meta-ness levels meet in things like
>
> ```
> Add command line option @code{--jobs @var{n}}, where @var{n} ...
> ```
Here @var{n} outputs in two different
On Sun, Aug 21, 2022 at 11:59:54AM +0200, pertu...@free.fr wrote:
> This is not directly related to the changes I proposed for @def*
> commands lines. Having @var always be roman with ligatures is Gavin
> decision, although I don't disagree with that decision. This is
> somewhat related to the
>> I'm *very* unhappy that `@var` in `@example` environments no longer
>> produce slanted typewriter but slanted roman – with ligatures!
>> Besides being extremely ugly, it completely ruins the fixed-width
>> spacing, which is of paramount importance. Please, PLEASE revert
>> this.
>
> To
[CCing `bug-texinfo` – this was lost by accident, right?]
> Slanted typewriter may be better in this context but there are at
> least two other contexts where slanted roman is better for @var (on
> definition lines, and in @table @code which is used for
> definitions).
Definition lines are a
On Sun, Aug 21, 2022 at 05:16:17AM +, Werner LEMBERG wrote:
>
> [texinfo.tex 2022-08-20.19]
>
> I'm *very* unhappy that `@var` in `@example` environments no longer
> produce slanted typewriter but slanted roman – with ligatures!
> Besides being extremely ugly, it completely ruins the
21 matches
Mail list logo
