From: Eli Zaretskii <eliz@gnu.org>
To: Mike Kupfer <mkupfer@alum.berkeley.edu>
Cc: 59094@debbugs.gnu.org
Subject: bug#59094: 29.0.50; ediff-revision flags wrong lines in etc/HELLO
Date: Mon, 07 Nov 2022 18:49:22 +0200 [thread overview]
Message-ID: <834jvazp4d.fsf@gnu.org> (raw)
In-Reply-To: <5768.1667836176@alto> (message from Mike Kupfer on Mon, 07 Nov 2022 07:49:36 -0800)
> From: Mike Kupfer <mkupfer@alum.berkeley.edu>
> cc: 59094@debbugs.gnu.org
> Date: Mon, 07 Nov 2022 07:49:36 -0800
>
> Are the charset tags (annotations) really necessary, given the setting
> of 'coding' in the local variables?
Yes, they help Emacs choose suitable fonts where the same characters
should use different fonts depending on the character set.
> The reason I ask is that the files that I saved last night from the old
> and new Ediff buffers can be reloaded, and Ediff is able to correctly
> show the changes. Yet I don't see any visual distinctions between the
> new file and etc/HELLO, even though the new file's mode is just
> Fundamental, not Fundamental Enriched. (Even the orange text on lines 1
> and 34 is duplicated in the saved file, which I confess puzzles me.)
The effect of the charsets is really relevant to CJK cultures, and
even that is nowadays less important than 20 years ago.
next prev parent reply other threads:[~2022-11-07 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 5:29 bug#59094: 29.0.50; ediff-revision flags wrong lines in etc/HELLO Mike Kupfer
2022-11-07 15:10 ` Eli Zaretskii
2022-11-07 15:49 ` Mike Kupfer
2022-11-07 16:49 ` Eli Zaretskii [this message]
2022-11-07 20:26 ` Mike Kupfer
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=834jvazp4d.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59094@debbugs.gnu.org \
--cc=mkupfer@alum.berkeley.edu \
/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).