From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Kenichi Handa <handa@gnu.org>
Cc: toomim@cs.washington.edu, 15138@debbugs.gnu.org
Subject: bug#15138: Font selection error on OSX
Date: Mon, 2 Sep 2013 17:57:14 +0200 [thread overview]
Message-ID: <2ADB2AAF-31B8-4271-B4C4-6A26EDFB5858@swipnet.se> (raw)
In-Reply-To: <87r4d7i8gt.fsf@gnu.org>
Hello.
2 sep 2013 kl. 16:50 skrev Kenichi Handa <handa@gnu.org>:
> In article <B1058569-FA76-4B76-84DF-46A38916008F@swipnet.se>, Jan Djärv <jan.h.d@swipnet.se> writes:
>
>> I've made a fix for this in the trunk, please try it.
>
> Do you mean this change?
>
> * fontset.c (face_for_char): Check char in the current face font first
> if HAVE_NS (Bug#15138).
>
> I agree that this change improves font selection for
> symbols, but it's not good for many scripts for which just
> having a glyph is not enough. For instance, if the default
> font has Hindi glyphs but doesn't have the OTF features for
> Hindi script, we must find another proper font for Hindi.
>
> How about modifying the current fontset mechanism as this?
>
> (1) Allow t for FONT-SPEC of set-fontset-font to tell that
> the default font should be tried.
> (2) Modiyf the default fontset to include `t' as the
> font-spec for scripts/characters for which the default
> font is ok.
libotf is genrelly not available on OSX, and probably not working with GNUStep either (unless they use it at a lower level). So the OTF case is not relevant to HAVE_NS anyway.
For OSX the way to go is to use Core text for this. I think GNUStep is looking at implementing Core text to replace their old display postscript implementation. So this is basically a temporary fix. Anyway, if you prefer OTF for some script, why not mark those scripts with "prefer-otf" and check if any otf-features are available? HAVE_NS will not have any OTF features.
Jan D.
next prev parent reply other threads:[~2013-09-02 15:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 2:37 bug#15138: Font rendering error on OSX Michael Toomim
2013-08-20 2:44 ` Michael Toomim
2013-08-26 16:14 ` Jan Djärv
2013-08-27 15:59 ` bug#15138: Font selection " Jan Djärv
2013-08-27 19:08 ` Michael Toomim
2013-08-28 4:55 ` Jan Djärv
2013-09-01 10:00 ` Jan Djärv
2013-09-01 18:51 ` Michael Toomim
2013-09-02 14:50 ` Kenichi Handa
2013-09-02 15:57 ` Jan Djärv [this message]
2013-09-03 12:10 ` Kenichi Handa
2013-09-03 15:26 ` Jan Djärv
2013-09-05 12:57 ` Kenichi Handa
2013-09-05 16:56 ` Jan Djärv
2013-09-02 18:34 ` Michael Toomim
2013-09-02 19:13 ` Jan Djärv
2013-09-02 17:29 ` bug#15138: revno: 114089 change causes cjk characters not shown correctly Darren Hoo
2013-09-03 7:00 ` Jan Djärv
2013-09-03 14:37 ` Darren Hoo
2013-09-03 15:18 ` Jan Djärv
2013-09-05 13:49 ` Kenichi Handa
2013-09-05 16:34 ` Jan Djärv
2013-09-05 17:04 ` Stefan Monnier
2013-09-05 17:25 ` Jan Djärv
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2ADB2AAF-31B8-4271-B4C4-6A26EDFB5858@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=15138@debbugs.gnu.org \
--cc=handa@gnu.org \
--cc=toomim@cs.washington.edu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.