From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>, Kenichi Handa <handa@gnu.org>
Cc: monnier@iro.umontreal.ca, 33796@debbugs.gnu.org
Subject: bug#33796: 27.0.50; Use utf-8 is all our Elisp files
Date: Thu, 20 Dec 2018 13:49:44 -0800 [thread overview]
Message-ID: <5f113128-36c9-30c6-3413-8dc36051e058@cs.ucla.edu> (raw)
In-Reply-To: <835zvochdj.fsf@gnu.org>
On 12/20/18 8:06 AM, Eli Zaretskii wrote:
> my opinion should also count, right?
Of course, although my impression was that you weren't expressing an
opinion and were soliciting opinions. If your opinion is that we should
not make the change, then of course that counts.
> we need the opinion of people
> who might be actually affected by the proposed change,
I assume you mean that we need the opinion of people who would be
affected _negatively_. Stefan and I would actually be affected
_positively_ by the proposed change, for the reasons we stated.
> All 3 of us simply don't care,
No, actually I do care. Non-UTF-8 source files are a real annoyance for
me, on a fairly regular basis. Stefan seems to care too, though I
suspect he doesn't care as much as I do.
> . Displaying HELLO doesn't show "gibberish", it shows UTF-8 encoded
> text with pure-ASCII markup.
You're right. My apologies: when I wrote "gibberish" I was looking at
the output of "git diff emacs-26..master etc/HELLO", which does indeed
display gibberish but that's not the current encoding's fault.
> But since in your opinion the current situation is a
> "disaster", you seem to be saying that we should go back to ISO-2022?
Not at all, but I do think we should cut down on the unnecessary markup
in that file. The markup should be used only when it helps. Text like
"<x-charset><param>mule-unicode-0100-24ff</param> </x-charset>" is not
helping anybody; the file should just contain " " there. Most of the
markup in that file is not necessary for proper display, and just gets
in the way when using tools other than Emacs.
> . By the above reasoning, if Emacs is enhanced to interpret HTML/XML
> and show typefaces instead of markup, you will see that as a
> regression and complain that raw HTML files are "gibberish"?
I hope Emacs doesn't do any such thing by default. I often use Emacs to
edit .html and .xml files, and if it attempted to render these files by
default I would be inconvenienced. Presumably there would be an option
to keep the old behavior, and I'd use that option.
> . You have find-file-literally to show you HELLO exactly as any
> text-mode tool will see it
No, because find-file-literally shows hard-to-read stuff like this:
</x-charset><x-charset><param>greek-iso8859-7</param>Greek
(\316\265\316\273\316\273\316\267\316\275\316\271\316\272\316\254)
\316\223\316\265\316\271\316\254 \317\203\316\261\317\202
which differs from (and is even worse than) what an ordinary tool like
git or cat shows:
</x-charset><x-charset><param>greek-iso8859-7</param>Greek (ελληνικά)
Γειά σας
It would be better to remove this particular markup, so that git etc.
would show this:
Greek (ελληνικά) Γειά σας
which is what Emacs ordinarily shows.
> . No experience in Enriched mode is needed to edit HELLO, you just
> need to apply text properties (via facemenu.el commands or the
> menu-bar's Edit->Text Properties menu). And these properties are
> optional.
Let's leave most of them out then, as they're not working well in
etc/HELLO. I don't use that menu, but I took your hint and just now
tried it, by selecting the abovementioned word "ελληνικά" and menuing to
Edit > Text Properties > Describe Properties, but all it said was 'Text
content at position 1530: There are text properties here: unknown
("x-charset")'. This missed the point that the word's character set is
greek-iso8859-7 which is a special hack that hints to Emacs (and nobody
else, I guess? I couldn't find documentation for this stuff even in the
Emacs manuals) that the text should be displayed with a Greek font
instead of the same Greek font that Emacs would be using anyway. And I
didn't see an easy way to see visually that the this (unnecessary)
<x-charset> hint is misplaced, since it should be placed so that it
applies only to the Greek text and not to the surrounding English text
in the same line.
next prev parent reply other threads:[~2018-12-20 21:49 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 [this message]
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-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=5f113128-36c9-30c6-3413-8dc36051e058@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=33796@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=handa@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).