From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>, 33796@debbugs.gnu.org
Subject: bug#33796: 27.0.50; Use utf-8 is all our Elisp files
Date: Fri, 21 Dec 2018 08:46:11 -0500 [thread overview]
Message-ID: <jwvr2eb0zp4.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <83va3nban3.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 21 Dec 2018 09:29:36 +0200")
> Not necessarily. I would actually like to hear opinions from people
> who read CJK scripts who think the distinction no longer matters, not
> these days.
BTW, while looking closer, I'm inclined to think that maybe their
opinion doesn't matter that much: while the general issue of font choice
for CJK text in Elisp files might really affect some users, in the
specific case of the files affected by this patch I believe this likely
isn't the case, because while there are affected *chars*, there is no
affected *text*. More specifically, AFAICT the affected chars are all
part of the code and they represent themselves rather than being used as
a carrier for a specific meaning in a text (because all this code is
about how to insert specific chars).
[ Snipped the rest about etc/HELLO. ]
Stefan "I asked Chong what he thought about it but said that
he's not using CJK enough to be a good source of opinion"
next prev parent reply other threads:[~2018-12-21 13:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 18:46 bug#33796: 27.0.50; Use utf-8 is all our Elisp files Stefan Monnier
2018-12-18 19:22 ` Eli Zaretskii
2018-12-18 19:46 ` Stefan Monnier
2018-12-19 17:54 ` Paul Eggert
2018-12-19 18:11 ` Eli Zaretskii
2018-12-19 22:13 ` Paul Eggert
2018-12-20 16:06 ` Eli Zaretskii
2018-12-20 21:49 ` Paul Eggert
2018-12-21 7:29 ` Eli Zaretskii
2018-12-21 13:46 ` Stefan Monnier [this message]
2018-12-21 15:54 ` Eli Zaretskii
2018-12-21 13:55 ` Eli Zaretskii
2018-12-19 21:16 ` Stefan Monnier
2019-01-08 2:20 ` 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=jwvr2eb0zp4.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=33796@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@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).