From: Po Lu <luangruo@yahoo.com>
To: Pip Cet <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: Fri, 09 Aug 2024 21:10:38 +0800 [thread overview]
Message-ID: <87bk21n8oh.fsf@yahoo.com> (raw)
In-Reply-To: <87ed6xswo2.fsf@protonmail.com> (Pip Cet's message of "Fri, 09 Aug 2024 12:33:37 +0000")
Pip Cet <pipcet@protonmail.com> writes:
>> https://github.com/adobe-fonts/source-han-sans
>
>> and its binaries are generated from the same source code by ADFKO
>> (though I am surprised to learn that this source is not in UFO format).
>
> I don't think it's the "source" at all. It's an intermediate binary,
> produced by a proprietary tool (as Adobe states), probably from a
> similarly proprietary, actual source format.
>
> Anyway, as for technical issues, the Type 1 font in the Source Han Sans
> CID is clearly closer to the source than the TrueType fonts are. Thus,
> there is some quality degradation when I, or when Google, generates a
> TrueType font from it.
Be that as it may, there is no perceptible difference between the two,
if hinting is disabled for the OTF original.
At all events, I do invite interested persons to undertake implementing
support for OTF font files in a manner that does not require Freetype,
Fontconfig, or further dependencies. This might be feasible (so far as
Noto and other outline fonts are concerned) without also supporting
color glyphs.
next prev parent reply other threads:[~2024-08-09 13:10 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
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 [this message]
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=87bk21n8oh.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).