From: Po Lu <luangruo@yahoo.com>
To: pipcet@protonmail.com
Cc: Benjamin Riefenstahl <b.riefenstahl@turtle-trading.net>,
Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org
Subject: Re: master bf0aeaa0d7a: Re-enable displaying `han' characters on Android
Date: Sat, 03 Aug 2024 22:54:56 +0800 [thread overview]
Message-ID: <s54ikwhvepr.fsf@yahoo.com> (raw)
In-Reply-To: <87o769wue4.fsf@protonmail.com> (pipcet@protonmail.com's message of "Sat, 03 Aug 2024 14:31:02 +0000")
pipcet@protonmail.com writes:
> Thanks! So supporting these fonts on Android using the sfnt driver is
> very hard, correct?
Yes, it would amount to writing a new font driver.
> The androidfont.c fallback driver appears to support them, but I
> understand that's not a good option either. (I tried
> (set-frame-parameter nil 'font-backend "android") and the difference
> in a C-h h buffer was quite noticeable).
Correct.
> In any case, asking users to install an extra font only to see basic
> CJK glyphs can't be a long-term solution, can it?
Till someone implements the aforesaid new font driver, why not? The
font is installed once, and that is the end of the matter, and
ultimately it is the same font that would ideally be loaded from
/system/fonts, with no degredation in quality.
next prev parent reply other threads:[~2024-08-03 14:54 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 15:45 master bf0aeaa0d7a: Re-enable displaying `han' characters on Android Eli Zaretskii
2024-08-01 0:07 ` Po Lu
2024-08-01 0:33 ` Po Lu
2024-08-01 5:52 ` Eli Zaretskii
2024-08-01 7:55 ` Po Lu
2024-08-01 8:52 ` Eli Zaretskii
2024-08-01 9:47 ` Po Lu
2024-08-01 9:56 ` Eli Zaretskii
2024-08-01 10:13 ` Po Lu
2024-08-01 10:19 ` Eli Zaretskii
2024-08-01 21:17 ` Dmitry Gutov
2024-08-01 5:32 ` Eli Zaretskii
2024-08-01 8:16 ` Po Lu
2024-08-01 9:49 ` Eli Zaretskii
2024-08-01 10:30 ` Po Lu
2024-08-01 10:35 ` Eli Zaretskii
2024-08-02 10:52 ` Benjamin Riefenstahl
2024-08-02 12:29 ` Eli Zaretskii
2024-08-02 12:55 ` Benjamin Riefenstahl
2024-08-02 13:13 ` Benjamin Riefenstahl
2024-08-03 7:12 ` pipcet
2024-08-03 8:52 ` Po Lu
2024-08-03 9:21 ` pipcet
2024-08-03 9:33 ` Po Lu
2024-08-03 13:13 ` pipcet
2024-08-03 13:31 ` Po Lu
2024-08-03 14:31 ` pipcet
2024-08-03 14:54 ` Po Lu [this message]
2024-08-07 17:52 ` Pip Cet
2024-08-08 0:10 ` Po Lu
2024-08-09 12:33 ` Pip Cet
2024-08-09 13:10 ` Po Lu
2024-08-03 15:15 ` Eli Zaretskii
2024-08-02 10:44 ` Benjamin Riefenstahl
2024-08-02 11:42 ` Po Lu
2024-08-01 7:57 ` Andrea Corallo
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=s54ikwhvepr.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=b.riefenstahl@turtle-trading.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=pipcet@protonmail.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).