From: Juri Linkov <juri@linkov.net>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Eli Zaretskii <eliz@gnu.org>, Paul Eggert <eggert@cs.ucla.edu>,
emacs-devel@gnu.org
Subject: Re: Encoding of etc/HELLO
Date: Sat, 21 Apr 2018 23:31:22 +0300 [thread overview]
Message-ID: <8736zopahx.fsf@mail.linkov.net> (raw)
In-Reply-To: <87in8l6ap1.fsf@gmx.de> (Michael Albinus's message of "Fri, 20 Apr 2018 19:37:30 +0200")
>> It's true that this isn't important. Still, I like the the "hello"
>> emoji; it's friendly.
>
> Yes, that was the idea. It's a pity that we cannot add valid utf-8
> characters to etc/HELLO, when they are not iso-2022-7bit compatible.
I don't understand why it's impossible to create a charset like the
existing mule-unicode-e000-ffff but for character range over U+FFFF
to include such characters as U+1F44B. Or is this an inherent limitation
of the iso-2022-7bit coding system?
next prev parent reply other threads:[~2018-04-21 20:31 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
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 [this message]
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=8736zopahx.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
/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).