From: Byung-Hee HWANG <soyeomul@doraji.xyz>
To: emacs-devel@gnu.org
Subject: Re: Any new method to deal with Emacs Fonts settings puzzles nearly every Chinese emacser?
Date: Mon, 15 Nov 2021 16:20:44 +0900 [thread overview]
Message-ID: <874k8ddgvn.fsf@penguin> (raw)
In-Reply-To: <871r3j6ps2.fsf@yahoo.com> (Po Lu's message of "Sun, 14 Nov 2021 17:38:05 +0800")
Po Lu <luangruo@yahoo.com> writes:
> Werner LEMBERG <wl@gnu.org> writes:
>
>> Interesting. AFAIK, the CJKV glyphs are based on the 'Adobe Source'
>> family. Could you point out some of the problems? Or maybe do you
>> have links to bug reports? Normally, both the Adobe and Google font
>> folks are quite willing to fix such issues.
>
> I can't give specific examples right now, but I would be willing to
> switch to Noto CJK for a while and report any problems I see.
>
> But Noto CJK having disagreeable glyphs is a relatively well known piece
> of received wisdom around here, so someone else can probably chime in.
As Korean CJK user, i would like to add this thread as "star
mark". Personally Korean Hanja is not bad under Google Noto CJK.
"START: 한강 漢江 대한민국 大韓民國 -- This is Google Noto CJK"
attached as screenshot:
https://gitlab.com/soyeomul/Gnus/-/raw/86707860b5733ffa398683750a4bab01f79e1ffa/ss/google-noto-cjk-test.png
Sincerely, Gnus fan Byung-Hee
next prev parent reply other threads:[~2021-11-15 7:20 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-13 14:36 Any new method to deal with Emacs Fonts settings puzzles nearly every Chinese emacser? tumashu
2021-11-13 14:49 ` tumashu
2021-11-13 15:03 ` tumashu
2021-11-13 15:32 ` Any " Eli Zaretskii
2021-11-13 16:19 ` Feng Shu
2021-11-13 16:42 ` Eli Zaretskii
2021-11-13 19:35 ` Feng Shu
2021-11-13 20:03 ` Eli Zaretskii
2021-11-13 23:38 ` Feng Shu
2021-11-14 0:28 ` Eric Abrahamsen
2021-11-14 7:37 ` Eli Zaretskii
2021-11-14 7:51 ` Po Lu
2021-11-14 9:07 ` Werner LEMBERG
2021-11-14 9:38 ` Po Lu
2021-11-15 7:20 ` Byung-Hee HWANG [this message]
2021-11-14 7:31 ` Eli Zaretskii
2021-11-14 7:36 ` Po Lu
2021-11-14 8:09 ` Eli Zaretskii
2021-11-14 8:24 ` Feng Shu
2021-11-14 9:41 ` Po Lu
2021-11-14 11:33 ` Eli Zaretskii
2021-11-14 11:57 ` Po Lu
2021-11-15 0:36 ` tumashu
2021-11-15 0:48 ` tumashu
2021-11-15 12:43 ` Eli Zaretskii
2021-11-15 12:47 ` Po Lu
2021-11-15 13:55 ` Eli Zaretskii
2021-11-13 15:21 ` Eli Zaretskii
2021-11-13 16:04 ` Feng Shu
2021-11-13 16:12 ` Feng Shu
2021-11-13 16:36 ` Eli Zaretskii
2021-11-13 19:33 ` Feng Shu
2021-11-13 19:54 ` Feng Shu
2021-11-13 20:06 ` Eli Zaretskii
2021-11-13 23:31 ` Feng Shu
2021-11-14 6:48 ` Eli Zaretskii
2021-11-14 7:03 ` Feng Shu
2021-11-13 20:02 ` Eli Zaretskii
2021-11-13 23:29 ` Feng Shu
2021-11-13 23:14 ` Phil Sainty
2021-11-14 0:02 ` Feng Shu
2021-11-14 0:18 ` Feng Shu
2021-11-14 7:36 ` Eli Zaretskii
2021-11-14 7:54 ` Po Lu
2021-11-14 8:14 ` Eli Zaretskii
2021-11-14 9:43 ` Po Lu
2021-11-14 6:45 ` Eli Zaretskii
2021-11-14 7:17 ` Feng Shu
2021-11-14 8:00 ` Eli Zaretskii
2021-11-14 1:12 ` Po Lu
2021-11-14 1:52 ` Feng Shu
2021-11-14 7:55 ` Eli Zaretskii
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=874k8ddgvn.fsf@penguin \
--to=soyeomul@doraji.xyz \
--cc=emacs-devel@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).