From: "George N. White III" <gnwiii@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: font switching questions
Date: Thu, 19 Mar 2009 15:17:12 -0300 [thread overview]
Message-ID: <22af238a0903191117t7ebcc31dveef318097a95a057@mail.gmail.com> (raw)
In-Reply-To: <49C2639D.7040607@elvenkind.com>
On Thu, Mar 19, 2009 at 12:24 PM, Taco Hoekwater <taco@elvenkind.com> wrote:
> Alan Stone wrote:
>>
>> The most important thing I understand from reading the fonts manual
>> and the ConTeXt manual's old and new font chapter for the n-th time
>> (lost count), is that explaining fonts and their use is not a piece
>> cake. As such, every effort in trying to explain it in a way that's
>> understandable to non initiated people can only be appreciated and
>> welcomed.
>
> Any remaining inclarity in any published documentation is by definition
> unexpected by the author of that documentation. So if something is
> unclear, you really have to mention specifically what it is exactly
> that is unclear. Otherwise, no progress will ever be made...
When I write, I try to guess the level of understanding/background of the
reader. With fonts (also graphics) it isn't appropriate to provide all the
background in a TeX documentation, so what is needed is a some
pointers to the required background material. I do expect a reader
who comes without the required background to find things they don't
understand, but the way to handle that is to send them to the appropriate
references.
--
George N. White III <aa056@chebucto.ns.ca>
Head of St. Margarets Bay, Nova Scotia
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-03-19 18:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 21:48 Alan Stone
2009-03-17 22:27 ` Hans Hagen
2009-03-17 23:48 ` Wolfgang Schuster
2009-03-18 8:05 ` Hans Hagen
2009-03-18 8:12 ` Alan Stone
2009-03-18 8:23 ` Hans Hagen
2009-03-18 8:39 ` Alan Stone
2009-03-18 8:51 ` Wolfgang Schuster
2009-03-18 10:44 ` Hans Hagen
2009-03-18 10:34 ` Alan Stone
2009-03-18 15:26 ` Alan Stone
2009-03-18 16:03 ` Wolfgang Schuster
2009-03-19 15:17 ` Alan Stone
2009-03-19 15:24 ` Taco Hoekwater
2009-03-19 16:38 ` Alan Stone
2009-03-19 18:17 ` George N. White III [this message]
2009-03-19 15:29 ` Hans Hagen
2009-03-19 16:39 ` Alan Stone
2009-03-19 15:36 ` Peter Rolf
2009-03-19 17:50 ` Wolfgang Schuster
2009-03-23 10:51 ` Alan Stone
2009-03-23 11:08 ` Wolfgang Schuster
2009-03-23 11:16 Vyatcheslav Yatskovsky
2009-03-23 11:20 ` Wolfgang Schuster
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=22af238a0903191117t7ebcc31dveef318097a95a057@mail.gmail.com \
--to=gnwiii@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).