From: Alan Third <alan@idiocy.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: Joost Kremers <joostkremers@fastmail.fm>,
John Wiegley <jwiegley@gmail.com>,
11075@debbugs.gnu.org
Subject: bug#11075: 24.0.94; Arabic character composition
Date: Sun, 22 Sep 2019 12:54:51 +0100 [thread overview]
Message-ID: <20190922115451.GA52669@breton.holly.idiocy.org> (raw)
In-Reply-To: <CADwFkm=xwDXuxpoEM7PTrhXZXAuC2r1_jLUQXwVxb4PaR0M_UA@mail.gmail.com>
On Sat, Sep 21, 2019 at 12:45:20AM +0200, Stefan Kangas wrote:
> Alan Third <alan@idiocy.org> writes:
>
> > On Mon, Sep 25, 2017 at 07:17:21AM -0700, John Wiegley wrote:
> >> >>>>> "AT" == Alan Third <alan@idiocy.org> writes:
> >>
> >> AT> Hi, does anyone know if this bug was resolved? I assume if it worked in
> >> AT> the Mac port it will now work in the NS port?
> >>
> >> Why can that assumption be made now?
> >
> > In the seven or eight years since this bug report was made, we
> > switched over to the mac port font backend.
>
> Since that was written, harfbuzz was enabled by default. And wouldn't
> that library have good support for this anyhow?
>
> > It might still be an issue on GNUstep, though. I think it still uses
> > nsfont.m.
>
> I'm not a GNUstep user so I can't easily test this.
>
> But would the recent harfbuzz support (enabled by default on GNUstep
> too, I assume) fix this? Do you know, Eli?
As I understand it Harfbuzz is not supported on the NS port at all. I
know that Yamamoto Mitsuharu wrote a proof of concept, but I don’t
believe it was ever finished.
--
Alan Third
next prev parent reply other threads:[~2019-09-22 11:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 15:44 bug#11075: 24.0.94; Arabic character composition Joost Kremers
2012-03-23 17:06 ` Eli Zaretskii
2012-03-23 18:23 ` Joost Kremers
2012-03-23 18:39 ` Eli Zaretskii
2012-03-27 14:33 ` Joost Kremers
2012-03-27 18:06 ` Eli Zaretskii
2012-04-03 2:27 ` Kenichi Handa
2012-04-03 9:12 ` Joost Kremers
2012-04-02 7:21 ` YAMAMOTO Mitsuharu
2012-04-02 7:44 ` Joost Kremers
2012-04-04 0:22 ` YAMAMOTO Mitsuharu
2017-09-25 14:01 ` Alan Third
2017-09-25 14:17 ` John Wiegley
2017-09-25 16:51 ` Alan Third
2019-09-20 22:45 ` Stefan Kangas
2019-09-21 6:35 ` Eli Zaretskii
2019-09-22 11:54 ` Alan Third [this message]
2019-09-22 20:23 ` mituharu
2019-09-23 18:40 ` Alan Third
2019-09-24 6:04 ` Eli Zaretskii
2019-09-27 21:39 ` Alan Third
2019-09-28 6:33 ` Eli Zaretskii
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=20190922115451.GA52669@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=11075@debbugs.gnu.org \
--cc=joostkremers@fastmail.fm \
--cc=jwiegley@gmail.com \
--cc=stefan@marxist.se \
/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).