ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Re: Fonts again in ConTeXt
Date: Thu, 13 Mar 2003 16:52:58 +0100	[thread overview]
Message-ID: <5.1.0.14.1.20030313164838.03536588@server-1> (raw)
In-Reply-To: <200303131007.07928.john@wexfordpress.com>

At 10:07 AM 3/13/2003 -0500, you wrote:
>On Thursday 13 March 2003 07:37 am, Hans Hagen wrote:
>
>(snip)
>Is it possible to take a deep breath and go back to the starting point, the
>TeX primitive \font? It allows one to name a specific font as listed in e.g.
>psfonts.map or some other designated mapping file. Control is absolute. You
>specify the font and if it is listed and installed you get it, in the size
>you specify.  As a practical matter I seldom need a font in  more than two
>sizes, and if I do then I can just dupe the \font statement, change the name
>and change the size parameter. Unfortunately Context has a much more
>elaborate, indirect and confusing (to me at least) mechanism embedded.
>
>Now, starting from this \font base, how do we add features without losing
>simplicity and basic control?  Stated another way, how can one create
>\font statements and alias them into the Context font handling system without
>too much grief?

\definefont[whatever][somename at somesize] \whatever

[or slightly more extensive (see chinese, symbols etc, for adaptive 
definitions)]

>Fonts are the most troublesome aspect of TeX in all versions, from plain
>TeX on forward.  The mission is not to add complexity, difficulty and
>confusion but to reduce them. We need a simpler way to install fonts and a
>simpler and more direct way to call for them.
>
>IMHO of course.

If you stick to english, fonts are less a problem since you can stick to 
tex's default encoding or whatever is at hand; however, it happens that 
most of us use more extensive char sets, and that each language has its own 
patterns, encodings, alternative glyphs etc.

Also, as soon as math shows up, one needs a consistent sub subsub system, 
so this adds to the complication.

And then, users want to combine fonts from different verdors, so we get 
typefaces (in context) and relative scaling, and specific interlinespace, 
and ... and ...



Hans
-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
                        information: http://www.pragma-ade.com/roadmap.pdf
                     documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------

  reply	other threads:[~2003-03-13 15:52 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-10 16:25 Displayed material, again Giuseppe Bilotta
2003-03-10 16:50 ` Bruce D'Arcus
2003-03-10 20:22   ` Re[2]: " Giuseppe Bilotta
2003-03-10 22:15     ` s-mag-01 Bruce D'Arcus
2003-03-11  8:00       ` s-mag-01 Hans Hagen
2003-03-11 14:11         ` s-mag-01 Bruce D'Arcus
2003-03-11 14:31           ` s-mag-01 Hans Hagen
2003-03-11 14:34         ` s-mag-01 Bruce D'Arcus
2003-03-11 14:46           ` Fonts again in ConTeXt Patrick Gundlach
2003-03-11 15:10             ` Bruce D'Arcus
2003-03-12 13:04               ` Maarten Sneep
2003-03-12 13:23                 ` Bruce D'Arcus
2003-03-12 13:26                   ` Maarten Sneep
2003-03-12 14:05                     ` Patrick Gundlach
2003-03-12 15:11                       ` Hans Hagen
2003-03-12 15:43                         ` Patrick Gundlach
2003-03-12 19:35                           ` Jens-Uwe Morawski
2003-03-13  8:31                             ` Patrick Gundlach
2003-03-14  8:27                               ` Hans Hagen
2003-03-12 20:26                           ` Hans Hagen
2003-03-13  8:54                             ` Patrick Gundlach
2003-03-13 12:37                               ` Hans Hagen
2003-03-13 15:07                                 ` John Culleton
2003-03-13 15:52                                   ` Hans Hagen [this message]
2003-03-21 18:05                                 ` Patrick Gundlach
2003-03-22 11:10                                   ` Hans Hagen
2003-03-14 21:34                             ` Henning Hraban Ramm
2003-03-14 21:24                           ` Henning Hraban Ramm
2003-03-21 18:06                             ` Patrick Gundlach
2003-03-12 15:09                 ` Hans Hagen
2003-03-11 15:02           ` s-mag-01 Adam Lindsay
2003-03-11 20:52             ` s-mag-01 Hans Hagen
2003-03-11  9:13       ` s-mag-01 Patrick Gundlach
2003-03-10 17:00 ` Displayed material, again Hans Hagen
2003-03-10 23:24 ` Hans Hagen
2003-03-11 10:08   ` Re[2]: " Giuseppe Bilotta
2003-03-11 10:52     ` Hans Hagen
2003-03-11 11:47       ` Re[3]: " Giuseppe Bilotta
2003-03-11 14:57         ` Hans Hagen
2003-03-11 17:04           ` Re[4]: " Giuseppe Bilotta
2003-03-12 20:36             ` Hans Hagen
2003-03-13  9:36               ` Re[5]: " Giuseppe Bilotta
2003-03-13 12:23                 ` Hans Hagen
2003-03-11 15:12         ` Re[3]: " Hans Hagen
2003-03-12 21:07         ` Hans Hagen
2003-03-13  9:38           ` Re[4]: " Giuseppe Bilotta

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=5.1.0.14.1.20030313164838.03536588@server-1 \
    --to=pragma@wxs.nl \
    --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).