From: "Idris Samawi Hamid ادريس سماوي حامد" <ishamid@colostate.edu>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Adobe Garamond Problems with letter combination "fi"
Date: Fri, 26 Apr 2013 14:05:43 -0600 [thread overview]
Message-ID: <op.wv5zftiepw6hmh@ishamid-pc> (raw)
In-Reply-To: <517AAECF.1050902@uni-bonn.de>
Greetings, Keith, Thomas, and all,
On Fri, 26 Apr 2013 10:43:59 -0600, Thomas A. Schmitz
<thomas.schmitz@uni-bonn.de> wrote:
> if you look at the books of decent publishers, you will see that most of
> them still use ligatures (most American university presses, Oxford and
> Cambridge, German publishers such as Reclam etc.) However, many smaller
> publishers don't give a rat's ass about esthetics, and that's where Word
> comes into play: they have their authors deliver their manuscripts as
> Word files and simply typeset from that, more often than not by
> employing some underpaid and untrained "contractors" in India. Cuts
> costs and makes authors do all the work that publishers used to do in
> the olden days... Taking this as the norm is not a good idea.
The situation Thomas is describing is analogous to what happened 40 years
ago: When metal-based typesetting started to die out, what came after was
atrocious but ubiquitous. And that's _exactly_ why Knuth invented TeX!
As a general rule: High-quality typesetting with good fonts and the
ligatures off is like pouring fine wine into a plastic cup.
Best wishes
Idris
--
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
___________________________________________________________________________________
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 20:05 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
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 ادريس سماوي حامد [this message]
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=op.wv5zftiepw6hmh@ishamid-pc \
--to=ishamid@colostate.edu \
--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).