ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Font questions once again...
Date: Thu, 28 Aug 2008 14:21:04 +0200	[thread overview]
Message-ID: <48B69830.4030808@elvenkind.com> (raw)
In-Reply-To: <20080828104934.GS4017@atos.labs.wmid.amu.edu.pl>

Marcin Borkowski wrote:
> I looked a bit at the type-otf.tex file.  At the beginning, it says
> something like "\starttypescriptcollection[examples]".  Typescripts from
> this \start...\stop block work correctly (with the exception of Antykwa
> Torunska).  Typescripts from the outside don't work (with the exception
> of Heros).  

The \starttypescriptcollection command is only relevant if
\preloadtypescripts is given. If that is not the case, you can
forget about it immediately. (and in the other case it is still 
undocumented, but it should not matter)

 > Maybe I should mimick these definitions somehow?  Still, the
> cases of Antykwa Torunska and Heros are mysterious to me.

Answered by Wolfgang.

> The table 1.7 you mentioned is also a bit strange: it mentions palatino
> as "commercial".

You found a bug in the manual, I have corrected the table and uploaded
a new version. Please let me know if it makes more sense now.

> What I was aiming at was: how to (easily) use the fonts "shipped with
> ConTeXt" (i.e., the Minimals).  I would expect them to be usable "out of
> the box"; if they are not, please consider this a bug report/feature
> request;).  In fact, I would expect something like
> \useptypescript[pagella]
> \setupbodyfont[pagella]
> work for the whole collection in the Minimals.

The top-level typescripts provided by Hans are only examples. The
typeface buildingblocks (from the tables in co-fonts.pdf) are all
there, but the combination of those into typescripts (as in the top
of type-otf and type-one) is generally left to the user.

> (BTW, why is pagella called palatino etc?  I guess that some aliases
> could also be default?)

answered by Wolfgang

Best wishes,
Taco
___________________________________________________________________________________
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
___________________________________________________________________________________


  parent reply	other threads:[~2008-08-28 12:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-25 20:46 Marcin Borkowski
2008-08-25 21:05 ` Thomas A. Schmitz
2008-08-25 21:34   ` Marcin Borkowski
2008-08-25 22:14     ` Olivier Guéry
2008-08-28  9:44   ` Marcin Borkowski
2008-08-28  9:56     ` Wolfgang Schuster
2008-08-28 10:29       ` Taco Hoekwater
2008-08-28 10:49         ` Marcin Borkowski
2008-08-28 12:02           ` Wolfgang Schuster
2008-08-28 12:21           ` Taco Hoekwater [this message]
2008-08-28  9:58     ` Hans Hagen
2008-08-28 10:03       ` Marcin Borkowski
2008-08-28 23:55 ` Mojca Miklavec
2008-08-29  5:42   ` Marcin Borkowski
2008-08-29  7:33     ` Hans Hagen

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=48B69830.4030808@elvenkind.com \
    --to=taco@elvenkind.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).