From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 20222@debbugs.gnu.org, schwab@linux-m68k.org, orivej@gmx.fr
Subject: bug#20222: 25.0.50; Wrong horizontal position of combining characters
Date: Wed, 15 Jan 2020 18:21:28 +0200 [thread overview]
Message-ID: <83o8v44rnb.fsf@gnu.org> (raw)
In-Reply-To: <87eew1fg6c.fsf@marxist.se> (message from Stefan Kangas on Wed, 15 Jan 2020 06:21:31 +0100)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Wed, 15 Jan 2020 06:21:31 +0100
> Cc: 20222@debbugs.gnu.org, Andreas Schwab <schwab@linux-m68k.org>
>
> Orivej Desh <orivej@gmx.fr> writes:
>
> >> > --with-xft --without-libotf --without-m17n-flt --with-x-toolkit=gtk2
> >>
> >> What happens if you build with libotf?
> >
> > Thanks! I rebuilt Emacs with m17n and libotf, and now Ezra SIL and Linux
> > Libertine look perfect. (But only if multiple composing characters are
> > entered in some order that seems logical: 05E9 shin + 05C2 sin dot +
> > 05B9 holam compose into one character, yet shin + holam does not compose
> > with the following sin dot.) Cardo font, on the other hand, became even
> > more broken, with more composing characters shifted to the right. (I
> > think it was m17n that helped, because only Linux Libertine is available
> > in OTF, and also rendering of TTF variant of Linux Libertine got fixed.)
>
> It seems to me that the original issue is solved by building with
> libotf. Is there anything more to do here? If I don't hear anything
> else within a couple of weeks, I'll assume this is fixed and close the
> bug.
I think this bug doesn't exist with HarfBuzz, because it can handle
these in any order.
next prev parent reply other threads:[~2020-01-15 16:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-29 6:35 bug#20222: 25.0.50; Wrong horizontal position of combining characters Orivej Desh
2015-03-29 8:01 ` Andreas Schwab
2015-03-29 14:28 ` Orivej Desh
2020-01-15 5:21 ` Stefan Kangas
2020-01-15 16:21 ` Eli Zaretskii [this message]
2020-01-15 18:04 ` Stefan Kangas
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=83o8v44rnb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=20222@debbugs.gnu.org \
--cc=orivej@gmx.fr \
--cc=schwab@linux-m68k.org \
--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 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.