From: Eli Zaretskii <eliz@gnu.org>
To: handa <handa@gnu.org>
Cc: 30193@debbugs.gnu.org
Subject: bug#30193: crash in libotf
Date: Fri, 26 Jan 2018 15:39:49 +0200 [thread overview]
Message-ID: <83mv10lowq.fsf@gnu.org> (raw)
In-Reply-To: <87zi50bytx.fsf@gnu.org> (message from handa on Fri, 26 Jan 2018 21:15:38 +0900)
> From: handa <handa@gnu.org>
> Cc: rgm@gnu.org, 30193@debbugs.gnu.org
> Date: Fri, 26 Jan 2018 21:15:38 +0900
>
> In article <83h8r9na0c.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
>
> > > 1. Check the version number of libotf in configure script.
> > > 2. Expose that version number to config.h.
> > > 3. In xfaces.c, if the version number is less than 0.9.16, initialize
> > > Vface_ignored_fonts to ("Noto Serif Kannada").
>
> > Why not just add that font to face-ignored-fonts by default?
>
> For those who build Emacs from source, isn't it better that they do not
> have to change Emacs when they build Emacs with the new version of
> libotf?
Why would they need ti change Emacs? Is Noto Serif Kannada so
important that we cannot reasonably handle the Kannada script without
it?
next prev parent reply other threads:[~2018-01-26 13:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-21 9:54 bug#30193: The deadliest file in Emacs history 積丹尼 Dan Jacobson
2018-01-21 16:23 ` Eli Zaretskii
2018-01-21 18:37 ` bug#30193: crash in libotf Glenn Morris
2018-01-23 14:30 ` handa
2018-01-24 3:31 ` Glenn Morris
2018-01-25 9:23 ` handa
2018-01-25 17:06 ` Eli Zaretskii
2018-01-26 12:15 ` handa
2018-01-26 13:39 ` Eli Zaretskii [this message]
2018-01-28 12:16 ` handa
2018-01-27 3:56 ` Glenn Morris
2018-01-28 11:57 ` handa
2018-01-21 16:38 ` bug#30193: The deadliest file in Emacs history 積丹尼 Dan Jacobson
2018-02-02 16:47 ` bug#30193: crash in libotf Glenn Morris
2018-02-12 23:25 ` handa
2018-03-05 22:50 ` bug#30193: iOS, Telugu character 積丹尼 Dan Jacobson
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=83mv10lowq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=30193@debbugs.gnu.org \
--cc=handa@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 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.