[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ligatures reinstated (wrongly) by @r, @i, @b, @sansserif, @slanted i
From: |
Patrice Dumas |
Subject: |
Re: ligatures reinstated (wrongly) by @r, @i, @b, @sansserif, @slanted in texi2any |
Date: |
Mon, 22 Aug 2022 00:45:17 +0200 |
On Mon, Aug 22, 2022 at 12:35:44AM +0200, Patrice Dumas wrote:
> Hello,
>
> In all the formats output by texi2any, except in LaTeX which is
> more consistent with TeX, @r, @i, @b, @sansserif and @slanted switch
> back to normal context if in code/monospace context. This is not
> the case in LaTeX output, only @r, @cite and @var restore ligatures
> for --, ---...
>
> At the same time, font changes are combined (this is the case for LaTeX
> too). This leads to a very inconsistent output, for example
> @code{@slanted{a--b}} leads to a typewriter font with -- being rendered
> as an en dash and not as two -.
>
> I propose to have only @r, among font commands restore ligatures. Would
> that be ok?
Forgot to say that I did not find that specific issue being discussed,
the only thread I found is the one were Karl said that we should not
specify anything for nested marking @-commands.
--
Pat
- ligatures reinstated (wrongly) by @r, @i, @b, @sansserif, @slanted in texi2any, Patrice Dumas, 2022/08/21
- Re: ligatures reinstated (wrongly) by @r, @i, @b, @sansserif, @slanted in texi2any,
Patrice Dumas <=
- Re: ligatures reinstated (wrongly) by @r, @i, @b, @sansserif, @slanted in texi2any, Werner LEMBERG, 2022/08/21
- Re: ligatures reinstated (wrongly) by @r, @i, @b, @sansserif, @slanted in texi2any, Gavin Smith, 2022/08/22
- Prev by Date:
ligatures reinstated (wrongly) by @r, @i, @b, @sansserif, @slanted in texi2any
- Next by Date:
Re: ligatures reinstated (wrongly) by @r, @i, @b, @sansserif, @slanted in texi2any
- Previous by thread:
ligatures reinstated (wrongly) by @r, @i, @b, @sansserif, @slanted in texi2any
- Next by thread:
Re: ligatures reinstated (wrongly) by @r, @i, @b, @sansserif, @slanted in texi2any
- Index(es):