From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 33796@debbugs.gnu.org
Subject: bug#33796: 27.0.50; Use utf-8 is all our Elisp files
Date: Tue, 18 Dec 2018 14:46:17 -0500 [thread overview]
Message-ID: <jwvk1k63a5r.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <83sgyud4it.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 18 Dec 2018 21:22:02 +0200")
> The .elc files are identical, but visiting the .el files will (or
> might) use different fonts, because the charset information is lost.
> (You will see that I jumped through some hoops to do something similar
> with etc/HELLO.)
That's indeed what I understand of the situation. But I don't think
it's a good reason to keep supporting non-utf-8 encoding for ever
(many/most programming languages only support a single encoding,
typically ASCII or utf-8 nowadays).
Part of the purpose of this bug-report is to try and come up with a plan ;-)
Hence, there are some questions:
- Do those people who edit those files really care about the difference?
After all, IIUC utf-8 is becoming standard even in the CJK world so
maybe the change is not that terrible (or at least, users have gotten
used to lowering their expectations in this respect).
- If the change is indeed problematic, can we adjust it by using
a file-global language tag?
- If that's not sufficient, can we use a scheme like that
of etc/HELLO but to keep the files directly usable as Elisp (so as to
have our cake and eat it too)?
> So I don't think we should make this change without considering
> whether the charset information is as important nowadays as it was
> back then.
How 'bout installing the titdic-cnv.el part which changes the coding
system used for the generated quail files (being auto-generated their
rending as source files shouldn't matter nearly as much since noone
should edit them)?
> And I'm not really sure who to ask about this.
I added Handa in the Cc, since I had forgotten to add him to the
X-Debbugs-Cc.
Stefan
next prev parent reply other threads:[~2018-12-18 19:46 UTC|newest]
Thread overview: 33+ 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 [this message]
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
2018-12-21 15:54 ` Eli Zaretskii
2018-12-21 13:55 ` Eli Zaretskii
2018-12-21 21:07 ` Paul Eggert
2018-12-22 1:19 ` Eric Lindblad
2018-12-22 7:56 ` etc/HELLO markup etc. (Was: 27.0.50; Use utf-8 is all our Elisp files) Eli Zaretskii
2018-12-22 8:12 ` etc/HELLO markup etc Eli Zaretskii
2018-12-22 19:41 ` Paul Eggert
2018-12-22 20:42 ` Eli Zaretskii
2018-12-23 7:47 ` Yuri Khan
2018-12-23 15:42 ` Eli Zaretskii
2018-12-23 15:53 ` Werner LEMBERG
2018-12-23 16:04 ` Eli Zaretskii
2018-12-23 21:11 ` Werner LEMBERG
2018-12-28 7:10 ` Eli Zaretskii
2018-12-29 7:23 ` handa
2018-12-29 7:37 ` Eli Zaretskii
2019-01-06 12:06 ` handa
2019-01-06 15:29 ` Eli Zaretskii
2019-01-06 17:26 ` Stefan Monnier
2019-01-06 17:39 ` Eli Zaretskii
2019-01-06 18:08 ` Stefan Monnier
2018-12-19 21:16 ` bug#33796: 27.0.50; Use utf-8 is all our Elisp files 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvk1k63a5r.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=33796@debbugs.gnu.org \
--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 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.