From: Ulrich Mueller <ulm@gentoo.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Non-ASCII characters in Info files produced by Texinfo 7.1
Date: Thu, 26 Oct 2023 11:54:15 +0200 [thread overview]
Message-ID: <ucyx13e0o@gentoo.org> (raw)
In-Reply-To: <83il6thii4.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 26 Oct 2023 11:53:39 +0300")
>>>>> On Thu, 26 Oct 2023, Eli Zaretskii wrote:
> Are there any other opinions? For now, the opinions are 5:3 in favor
> of keeping the pre-7.1 behavior of producing Unicode characters,
> i.e. in favor of adding "-c ASCII_DASHES_AND_QUOTES=0" to our makeinfo
> options. If no other opinions will emerge within a few days that
> change this picture, I will add that switch to our Makefile's.
If most people think that the old behaviour is preferable, maybe also
ask the texinfo maintainers to change their default?
IMHO it doesn't make much sense if different parts of the GNU system
disagree from each other.
next prev parent reply other threads:[~2023-10-26 9:54 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 19:12 Non-ASCII characters in Info files produced by Texinfo 7.1 Eli Zaretskii
2023-10-23 19:52 ` Stefan Kangas
2023-10-24 5:02 ` Visuwesh
2023-10-24 8:52 ` Stefan Kangas
2023-10-24 9:07 ` Visuwesh
2023-10-24 11:45 ` Eli Zaretskii
2023-10-25 6:45 ` Juri Linkov
2023-10-25 12:31 ` Eli Zaretskii
2023-10-25 12:33 ` Eli Zaretskii
2023-10-25 13:12 ` Gerd Möllmann
2023-10-23 20:49 ` Alan Mackenzie
2023-10-24 4:31 ` tomas
2023-10-24 5:28 ` Christopher Dimech
2023-10-24 7:42 ` tomas
2023-10-24 6:54 ` Yuri Khan
2023-10-24 11:15 ` Eli Zaretskii
2023-10-24 11:20 ` Eli Zaretskii
2023-10-24 8:02 ` Manuel Giraud via Emacs development discussions.
2023-10-24 8:21 ` Ulrich Mueller
2023-10-24 9:39 ` Manuel Giraud via Emacs development discussions.
2023-10-24 10:59 ` Po Lu
2023-10-24 12:04 ` Eli Zaretskii
2023-10-24 11:27 ` Eli Zaretskii
2023-10-24 11:22 ` Eli Zaretskii
2023-10-24 12:28 ` Manuel Giraud via Emacs development discussions.
2023-10-24 12:45 ` Eli Zaretskii
2023-10-24 13:43 ` Manuel Giraud via Emacs development discussions.
2023-10-26 8:53 ` Eli Zaretskii
2023-10-26 9:43 ` Alan Mackenzie
2023-10-26 10:11 ` Eli Zaretskii
2023-10-26 10:55 ` Alan Mackenzie
2023-10-26 11:18 ` Eli Zaretskii
2023-12-09 4:01 ` Richard Stallman
2023-10-26 9:54 ` Ulrich Mueller [this message]
2023-10-26 10:14 ` Eli Zaretskii
2023-10-26 10:31 ` Gregory Heytings
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=ucyx13e0o@gentoo.org \
--to=ulm@gentoo.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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).