From: "Keith J. Schultz" <keithjschultz@web.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Adobe Garamond Problems with letter combination "fi"
Date: Fri, 26 Apr 2013 22:05:25 +0200 [thread overview]
Message-ID: <60743B9E-1882-42E0-9C34-BF999393695F@web.de> (raw)
In-Reply-To: <517AAECF.1050902@uni-bonn.de>
Am 26.04.2013 um 18:43 schrieb "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>:
>
> Hi Keith,
>
> 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.
>
> As to LaTeX: you're wrong, LaTeX is part of the TeX family as is ConTeXt and has ligatures. If you set up your fonts correctly in XeLaTeX, you get them.
>
Hi Thomas,
I never said that they do not have ligatures. I never said XeLaTeX does not have
the ability to use them I have read the fontspec manual!
What I do not understand is why you rant to me about Words inabilities! I never mentioned
before you did!!
It is a shame that when one states an opinion that others dislike or do not agree with one
is pushed into a corner which had absolutely nothing to do with one post.
For me this discussion has gone far enough.
regards
Keith
___________________________________________________________________________________
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 [this message]
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=60743B9E-1882-42E0-9C34-BF999393695F@web.de \
--to=keithjschultz@web.de \
--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).