From: Christopher Dimech <dimech@gmx.com>
To: tomas@tuxteam.de
Cc: emacs-devel@gnu.org
Subject: Re: Non-ASCII characters in Info files produced by Texinfo 7.1
Date: Tue, 24 Oct 2023 07:28:38 +0200 [thread overview]
Message-ID: <trinity-41516aed-a1ec-41af-896a-8749a1149f53-1698125318058@3c-app-mailcom-bs16> (raw)
In-Reply-To: <ZTdIpNustqffCETz@tuxteam.de>
> Sent: Tuesday, October 24, 2023 at 4:31 PM
> From: tomas@tuxteam.de
> To: emacs-devel@gnu.org
> Subject: Re: Non-ASCII characters in Info files produced by Texinfo 7.1
>
> On Mon, Oct 23, 2023 at 08:49:53PM +0000, Alan Mackenzie wrote:
> > Hello, Eli.
>
> [...]
>
> > I have always disliked the replacement of ASCII characters by non-ASCII
> > Unicode punctuation in working documents [...]
>
> Not a devel here, by a long stretch, so count me as anecdotal, but I'm
> with Alan here.
One should learn a language and get an article published (e.g. in Japan).
It is evident that only American Isolationists dislike anything unresembling
the modern english alphabet. Unicodes are your friends. The only problem
people have is that their keyboard prints a different character when hitting
the punctuation marks.
A much more serious problem is Texinfo continuing to rely upon Plain Tex only.
> Cheers
> --
> t
>
next prev parent reply other threads:[~2023-10-24 5:28 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 [this message]
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
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=trinity-41516aed-a1ec-41af-896a-8749a1149f53-1698125318058@3c-app-mailcom-bs16 \
--to=dimech@gmx.com \
--cc=emacs-devel@gnu.org \
--cc=tomas@tuxteam.de \
/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).