ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: basic fontsizes question
Date: Wed, 08 Jun 2016 11:11:06 +0200	[thread overview]
Message-ID: <5757E12A.4020306@gmail.com> (raw)
In-Reply-To: <5757D8CA.2070003@fehige.de>


[-- Attachment #1.1: Type: text/plain, Size: 1531 bytes --]

> Thomas Fehige <mailto:thomas@fehige.de>
> 8. Juni 2016 um 10:35
> Nevertheless, I prefer to keep all the font and fontsize definitions 
> and tweaks together in the preamble. This poster is not the only work 
> I'm planning to do in ConTeXt, and I need to learn to swim while 
> already in the water ;) .
For short texts where you want a certain style and size (e.g. a title 
page or a poster with few words) \definedfont is the recommended method, 
for larger amounts of the text (e.g. the abstract of a book) you can use 
\switchtobodyfont to change the size.
> Meanwhile I found the command \definebodyfontswitch and defined 
> switches like \normalsize, \scriptsize, \large, \Large etc.
The \definebodyfontswitch creates only a command which uses 
\switchtobodyfont with a fixed number of arguments.
> But this doesn't explain why \definebodyfontenvironment did not do 
> anything in my MNWE. The fonts book is not very clear on its intended 
> use.
You put spaces before and after = which aren’t allowed there.

\definebodyfontenvironment
   [24pt]
   [         small=22pt,
               big=28pt,
                 x=22pt,
                xx=16pt,
                 a=30pt,
                 b=40pt,
                 c=50pt,
                 d=60pt,
    interlinespace=30pt,
                em=italic]

\setupbodyfont[palatino,24pt]

\starttext

\startlines
  \tf   tf
{\tfa  tfa}
{\tfb  tfb}
{\tfc  tfc}
{\tfd  tfd}
{\tfx  tfx}
{\tfxx tfxx}
\stoplines

\stoptext

Wolfgang

[-- Attachment #1.2: Type: text/html, Size: 3234 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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:[~2016-06-08  9:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-29 10:35 issue in the wiki Pablo Rodriguez
2016-05-29 15:31 ` Mohammad Hossein Bateni
2016-05-29 16:36   ` Letterspacing Thomas Fehige
2016-05-29 16:49     ` Letterspacing Hans Hagen
2016-05-31  8:31   ` issue in the wiki Pablo Rodriguez
2016-06-06  8:11     ` Partial \framed Thomas Fehige
2016-06-06 10:32       ` Wolfgang Schuster
2016-06-06 12:14         ` Thomas Fehige
2016-06-06 14:04           ` basic fontsizes question Thomas Fehige
2016-06-06 14:05           ` Thomas Fehige
2016-06-06 14:20             ` Thomas Fehige
2016-06-06 20:48             ` Wolfgang Schuster
2016-06-08  8:35               ` Thomas Fehige
2016-06-08  9:11                 ` Wolfgang Schuster [this message]
2016-06-08 12:40                   ` Thomas Fehige

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=5757E12A.4020306@gmail.com \
    --to=schuster.wolfgang@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).