Re: When should we put @key inside @kbd?

2022-01-01 Thread Eli Zaretskii
> Date: Sat, 1 Jan 2022 16:46:09 -0700 > From: Karl Berry > Cc: jwieg...@gmail.com, michael.albi...@gmx.de, r...@gnu.org, > bug-texinfo@gnu.org > > There seemed to be a general feeling in the 2018 discussion I linked > to that consistently unslanted fonts are good for @key. > > Then > @

Re: When should we put @key inside @kbd?

2022-01-01 Thread Karl Berry
There seemed to be a general feeling in the 2018 discussion I linked to that consistently unslanted fonts are good for @key. Then @kbd{foo @key{RET} bar} would have "foo" and "bar" slanted (by default), and "RET" unslanted. That seems weird to me. But whatever. -k

Re: When should we put @key inside @kbd?

2022-01-01 Thread Gavin Smith
On Sat, Jan 01, 2022 at 03:13:15PM -0700, Karl Berry wrote: > I found an inconsistency in the HTML output in the output for @key, > depending on whether it was in @kbd or not. It would be slanted only > if inside @kbd. > > Certainly that was an intentional feature, not a random "incon

Re: When should we put @key inside @kbd?

2022-01-01 Thread Karl Berry
I found an inconsistency in the HTML output in the output for @key, depending on whether it was in @kbd or not. It would be slanted only if inside @kbd. Certainly that was an intentional feature, not a random "inconsistency". Maybe @key should use the same font as @kbd, rather than a

Re: When should we put @key inside @kbd?

2022-01-01 Thread Gavin Smith
(Link to mailing list archive https://lists.gnu.org/archive/html/bug-texinfo/2018-03/msg00037.html) On Sat, Mar 10, 2018 at 9:08 PM Richard Stallman wrote: > So I think it is best for @key never to be slanted. I found an inconsistency in the HTML output in the output for @key, depending on wheth