From: Alan Mackenzie <acm@muc.de>
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: Mon, 23 Oct 2023 20:49:53 +0000 [thread overview]
Message-ID: <ZTbccenXjg522PpD@ACM> (raw)
In-Reply-To: <83o7gpm9uy.fsf@gnu.org>
Hello, Eli.
On Mon, Oct 23, 2023 at 22:12:21 +0300, Eli Zaretskii wrote:
> Texinfo 7.1, released a few days ago, changed the behavior wrt
> characters produced from quotes, apostrophes and en- and em-dashes: by
> default, it now produces the ASCII equivalents. So, for example, "--"
> in the Texinfo source remains "--" in the produced Info file, where
> previous versions would produce a real en-dash '–'.
> The main reason for this change is that it makes it easier to grep the
> Info files.
> To revert to previous behavior, we will need to pass an optional
> argument to the makeinfo command in our Makefile's. But before I make
> this change, I would like to know if people here want the new behavior
> or the old one.
Thanks for raising this issue on the mailing list.
> For those who want the read about the reasons for this change in
> behavior, here are the links:
> https://lists.gnu.org/archive/html/automake-patches/2022-12/msg00000.html
> https://lists.gnu.org/archive/html/automake-patches/2022-12/msg00019.html
> https://lists.gnu.org/archive/html/bug-texinfo/2023-06/msg00000.html
> What do people think about this?
I have always disliked the replacement of ASCII characters by non-ASCII
Unicode punctuation in working documents; it makes those documents less
easy to search, whether by grep or by C-s, or whatever, and these
characters are displayed in an obtrusive face.
Quite likely, there will also be people who dislike the use of ASCII for
these purposes.
So I would vote for either texinfo's new default of using ASCII quotes,
etc., or having a configuration option to set/unset the command line
option to texinfo.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2023-10-23 20:49 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZTbccenXjg522PpD@ACM \
--to=acm@muc.de \
--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 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.