ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Thomas A.Schmitz <thomas.schmitz@uni-bonn.de>
Subject: Re: chancery font
Date: Sun, 3 Apr 2005 19:10:02 +0200	[thread overview]
Message-ID: <4aed416dad30059562e80ad2bfd8018a@uni-bonn.de> (raw)
In-Reply-To: <42ADAC66@webmail.colostate.edu>


On Apr 3, 2005, at 6:15 PM, Idris Samawi Hamid wrote:

> As Ciro suggested, what what would be useful is a gui that completely
> automates the process and that asks all relevant questions and 
> generates
> everything ConTeXt needs to install and run Latin fonts, including 
> expert
> fonts like Minion.**** (Maybe oneday the gui can be extended for 
> Chinese,
> Arabic, etc.)
>

Idris,

I disagree strongly. First: fonts are a complex business, and when you 
venture outside of the normal Western character range, things start to 
get really messy (I speak from experience, having just completed work 
on Greek Extended). I'm not saying a GUI will never be able to cope 
with all  this complicated stuff. But I do think that an extraordinary 
amount of work would be needed to catch all the exceptions, ifs and 
buts that would be involved. And I do think that this work could better 
be spent on other, much more important business. To be honest: in my 
personal opinion (and this is a very personal opinion), die-hard GUI 
users who just loathe the command line should not be using TeX.

I also think that despite all the efforts that ConTeXt makes, it would 
be rash to make inexperienced users believe that handling fonts in TeX 
is a simple matter of pointing and clicking. The frustration would be 
huge when things do not work out as expected - and they will. In a way, 
the current state puts a gentle, but firm sign on font handling saying 
"This might be a bit difficult. Be warned!" And I don't think this is a 
bad thing.

No offense, but that's what I think about this issue.

Best

Thomas

  parent reply	other threads:[~2005-04-03 17:10 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-03 16:15 Idris Samawi Hamid
2005-04-03 16:42 ` Rob Ermers
2005-04-03 16:57 ` Paul Tremblay
2005-04-03 17:10 ` Thomas A.Schmitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-16 14:13 Enrique Laya
2005-04-03 20:39 Idris Samawi Hamid
2005-04-03 19:40 Idris Samawi Hamid
2005-04-03 19:54 ` Paul Tremblay
2005-04-03 20:22 ` Thomas A.Schmitz
2005-04-03 18:46 Idris Samawi Hamid
2005-04-03 18:45 Idris Samawi Hamid
2005-04-03 20:25 ` Ciro Soto
2005-04-03 21:06   ` h h extern
2005-04-02 22:33 Idris Samawi Hamid
2005-04-02 21:21 Idris Samawi Hamid
2005-04-01  8:37 btex-etex Jiri Polcar
2005-04-02 16:52 ` chancery font Ciro Soto
2005-04-02 17:27   ` Idris Samawi Hamid
2005-04-02 17:52   ` Willi Egger
2005-04-02 18:29     ` Ciro Soto
2005-04-02 19:21       ` Idris Samawi Hamid
2005-04-02 20:00         ` Ciro Soto
2005-04-02 21:22           ` Adam Lindsay
2005-04-02 23:33             ` Ciro Soto
2005-04-03 14:03               ` Rob Ermers
2005-04-03 14:57                 ` Adam Lindsay
2005-04-03 16:22                   ` Ciro Soto
2005-04-03 19:41       ` h h extern

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=4aed416dad30059562e80ad2bfd8018a@uni-bonn.de \
    --to=thomas.schmitz@uni-bonn.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).