From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Nikishkin <lockywolf@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Small typo in calc.texi
Date: Tue, 13 Jun 2023 16:34:19 +0300 [thread overview]
Message-ID: <83edmfwko4.fsf@gnu.org> (raw)
In-Reply-To: <87bkhj8q4u.fsf@laptop.lockywolf.net> (message from Vladimir Nikishkin on Tue, 13 Jun 2023 21:08:00 +0800)
> From: Vladimir Nikishkin <lockywolf@gmail.com>
> Cc: emacs-devel@gnu.org
> Date: Tue, 13 Jun 2023 21:08:00 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Vladimir Nikishkin <lockywolf@gmail.com>
> >> Cc: emacs-devel@gnu.org
> >> Date: Tue, 13 Jun 2023 20:10:40 +0800
> >>
> >> >> @expr{C_{(-1)}} corresponds to the midi note number 0
> >> >
> >> > Are you sure? Texinfo in general doesn't allow unadorned { or }.
> >> >
> >> > What is the problem with @expr{C_(-1)}?
> >>
> >> What does "unadorned" mean?
> >
> > The literal characters '{' and '}'.
>
> I am not a pro on GNU texinfo. I just replaced
>
> @expr{C_(-1)} with @expr{C_{(-1)}}
>
> , despite syntax checker's complaints,
> and run make pdf. And the resulting pdf looks the way it should look,
> with all of (-1) in the sub-index.
>
> I am not sure if that is the way it should be solved, or it is just a
> co-incidence that it works for the pdf output.
What happens in the HTML output?
Anyway, since @expr is just an alias for @math, I guess we need some
TeX expert to help us out here. Anyone?
Btw, please in the future report any bugs, including these tiny ones,
to bug-gnu-emacs, so that they open an issue that can be tracked.
TIA.
next prev parent reply other threads:[~2023-06-13 13:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-03 3:45 Small typo in calc.texi Vladimir Nikishkin
2023-06-03 6:15 ` Eli Zaretskii
2023-06-13 3:40 ` Vladimir Nikishkin
2023-06-13 11:20 ` Eli Zaretskii
2023-06-13 12:10 ` Vladimir Nikishkin
2023-06-13 12:35 ` Eli Zaretskii
2023-06-13 13:08 ` Vladimir Nikishkin
2023-06-13 13:34 ` Eli Zaretskii [this message]
2023-06-13 13:45 ` Gregory Heytings
2023-06-13 13:55 ` Andreas Schwab
2023-06-13 19:39 ` Jens Schmidt
2023-06-15 7:12 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83edmfwko4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lockywolf@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).