From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Amin Bandali <bandali@gnu.org>
Cc: Khaled Hosny <dr.khaled.hosny@gmail.com>,
Ebrahim Byagowi <ebraminio@gmail.com>,
Ken Brown <kbrown@cornell.edu>, Kenichi Handa <handa@gnu.org>,
Eric Abrahamsen <eric@ericabrahamsen.net>,
John Wiegley <johnw@gnu.org>,
Mohammad Nasirifar <far.nasiri.m@gmail.com>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>,
Behdad Esfahbod <behdad@behdad.org>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: Emacs text shaping using Harfbuzz
Date: Fri, 14 Dec 2018 14:40:57 +0000 [thread overview]
Message-ID: <87mup8gohy.fsf@tcd.ie> (raw)
In-Reply-To: <871s6lj59k.fsf@aminb.org> (Amin Bandali's message of "Thu, 13 Dec 2018 19:55:51 -0500")
Amin Bandali <bandali@gnu.org> writes:
> On 2018-12-13 3:23 PM, Eric Abrahamsen wrote:
>> Ken Brown <kbrown@cornell.edu> writes:
>>
>>> On 12/13/2018 10:39 AM, Eli Zaretskii wrote:
>>>> I'd like to encourage people who build Emacs on GNU/Linux to checkout
>>>> and build this branch and report any problems you see.
>>>
>>> It builds on Cygwin (both 32-bit and 64-bit) and appears to run fine. I tested
>>> by visiting etc/HELLO, and nothing jumped out at me on visual comparison with
>>> Emacs built from master.
>>
>> Likewise on arch linux. Thai and Chinese (the two languages I'm familiar
>> with) look just fine.
>>
>
> Same goes for Persian and English on my Parabola GNU/Linux-libre setup.
>
> I’d also like to thank everyone on both sides of this collaboration for
> working on this.
Sorry if this is getting annoying, but the harfbuzz branch builds on
Debian x86_64 GNU/Linux buster/sid and renders Greek just fine.
Thanks to everyone working on this.
--
Basil
next prev parent reply other threads:[~2018-12-14 14:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 15:39 Emacs text shaping using Harfbuzz Eli Zaretskii
2018-12-13 18:47 ` Paul Eggert
2018-12-13 19:31 ` Khaled Hosny
2018-12-13 19:48 ` Eli Zaretskii
2018-12-13 20:01 ` Eli Zaretskii
2018-12-13 20:23 ` Eli Zaretskii
2018-12-13 19:38 ` Kaushal Modi
2018-12-13 19:48 ` Paul Eggert
2018-12-13 19:55 ` Eli Zaretskii
2018-12-13 20:01 ` Kaushal Modi
2018-12-13 21:16 ` Richard Stallman
2018-12-13 21:43 ` Ken Brown
2018-12-13 23:23 ` Eric Abrahamsen
2018-12-14 0:55 ` Amin Bandali
2018-12-14 7:41 ` Eli Zaretskii
2018-12-14 14:40 ` Basil L. Contovounesios [this message]
2018-12-14 14:55 ` Eli Zaretskii
2018-12-14 7:40 ` Eli Zaretskii
2018-12-14 7:35 ` Eli Zaretskii
2018-12-14 1:11 ` Florian Beck
2018-12-14 2:35 ` Kaushal Modi
2018-12-14 7:46 ` Eli Zaretskii
2018-12-15 0:49 ` Paul Eggert
2018-12-16 14:09 ` Benjamin Riefenstahl
2018-12-16 15:27 ` Eli Zaretskii
2018-12-16 17:27 ` Mike Kupfer
2018-12-16 17:30 ` 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=87mup8gohy.fsf@tcd.ie \
--to=contovob@tcd.ie \
--cc=bandali@gnu.org \
--cc=behdad@behdad.org \
--cc=dr.khaled.hosny@gmail.com \
--cc=ebraminio@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=far.nasiri.m@gmail.com \
--cc=handa@gnu.org \
--cc=johnw@gnu.org \
--cc=kbrown@cornell.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 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).