ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Font selection problem in MKIV
Date: Sat, 21 May 2011 19:31:24 +0200	[thread overview]
Message-ID: <3E9D70E9-BB0B-4FDE-B66D-EB6FFF480634@googlemail.com> (raw)
In-Reply-To: <20110521153146.GA9053@innsmouth.lan>


Am 21.05.2011 um 17:31 schrieb Otso Helenius:

>> Try
>>> \switchtotypeface[LeagueScript][12pt]
>> \switchtobodyfont[LeageScript]
> 
> Is \switchtobodyfont the recommended way of changing the typeface temporarily anywhere in a document
> (for example when making cover page graphics)? Its name implies only document body.
> 
> Nevertheless, \switchtobodyfont works (at least in the document body, haven't tested yet elsewhere)
> without setting \setupbodyfont.

\switchtotypeface wasn’t working for you because the second argument
expects a font alternative (e.g. rm, ss etc.)  and not the size.

You can also switch to a certain typeface when you use the command,
in your case \LeagueScript but have to ensure that the typeface
is loaded, otherwise you’ll get an error message.

The preferred method to select a typescript are \setupbodyfont and
\switchtobodyfont, the differences between both is that \switchtobodyfont
use the chosen font only for the document text while \setupbodyfont
affects also the header and footer of your document.

>> \definetypeface[LeagueScript][ss][specsans][League Script Thin]
>> \definetypeface[Pompadour][ss][specsans][Pompadour]
> 
> This seems to work for most fonts, with others like Pompadour it fails (pompadour has SubFamily string of
> "Black" [Mac] and "Regular" [Windows] in the .otf), and spec fails to find pompadour-normal-normal which
> it is looking for). Pompadour is a serif font, so i tried also with arguments [rm][specserif].

A real problem with all TeX systems, fonts have too many names
and it’s hard to know which one you need to load it.

> I have looked into co-typography.pdf for help, and while it is very extensive in some parts, in others it
> is (too) technical and lacks expanations for some parameters.

Indeed, Hans explains in his manuals sometimes too much which can
confuse a beginner because these information aren’t necessary to
use a certain mechanism, e.g. to load a font.

Wolfgang
___________________________________________________________________________________
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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2011-05-21 17:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-21 15:31 Otso Helenius
2011-05-21 17:31 ` Wolfgang Schuster [this message]
2011-05-21 18:21   ` Otso Helenius
2011-05-22  7:22     ` Wolfgang Schuster
2011-05-21 20:03   ` Otso Helenius
2011-05-22  7:25     ` Wolfgang Schuster
  -- strict thread matches above, loose matches on Subject: below --
2011-05-21 14:38 Otso Helenius
2011-05-21 14:50 ` 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=3E9D70E9-BB0B-4FDE-B66D-EB6FFF480634@googlemail.com \
    --to=schuster.wolfgang@googlemail.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).