From: Eli Zaretskii <eliz@gnu.org>
To: ynyaaa@gmail.com
Cc: 39482@debbugs.gnu.org
Subject: bug#39482: 26.3; set-fontset-font with emacs charset does not work correctly
Date: Sat, 08 Feb 2020 10:16:17 +0200 [thread overview]
Message-ID: <83imkhebou.fsf@gnu.org> (raw)
In-Reply-To: <86d0ap3j9y.fsf@gmail.com> (ynyaaa@gmail.com)
> From: ynyaaa@gmail.com
> Cc: 39482@debbugs.gnu.org
> Date: Sat, 08 Feb 2020 11:27:53 +0900
>
> I installed emacs-27.0.60-snapshot-emacs-27-2019-12-28-x86_64-installer.exe
> and tested the same form. It looks like there is no difference.
Are you using HarfBuzz? I don't know if the installer installs the
HarfBuzz library by default. If the library is not installed, Emacs
will fall back on Uniscribe, and you have the same problems as in
Emacs 26 again. "C-u C-x =" on some character should tell you if
HarfBuzz or Uniscribe is being used.
> >> (kr-spec '("BatangChe" . "ksc5601.1987"))
>
> Replacing "ksc5601.1987" with "ksc5601.1987-0" makes most of
> 'korean-ksc5601 characters displayed with BatangChe font.
> (Some characters are displayed with SimHei.)
>
> I think "ksc5601", "ksc5601*" or "ksc5601.1987" should be accepted.
IME, font families are not supported well on MS-Windows, and font
registry is an XLFD notion supported natively on X Windows that I
wouldn't be surprised if is not well supported on Windows, either.
That said, people who have enough time on their hands are welcome to
dig into the font/fontset support code on MS-Windows and suggest
patches to improve that.
next prev parent reply other threads:[~2020-02-08 8:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 15:11 bug#39482: 26.3; set-fontset-font with emacs charset does not work correctly ynyaaa
2020-02-07 16:04 ` Eli Zaretskii
2020-02-08 2:27 ` ynyaaa
2020-02-08 8:16 ` Eli Zaretskii [this message]
2020-02-08 10:50 ` ynyaaa
2020-02-08 11:36 ` Eli Zaretskii
2020-02-08 14:20 ` ynyaaa
2020-02-08 15:06 ` Eli Zaretskii
2022-02-02 18:26 ` Lars Ingebrigtsen
2022-03-03 21:38 ` Lars Ingebrigtsen
2020-02-09 17:19 ` 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=83imkhebou.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39482@debbugs.gnu.org \
--cc=ynyaaa@gmail.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 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).