From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Brooks <db48x@db48x.net>
Cc: 66944@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#66944: 30.0.50; [PATCH] make calc parse fractions written using U+2044 FRACTION SLASH
Date: Sat, 27 Jan 2024 16:00:40 +0200 [thread overview]
Message-ID: <861qa298qf.fsf@gnu.org> (raw)
In-Reply-To: <87bk96apkq.fsf@db48x.net> (message from Daniel Brooks on Sat, 27 Jan 2024 05:11:33 -0800)
> From: Daniel Brooks <db48x@db48x.net>
> Cc: stefankangas@gmail.com, 66944@debbugs.gnu.org
> Date: Sat, 27 Jan 2024 05:11:33 -0800
>
> > Please try rewriting these to avoid non-ASCII characters in Texinfo
> > source files, since processing those with TeX could cause problems.
> > Where possible, please use the special Texinfo commands described in
> > the "Insertions" chapter of the Texinfo manual and its sections. If
> > some character cannot be written using ASCII characters as described
> > in that section, please just name it, as in "U+2044 FRACTION SLASH",
> > but don't include it verbatim.
>
> Thanks, I hadn’t read that. Done.
Thanks, but I'm not sure @U{HEX} will always work in the printed
output. Did you try to say "make calc.pdf" in doc/emisc/? If not,
can you try that?
If you see errors about @U when generating PDF format, we will need to
make use of @U conditional by using @ifnottex, and in @iftex case omit
the @U{HEX} parts.
Thanks.
next prev parent reply other threads:[~2024-01-27 14:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-05 8:18 bug#66944: 30.0.50; [PATCH] make calc parse fractions written using U+2044 FRACTION SLASH Daniel Brooks
2024-01-13 10:52 ` Stefan Kangas
2024-01-13 16:11 ` Daniel Brooks
2024-01-27 9:09 ` Eli Zaretskii
2024-01-27 13:11 ` Daniel Brooks
2024-01-27 14:00 ` Eli Zaretskii [this message]
2024-01-27 14:26 ` Daniel Brooks
2024-01-27 14:49 ` Eli Zaretskii
2024-01-27 15:16 ` Daniel Brooks
2024-01-27 18:41 ` john muhl via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-28 8:20 ` Daniel Brooks
2024-01-29 12:51 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=861qa298qf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66944@debbugs.gnu.org \
--cc=db48x@db48x.net \
--cc=stefankangas@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.