From: handa <handa@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: eggert@cs.ucla.edu, monnier@iro.umontreal.ca, Emacs-devel@gnu.org
Subject: Re: etc/HELLO markup etc.
Date: Sat, 29 Dec 2018 16:23:24 +0900 [thread overview]
Message-ID: <87wons6bkj.fsf@gnu.org> (raw)
In-Reply-To: <838t0iasju.fsf@gnu.org> (message from Eli Zaretskii on Sat, 22 Dec 2018 10:12:37 +0200)
In article <838t0iasju.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
> > Eli Zaretskii wrote:
> > > Which markup is not necessary for display, in your opinion?
> >
> > At most all that's useful is markup that distinguishes Chinese and Japanese
> > variants of Han characters; this might also include hanja (Korean) and Chữ Nôm
> > (Vietnamese) variants if we ever added such characters to etc/HELLO. Such markup
> > might be useful because a significant set of east Asian users dislike Unicode's
> > Han unification and prefer specific variants of Han characters. I'm not aware of
> > any other set of users who dislike unification in that way.
> I'm not yet sure this is only about Han unification. Using charsets
> for specifying fonts is a general feature in Emacs, which can be used
> to control which fonts are selected independently of what the OS
> facilities such as fontconfig do.
> I hope Handa-san will be able to comment on this stuff.
> If Han unification is the only important user of the charset property,
> then yes, we could remove the rest of the charset info from HELLO.
Long ago, the quality of fonts designed for a specific regacy charset
were far better than so-called Unicode fonts even for non-Han charaters.
So, the charset information for non-Han charsets did have some meaning.
But, I don't know the current situation. Perhaps, it is good to remove
them and wait for complaint from users.
---
K. Handa
handa@gnu.org
next prev parent reply other threads:[~2018-12-29 7:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3fd27fe5-e650-b207-fdd4-36f805b89b4d@cs.ucla.edu>
[not found] ` <83bm5hcroa.fsf@gnu.org>
[not found] ` <9f33127d-f01b-b138-7a0c-ffeac7b77938@cs.ucla.edu>
[not found] ` <835zvochdj.fsf@gnu.org>
[not found] ` <5f113128-36c9-30c6-3413-8dc36051e058@cs.ucla.edu>
[not found] ` <83va3nban3.fsf@gnu.org>
2018-12-21 21:07 ` 27.0.50; Use utf-8 is all our Elisp files Paul Eggert
2018-12-22 1:19 ` Eric Lindblad
2018-12-22 7:56 ` etc/HELLO markup etc. (Was: 27.0.50; Use utf-8 is all our Elisp files) Eli Zaretskii
2018-12-22 8:12 ` etc/HELLO markup etc Eli Zaretskii
2018-12-22 19:41 ` Paul Eggert
2018-12-22 20:42 ` Eli Zaretskii
2018-12-23 7:47 ` Yuri Khan
2018-12-23 15:42 ` Eli Zaretskii
2018-12-23 15:53 ` Werner LEMBERG
2018-12-23 16:04 ` Eli Zaretskii
2018-12-23 21:11 ` Werner LEMBERG
2018-12-28 7:10 ` Eli Zaretskii
2018-12-29 7:23 ` handa [this message]
2018-12-29 7:37 ` Eli Zaretskii
2019-01-06 12:06 ` handa
2019-01-06 15:29 ` Eli Zaretskii
2019-01-06 17:26 ` Stefan Monnier
2019-01-06 17:39 ` Eli Zaretskii
2019-01-06 18:08 ` Stefan Monnier
2018-12-29 5:32 Van L
2018-12-29 7:33 ` Eli Zaretskii
2018-12-30 6:51 ` Van L
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=87wons6bkj.fsf@gnu.org \
--to=handa@gnu.org \
--cc=Emacs-devel@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@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).