unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: rpluim@gmail.com, ola.nilsson@gmail.com, 38442@debbugs.gnu.org
Subject: bug#38442: 27.0.50; segmentation fault switching to cairo
Date: Mon, 02 Dec 2019 22:26:25 +0200	[thread overview]
Message-ID: <835ziylbim.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0STFLhgJs1p2tB_fwaXCF+Xv4+eGc=B=SBYNsiMDzcwOOw@mail.gmail.com> (message from Juanma Barranquero on Mon, 2 Dec 2019 19:08:13 +0100)

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Mon, 2 Dec 2019 19:08:13 +0100
> Cc: rpluim@gmail.com, ola.nilsson@gmail.com, 38442@debbugs.gnu.org
> 
> > Every font that can use Uniscribe can also use HarfBuzz.  So this is
> > not a problem, and users have no reason to wish to use Uniscribe when
> > they restore their sessions.
> 
> That's an argument to remove support for Uniscribe. I imagine that, if we
> haven't done that, it's likely because there could be some problematic
> font that would behave better with Uniscribe than Harfbuzz, isn't it?

Something like that.  Basically, we didn't remove any backend on any
platform in Emacs 27 yet, as this is the first release which uses
HarfBuzz.  It's an insurance policy.

(Uniscribe in particular was deprecated by MS, so we will have to drop
it sooner or later, because at some point it will no longer come with
Windows.)

> All in all, I think I would prefer to keep font-backend and filter it out
> on restoring when/if necessary; but I don't have a compelling use case,
> so I'll just filter it out entirely. We can always change it later if the
> need arises.
> 
> I'll commit it ASAP.

Thanks.





      parent reply	other threads:[~2019-12-02 20:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-30 23:03 bug#38442: 27.0.50; segmentation fault switching to cairo Ola Nilsson
2019-12-01  3:38 ` Eli Zaretskii
2019-12-01 17:28   ` Eli Zaretskii
2019-12-01 23:55     ` Juanma Barranquero
2019-12-02  7:54       ` Robert Pluim
2019-12-02  8:08         ` Juanma Barranquero
2019-12-02  8:36           ` Eli Zaretskii
2019-12-02 12:57             ` Juanma Barranquero
2019-12-02 16:09               ` Eli Zaretskii
2019-12-02 17:28                 ` Juanma Barranquero
2019-12-02 17:48                   ` Eli Zaretskii
2019-12-02 18:08                     ` Juanma Barranquero
2019-12-02 18:21                       ` Juanma Barranquero
2019-12-02 20:27                         ` Eli Zaretskii
2019-12-02 20:36                           ` Juanma Barranquero
2019-12-04 20:32                             ` Ola Nilsson
2019-12-05  3:30                               ` Eli Zaretskii
2019-12-02 20:26                       ` Eli Zaretskii [this message]

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=835ziylbim.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=38442@debbugs.gnu.org \
    --cc=lekktu@gmail.com \
    --cc=ola.nilsson@gmail.com \
    --cc=rpluim@gmail.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).