ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Arthur Reutenauer <arthur.reutenauer@normalesup.org>
To: Mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: Re: Adobe Garamond Problems with letter combination "fi"
Date: Tue, 30 Apr 2013 13:28:20 +0100	[thread overview]
Message-ID: <20130430122820.GA9392@phare.normalesup.org> (raw)
In-Reply-To: <517AFF4C.5090709@wxs.nl>

> thinking of it: one reason why a general purpose word processor used
> by people with no idea about things like ligatures, is that
> ligatures are language dependent

  I don't think that's necessary relevant: the only example I can think
of language-dependent ligatures is fi and ffi for Turkish and other
languages that use the dotless i (ı, U+0131), because removing the dot
on the i would be confusing in that case; but that's really all.  All
other ligatures depend on the font.

  Many Adobe-produced fonts have a special ligatures for Turkish and
some other languages using ı, I suspect because Adobe Font Development
Kit for OpenType has a provision for them.

	Arthur
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2013-04-30 12:28 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-24  8:39 "H. Özoguz"
2013-04-24  8:51 ` Wolfgang Schuster
2013-04-25  6:20   ` Keith J. Schultz
2013-04-25  6:56     ` Thomas A. Schmitz
2013-04-26  7:41       ` Keith J. Schultz
2013-04-26  8:18         ` Hans Hagen
2013-04-26  8:20         ` Khaled Hosny
2013-04-26 12:12           ` Keith J. Schultz
2013-04-26 12:54             ` Hans Hagen
2013-04-26 18:27             ` Khaled Hosny
2013-04-26 19:57               ` Keith J. Schultz
2013-04-26 21:48                 ` Mojca Miklavec
2013-04-26 22:16                   ` Hans Hagen
2013-04-26 22:49                     ` Khaled Hosny
2013-04-27  6:47                     ` Schmitz Thomas A.
2013-04-27 11:58                     ` Mojca Miklavec
2013-04-26 16:43         ` Thomas A. Schmitz
2013-04-26 20:05           ` Keith J. Schultz
2013-04-26 20:17             ` Thomas A. Schmitz
2013-04-26 22:27               ` Hans Hagen
2013-04-30 12:28                 ` Arthur Reutenauer [this message]
2013-04-30 13:32                   ` Khaled Hosny
2013-05-01 11:31                     ` Arthur Reutenauer
2013-04-30 12:29               ` Arthur Reutenauer
2013-04-26 20:05           ` Idris Samawi Hamid ادريس   سماوي حامد
2013-04-24  9:00 ` Peter Münster
2013-04-24  9:09   ` Wolfgang Schuster
2013-04-24  9:04 "H. Özoguz"

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=20130430122820.GA9392@phare.normalesup.org \
    --to=arthur.reutenauer@normalesup.org \
    --cc=ntg-context@ntg.nl \
    --cc=thomas.schmitz@uni-bonn.de \
    /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.
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 NNTP newsgroup(s).