From: Yuri D'Elia <wavexx@thregr.org>
To: help-gnu-emacs@gnu.org
Subject: Re: otf ligature rendering support?
Date: Sat, 03 Jan 2015 11:44:25 +0100 [thread overview]
Message-ID: <m88h69$hgr$1@ger.gmane.org> (raw)
In-Reply-To: <83ppax9ndy.fsf@gnu.org>
On 01/02/2015 05:07 PM, Eli Zaretskii wrote:
>> From: Yuri D'Elia <wavexx@thregr.org>
>> Date: Fri, 02 Jan 2015 17:00:31 +0100
>>
>>> I think you need to define rules for composing characters into
>>> ligatures, in order to have what you want.
>>
>> This is different than composition of unicode ligatures.
>> OTF ligatures are an inherent property of the font along with kerning
>> tables.
>
> I'm probably missing something, and I'm certainly not an expert on OTF
> fonts, in Emacs or elsewhere. But if what you want is display several
> characters as a single glyph, the way to do that in Emacs is define
> composition rules.
Composition generates at most a sequence of precomposed utf code points,
such as æ. This is done at the client level and is font-agnostic.
OTF ligatures instead are glypt replacement tables which are provided
for a sequence of characters in the font itself. This is mostly needed
to improve the rendering for languages such as arabic.
The issue is that it needs special support in the client, since
previously drawn glypts might change as a result of typing.
I was under the impression that ligatures were supported by looking at
`fontset.el'.
next prev parent reply other threads:[~2015-01-03 10:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-02 15:32 otf ligature rendering support? Yuri D'Elia
2015-01-02 15:45 ` Eli Zaretskii
2015-01-02 16:00 ` Yuri D'Elia
2015-01-02 16:07 ` Eli Zaretskii
2015-01-03 10:44 ` Yuri D'Elia [this message]
2015-01-03 11:22 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2015-01-02 15:25 Yuri D'Elia
2015-01-03 15:16 ` K. Handa
2015-01-03 16:38 ` Yuri D'Elia
2015-08-17 1:04 ` YAMAMOTO Mitsuharu
2015-08-17 4:17 ` Stefan Monnier
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='m88h69$hgr$1@ger.gmane.org' \
--to=wavexx@thregr.org \
--cc=help-gnu-emacs@gnu.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.