all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: James Cloos <cloos@jhcloos.com>
Cc: emacs-devel@gnu.org
Subject: Re: How is a composition being done?
Date: Mon, 16 Aug 2010 16:22:51 +0900	[thread overview]
Message-ID: <tl739uf2f90.fsf@m17n.org> (raw)
In-Reply-To: <m3tymyhgfc.fsf@carbon.jhcloos.org> (message from James Cloos on Fri, 13 Aug 2010 07:58:55 -0400)

In article <m3tymyhgfc.fsf@carbon.jhcloos.org>, James Cloos <cloos@jhcloos.com> writes:

> f-ligs are the lugatures which start with a miniscule f.  The most
> common ones are fi, fl, ff, ffi, ffl; some fonts have fj; some even
> have ligatures like fb, fk or ft which are only found at syllable
> boundries.

Ah, I see.

>>> I'd like to see emacs use f-ligs when in variable pitch mode.

>>> My guess is that a function which applies the GSUB liga feature would be
>>> the right solution, since monowidth fonts usualy avoid that.

KH> Yes, I think so.  But, for that, we must at first implement
KH> a function to apply specific OpenType features.

> Yes, that would be ideal.

> Perhaps the faces could specify which features should be applied, just
> like they currently specify styles.  The default set could be those
> which are generally applied by opentype-aware programs for the given
> scripts.

> I would also be useful to have a way to add features for a given span
> of text.  Perahps overlays could be used (abused?) for that?

If we make face to specify such features, we can naturally
use text property and/or overlay because both of them can
have `face' property.

---
Kenichi Handa
handa@m17n.org



      reply	other threads:[~2010-08-16  7:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-09 18:29 How is a composition being done? Yair F
2010-08-10  1:13 ` Kenichi Handa
2010-08-10 11:52   ` James Cloos
2010-08-12  6:25     ` Kenichi Handa
2010-08-13 11:58       ` James Cloos
2010-08-16  7:22         ` Kenichi Handa [this message]

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=tl739uf2f90.fsf@m17n.org \
    --to=handa@m17n.org \
    --cc=cloos@jhcloos.com \
    --cc=emacs-devel@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.