From: ynyaaa@gmail.com
To: Eli Zaretskii <eliz@gnu.org>
Cc: 33019@debbugs.gnu.org
Subject: bug#33019: 26.1; can not set fontset as frame font by set-frame-font
Date: Sat, 13 Oct 2018 19:38:00 +0900 [thread overview]
Message-ID: <86k1mmrv1z.fsf@gmail.com> (raw)
In-Reply-To: <831s8uwfwl.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 13 Oct 2018 08:54:02 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> When a font family is specified for some range of "fontset-default",
>> :family specification of text face is ignored in the range.
>
> So the problem is not the fontset but displaying faces defined using
> :family, is that right?
It may be an alternative solution.
>> (insert (propertize "ABC" 'face '(:family "Noto Serif")))
>> shows characters with "Noto Serif".
>>
>> (progn (set-fontset-font "fontset-default" '(#x4E00 . #x9FFF)
>> "Noto Sans CJK JP Regular")
>> (insert (propertize "\x4E00" 'face '(:family "Noto Serif CJK JP"))))
>> shows the character with "Noto Sans CJK JP Regular",
>> not "Noto Serif CJK JP".
>
> Why do you define this range of characters to use Noto Sans if you
> actually want to see it in Noto Serif? And in any case, why do use
> :family instead of specific font in the face definition?
I want to display some web pages partially with serif fonts.
Also I want to display chinese language text with "Noto Serif CJK SC"
or "Noto Serif CJK TC".
next prev parent reply other threads:[~2018-10-13 10:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 15:04 bug#33019: 26.1; can not set fontset as frame font by set-frame-font ynyaaa
2018-10-12 6:46 ` Eli Zaretskii
2018-10-12 18:53 ` ynyaaa
2018-10-12 19:51 ` Eli Zaretskii
2018-10-13 1:00 ` ynyaaa
2018-10-13 5:54 ` Eli Zaretskii
2018-10-13 10:38 ` ynyaaa [this message]
2018-10-13 10:53 ` Eli Zaretskii
2018-10-13 11:23 ` ynyaaa
2018-10-13 12:00 ` Eli Zaretskii
2018-10-13 13:12 ` ynyaaa
2018-10-13 13:20 ` Eli Zaretskii
2018-10-13 14:43 ` ynyaaa
2018-10-15 16:16 ` Eli Zaretskii
2022-02-21 14:57 ` Lars Ingebrigtsen
2022-02-21 15:24 ` 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=86k1mmrv1z.fsf@gmail.com \
--to=ynyaaa@gmail.com \
--cc=33019@debbugs.gnu.org \
--cc=eliz@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).