all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Benjamin Riefenstahl <b.riefenstahl@turtle-trading.net>
To: Mark David <mhd@yv.org>
Cc: 21846@debbugs.gnu.org
Subject: bug#21846: 25.0.50; emacs hebrew script bidi nikud rendering bug
Date: Mon, 30 Nov 2015 18:22:07 +0100	[thread overview]
Message-ID: <87two3l7wg.fsf@justinian.turtle-trading.net> (raw)
In-Reply-To: <3F7EF7A4-689A-41E9-88A4-5028AD420087@yv.org> (Mark David's message of "Sun, 29 Nov 2015 17:59:19 -0500")

Mark David writes:
> The nikud placement is good to excellent in the fonts tried so far.

Thank you for confirming that.

> However, I tried a few more, and found one that's terrible: Aharoni
>
> This font seems to systematically misplace not all but most base char
> + nikud combinations in my sample file.  (Screen shot attached.)  Any
> way to fix this?

When I install this from the package manager, I get a PostScript font,
not a TrueType font (you can verify that yourself with "fc-list 'Aharoni
CLM' file").  I don't know how PostScript fonts are handled by Emacs.
But, not surprisingly, it does not go through the FLT file that we have
been hacking on so far.

Note that AFAIK, PostScript fonts do not have the kind of metadata that
is needed for positioning individual glyphs as OpenType has, so all the
functionality comes from code.  Still, Harfbuzz can do it, so in
principle, Emacs can, too.  ;-)





  reply	other threads:[~2015-11-30 17:22 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-06 22:29 bug#21846: 25.0.50; emacs hebrew script bidi nikud rendering bug Mark H. David
2015-11-07  0:12 ` bug#21846: Additional Info re: bug#21846 (25.0.50; emacs hebrew script bidi nikud rendering bug) Mark David
2015-11-07  8:59 ` bug#21846: 25.0.50; emacs hebrew script bidi nikud rendering bug Eli Zaretskii
2015-11-08  0:49   ` Mark David
2015-11-07 17:44 ` Benjamin Riefenstahl
2015-11-07 17:58   ` Eli Zaretskii
2015-11-07 19:24     ` Benjamin Riefenstahl
2015-11-08  0:56       ` Mark David
2015-11-08 16:21         ` Benjamin Riefenstahl
2015-11-28 19:33       ` Benjamin Riefenstahl
2015-11-29 22:59         ` Mark David
2015-11-30 17:22           ` Benjamin Riefenstahl [this message]
2015-11-30 23:02             ` Benjamin Riefenstahl
2015-12-01 14:52               ` Benjamin Riefenstahl
2015-12-10 23:15               ` Benjamin Riefenstahl
2015-12-11  2:36                 ` Mark H. David
2015-12-18 13:49                   ` K. Handa
2016-01-03 12:03                     ` K. Handa
2016-01-10 20:21                       ` Mark H. David
2016-01-12 16:38                       ` Benjamin Riefenstahl
2016-01-22 12:46                         ` K. Handa
2016-01-22 13:46                           ` Eli Zaretskii
2016-03-18 15:56                       ` Wolfgang Jenkner
2016-03-21 14:56                         ` handa
2016-03-21 19:05                           ` Wolfgang Jenkner
2016-03-25  9:42                             ` Eli Zaretskii
2016-03-25 10:01                               ` Mark H. David
2016-03-27 11:51                                 ` handa
2015-12-05 12:55             ` K. Handa
2015-12-06 18:28               ` Mark David
2015-12-07  3:05                 ` Richard Stallman
2015-12-07 13:45                 ` K. Handa
2015-12-07 16:24               ` Benjamin Riefenstahl

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=87two3l7wg.fsf@justinian.turtle-trading.net \
    --to=b.riefenstahl@turtle-trading.net \
    --cc=21846@debbugs.gnu.org \
    --cc=mhd@yv.org \
    /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.