From: Alan Mackenzie <acm@muc.de>
To: Drew Adams <drew.adams@oracle.com>, 3501@emacsbugs.donarmstrong.com
Subject: bug#3501: 23.0.94; Use Unicode in Info (?)
Date: Tue, 9 Jun 2009 17:17:58 +0000 [thread overview]
Message-ID: <20090609171758.GB11634@muc.de> (raw)
In-Reply-To: <CEA3B46F10834364B599F19FC937AEFD@us.oracle.com>
Hi, Drew!
On Mon, Jun 08, 2009 at 08:23:49PM -0700, Drew Adams wrote:
> > > Can't we use Unicode or in some other way use accented characters in
> > > people's names (when appropriate)?
> I was thinking of display - what the user sees. But it should, if
> possible, affect also searching (including regexp searching) and any
> other behavior the user can notice. The user should experience only the
> fancy character, both visually and every other way.
Please no. I absolutely do not want to "experience" fancy unicode characters
when reading info. It's bad enough getting them in email and in usenet
postings from Xah Lee. ;-) ASCII can be displayed perfectly on any
screen or teletype or even punched card puncher that can display English
at all. Unicode, by contrast, needs a fancy setup, even if lots of
computers already have such a setup.
Unless accented hackers (of whom we're not two) find the ASCII rendering
of their names offensive, but I haven't seen any evidence of this.
> What is in the actual file is not important here, except in so far as
> it might affect perception.
> > What goes into the Info files depends on the directives in the
> > Texinfo sources and on the command line arguments used when makeinfo
> > was invoked to produce the Info files. You will see in the `doc'
> > directory that we already invoke makeinfo with --enable-encoding
> > switch in some cases.
> Whatever is already done is not sufficient in this regard, as indicated
> in the original report: I don't see composed characters; I see
> punctuation in the middle of people's names. I see J/orgensen, not
> Jørgensen.
Is that bad? J/orgensen is more readable (IMHO) than JÀ«rgensen (or
whatever that letter's two bytes actually are).
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2009-06-09 17:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 21:58 bug#3501: 23.0.94; Use Unicode in Info (?) Drew Adams
2009-06-09 3:11 ` Eli Zaretskii
2009-06-09 3:23 ` Drew Adams
2009-06-09 3:42 ` Eli Zaretskii
2009-06-09 4:10 ` Drew Adams
2009-06-09 17:17 ` Alan Mackenzie [this message]
2009-06-09 17:43 ` Drew Adams
2009-06-09 18:17 ` Alan Mackenzie
2009-06-09 19:56 ` Drew Adams
2009-06-09 21:10 ` Alan Mackenzie
2009-06-09 21:31 ` Lennart Borgman
2009-06-09 22:48 ` Jason Rumney
2009-06-09 17:46 ` Lennart Borgman
2009-06-25 23:12 ` Stefan Monnier
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=20090609171758.GB11634@muc.de \
--to=acm@muc.de \
--cc=3501@emacsbugs.donarmstrong.com \
--cc=drew.adams@oracle.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).