From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Adobe Garamond Problems with letter combination "fi"
Date: Fri, 26 Apr 2013 23:48:46 +0200 [thread overview]
Message-ID: <CALBOmsbPEiMQvY2gWdpM7PgkW6YVoV8T0ugn56=G8kEYb-n13Q@mail.gmail.com> (raw)
In-Reply-To: <18482110-F93A-412C-B4A5-E8C5C7DE7EA9@web.de>
On Fri, Apr 26, 2013 at 9:57 PM, Keith J. Schultz wrote:
>
> to be honest I never noticed them when I was using LaTeX. It might have been
> the fonts.
Someone had to show me the first ligature years ago and when he did
that, I had to check every single book and document I had at hand to
check if ligatures were really commonly used. I simply couldn't
believe my eyes and the fact that it took me some 15 years of literacy
and a couple of years of using TeX without ever noticing any ligature
anywhere.
I consider this (the fact that one doesn't notice it) part of a good
design. It's similar with kerning: one doesn't notice it until/unless
it's bad. It's similar in the kitchen also. One doesn't notice that
there is salt in food unless there's too little or too much of it
present.
Mojca
PS: if you really hate the ligatures, you can try to help improve this
"interesting" package to handle ligatures (it probably has the most
potential in engines other than XeTeX/LuaTeX because it's a bit more
complicated to turn off the ligatures there):
http://www.ctan.org/tex-archive/macros/latex/contrib/serbian-lig
The package defines commands for all the words from a dictionary which
contain letters "fi", for example
\def\profit{prof\kern 0.03em it\xspace}
\def\Gadafi{Gadaf\kern 0.03em i\xspace}
% \stopsarcasm
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2013-04-26 21:48 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 [this message]
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
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='CALBOmsbPEiMQvY2gWdpM7PgkW6YVoV8T0ugn56=G8kEYb-n13Q@mail.gmail.com' \
--to=mojca.miklavec.lists@gmail.com \
--cc=ntg-context@ntg.nl \
/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).