ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "John R. Culleton" <john@wexfordpress.com>
Cc: Jerzy.Ludwichowski@uni.torun.pl, Hans Hagen <pragma@wxs.nl>,
	v.r.w.Schaa@gsi.de, Staszek Wawrykiewicz <staw@gust.org.pl>,
	Karl Berry <karl@freefriends.org>
Subject: Re: Fleurons
Date: Thu, 2 Jun 2005 07:39:19 +0000	[thread overview]
Message-ID: <200506020739.20228.john@wexfordpress.com> (raw)
In-Reply-To: <429E4A65.5050206@wxs.nl>

On Wednesday 01 June 2005 11:53 pm, Hans Hagen wrote:
> Staszek Wawrykiewicz wrote:
> > Why? Anybody is free to make tfm files, as afm files are
> > always available for _that_ set of urw fonts.
>
> the problem is that there is a bunch of context users out there
> who think (are being told, whatever) that they should use the
> provided ones instead of generating them by texfont or afm2tfm
> (so they want to use the presumably present ones and not
> generate them by texfont, which is ok for me; but unfortunately
> they are not always there; and then they try the ps ones, which
> are only there for ec and not for texnansi and then ... and
> then ...)
>
> well, i give up on fonts ... maybe some day i just put metric
> files in the context zip (ec texnansi qx), why should i care
> about those few extra bytes
>

I use only the 8r encoding because I write/typeset in (American)
English and I need special characters like the copyright symbol.
the registered symbol, the trademark (tm) symbol and so on. Some
of these are not available in other encodings, or at least I
cannot find them. I understand that Europeans prefer other
encodings with good reason but 8r needs to remain in the scheme
of things IMO. 

I not only use plain tex, pdftex, Context etc. in my own work I
advertise these Open Source solutions as effective alternatives
to e.g., InDesign. To sell the system to new users requires a
K.I.S.S. approach. 

Is there a problem in Context with making the URW fonts the
default and then just aliasing the Adobe names to the URW versions?
The more we can hide these details the better. 

Font handling is the great Achilles heel of all flavors of TeX,
as we all know. Since Context is (relatively) new if we can
jigger things around so that the K.I.S.S. principle is adhered
to then selling the concept to new users will be easier. Too
many people in the printing world have horrid memories of LaTeX
from their college days or other earlier experience.

(K.I.S.S. = "Keep it simple silly.) 

> thanks for your patience

And thanks for Context!

-- 

John Culleton

  reply	other threads:[~2005-06-02  7:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-30 19:35 Fleurons Keith McKay
2005-05-30 21:52 ` Fleurons Hans Hagen
2005-05-30 23:39   ` Fleurons Adam Lindsay
2005-05-31  6:37     ` Fleurons Hans Hagen
2005-05-31  7:59       ` Fleurons Adam Lindsay
2005-05-31 10:14         ` Fleurons Hans Hagen
2005-05-31 11:15           ` Fleurons Adam Lindsay
2005-05-31 20:43           ` Fleurons Karl Berry
2005-06-01 21:27             ` Fleurons Staszek Wawrykiewicz
2005-06-01 22:10               ` Fleurons Hans Hagen
2005-06-01 23:31                 ` Fleurons Staszek Wawrykiewicz
2005-06-01 23:53                   ` Fleurons Hans Hagen
2005-06-02  7:39                     ` John R. Culleton [this message]
2005-06-02 22:25                       ` Fleurons Hartmut Henkel
2005-06-02 23:06                         ` Fleurons Stuart Jansen
2006-07-23 17:52                         ` Fleurons John R. Culleton
2005-06-11 20:48                       ` Fleurons Patrick Gundlach

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=200506020739.20228.john@wexfordpress.com \
    --to=john@wexfordpress.com \
    --cc=Jerzy.Ludwichowski@uni.torun.pl \
    --cc=karl@freefriends.org \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.nl \
    --cc=staw@gust.org.pl \
    --cc=v.r.w.Schaa@gsi.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).