From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mwd@md5i.com, handa@gnu.org, michael.albinus@gmx.de, emacs-devel@gnu.org
Subject: Re: Encoding of etc/HELLO
Date: Sat, 19 May 2018 11:23:01 -0700 [thread overview]
Message-ID: <013a179a-660a-f436-d9d4-af3466f8ff03@cs.ucla.edu> (raw)
In-Reply-To: <83in7jh6ab.fsf@gnu.org>
Eli Zaretskii wrote:
> What do you mean by "unified" here?
What I meant was that, as far as I know, in Emacs this font selection currently
does not depend on whether the charset is latin-iso8859-1 or latin-iso8859-3,
because in UTF-8 text those two charsets are always displayed the same way that
text sans charsets is displayed. And given the way the world has moved, it's
hard to imagine any future version of Emacs caring whether the charset is
latin-iso8859-1 or latin-iso8859-3 in UTF-8 text.
charset properties like japanese-jisx0208 do matter for display of course, and
so should be kept.
> The 'charset' property just tells Emacs to which "culture", so-called,
> or, if you want, to which language the greeting belongs
RFC 1896 specifies the 'lang' command to specify languages. Shouldn't etc/HELLO
do that instead of using 'charset'? That would seem to match the intent of
text/enriched better.
next prev parent reply other threads:[~2018-05-19 18:23 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 13:25 Encoding of etc/HELLO Eli Zaretskii
2018-04-20 15:34 ` Michael Albinus
2018-04-20 16:00 ` Eli Zaretskii
2018-04-20 16:16 ` Stefan Monnier
2018-04-20 17:22 ` Eli Zaretskii
2018-04-20 20:42 ` Stefan Monnier
2018-04-20 21:02 ` Clément Pit-Claudel
2018-04-20 21:26 ` Paul Eggert
2018-04-21 7:07 ` Eli Zaretskii
2018-04-21 14:58 ` Michael Welsh Duggan
2018-05-19 15:23 ` Eli Zaretskii
2018-05-19 17:17 ` Paul Eggert
2018-05-19 18:03 ` Eli Zaretskii
2018-05-19 18:23 ` Paul Eggert [this message]
2018-05-19 18:39 ` Eli Zaretskii
2018-05-19 19:38 ` Paul Eggert
2018-05-19 20:03 ` Eli Zaretskii
2018-05-20 8:56 ` Eli Zaretskii
2018-05-19 17:52 ` Michael Albinus
2018-04-20 17:39 ` Michael Albinus
2018-04-21 7:10 ` Eli Zaretskii
2018-04-21 14:40 ` Clément Pit-Claudel
2018-04-21 15:43 ` Eli Zaretskii
2018-04-21 15:52 ` Paul Eggert
2018-04-23 2:53 ` Stefan Monnier
2018-04-23 15:07 ` Eli Zaretskii
2018-04-23 15:23 ` Stefan Monnier
2018-04-23 16:12 ` Eli Zaretskii
2018-04-20 16:56 ` Paul Eggert
2018-04-20 17:37 ` Michael Albinus
2018-04-21 20:31 ` Juri Linkov
2018-04-23 16:25 ` Eli Zaretskii
2018-04-23 20:05 ` Juri Linkov
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=013a179a-660a-f436-d9d4-af3466f8ff03@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=handa@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=mwd@md5i.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 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.