unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Raoul Comninos <revrari@mweb.co.za>, 36171@debbugs.gnu.org
Subject: bug#36171: 25.1; Emacs displays Hebrew text incorrectly
Date: Thu, 13 Jun 2019 18:07:06 +0200	[thread overview]
Message-ID: <m2lfy51nbp.fsf@gmail.com> (raw)
In-Reply-To: <83o931zkyv.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 13 Jun 2019 16:14:00 +0300")

>>>>> On Thu, 13 Jun 2019 16:14:00 +0300, Eli Zaretskii <eliz@gnu.org> said:

    >> Cc: 36171@debbugs.gnu.org
    >> From: Raoul Comninos <revrari@mweb.co.za>
    >> Date: Thu, 13 Jun 2019 14:54:19 +0200
    >> 
    >> I am very pleased we are making progress. If we can get this right, it 
    >> is going to save me having to retype all the Hebrew! The text certainly 
    >> looks much better but the problem is not as yet fully resolved. There 
    >> remain circles in the text (see attachment).

    Eli> I don't see any such circles on my system.  I tried half a dozen
    Eli> different fonts, and they all work correctly.  How many fonts did you
    Eli> try?

I see circles on my GNU/Linux box, but only when using the xft font
backend, eg the second character from the left (visually) on the
'Aoristic perfect' line. If I put

(add-to-list 'default-frame-alist '(font-backend xfthb))

in my .emacs, then everything displays correctly. I thought HarfBuzz
was supposed to be preferred to xft?

Robert





  reply	other threads:[~2019-06-13 16:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11 15:11 bug#36171: 25.1; Emacs displays Hebrew text incorrectly Raoul Comninos
2019-06-11 16:29 ` Eli Zaretskii
     [not found]   ` <b36cb179-8481-1430-2576-db511b27d46b@mweb.co.za>
2019-06-12 16:23     ` Eli Zaretskii
2019-06-12 18:19       ` Raoul Comninos
2019-06-12 18:48         ` Eli Zaretskii
2019-06-12 19:11           ` Eli Zaretskii
2019-06-12 19:27           ` Raoul Comninos
2019-06-13  3:32             ` Eli Zaretskii
2019-06-13  8:53               ` Raoul Comninos
2019-06-13  9:44                 ` Eli Zaretskii
2019-06-13 12:54                   ` Raoul Comninos
2019-06-13 13:14                     ` Eli Zaretskii
2019-06-13 16:07                       ` Robert Pluim [this message]
2019-06-13 16:42                         ` Eli Zaretskii
2019-06-13 18:39                           ` Raoul Comninos
2019-06-13 18:57                             ` Eli Zaretskii
2019-06-14 11:51                               ` Raoul Comninos
2019-06-14 12:22                                 ` Eli Zaretskii
2019-06-14 14:40                                   ` Raoul Comninos
2019-06-18 18:00                                   ` Raoul Comninos
2019-06-18 18:09                                     ` Eli Zaretskii
     [not found]                       ` <ecfc571f-e6e5-6532-4152-796ec9d8d591@mweb.co.za>
2019-06-13 16:07                         ` 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=m2lfy51nbp.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=36171@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=revrari@mweb.co.za \
    /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).