From: Eli Zaretskii <eliz@gnu.org>
To: eggert@cs.ucla.edu
Cc: handa@gnu.org, emacs-devel@gnu.org
Subject: Re: Encoding of etc/HELLO
Date: Sun, 20 May 2018 11:56:22 +0300 [thread overview]
Message-ID: <83zi0ug0y1.fsf@gnu.org> (raw)
In-Reply-To: <83efi7h0qi.fsf@gnu.org> (message from Eli Zaretskii on Sat, 19 May 2018 23:03:17 +0300)
> Date: Sat, 19 May 2018 23:03:17 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: mwd@md5i.com, handa@gnu.org, michael.albinus@gmx.de, emacs-devel@gnu.org
>
> > In the meantime how about if we mark up etc/HELLO with lang commands instead of
> > x-charset commands, except that we also keep x-charset commands that actually
> > affect Emacs display in common use (e.g., CJK charsets)? When we get lang
> > working, we can then remove the remaining x-charset commands.
>
> I'd rather we first fixed the charset properties coverage in the file
> so that they make more sense.
Now done on the master branch.
As for 'lang', it sounds strange to me to use a text property that has
absolutely no meaning in the current Emacs. I think we should first
develop at least some initial support for this property, and only then
start using it in files we distribute.
next prev parent reply other threads:[~2018-05-20 8:56 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
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 [this message]
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
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=83zi0ug0y1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=handa@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).