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: libertine typescript
Date: Wed, 17 Nov 2010 17:16:30 +0100	[thread overview]
Message-ID: <18F50F0B-3AD3-4BCE-8DBF-BB662576370E@gmail.com> (raw)
In-Reply-To: <4CE3EE36.50606@elvenkind.com>


Am 17.11.2010 um 16:01 schrieb Taco Hoekwater:

> Hans has the final answer on this, but I suspect that the
> second argument to \definetypeface has to be one of the six
> predefined font styles (or a \definefontstyle alias to those
> six). That limits the  allowable set to:
> 
>  [mm]                        [mm]
>  [rm,roman,serif,regular]    [rm]
>  [ss,sansserif,sans,support] [ss]
>  [tt,teletype,type,mono]     [tt]
>  [hw,handwritten]            [hw]
>  [cg,calligraphic]           [cg]
> 
> the reason for that is that for each of those, there is possibly
> also a bold, italic, bolditalic etc. font.

Handwritten and calligraphic have no bold or italic styles, only regular.

> Since your special fonts do not have such alternatives, the easier
> way is indeed
> 
>  \definefont[keyboard][LinBiolinum_Kb-0.5.4 sa 1]
>  \definefont[outline][fxbo sa 1]
>  \definefont[shadow][fxbs sa 1]
> 
> the reason for using 'sa 1' in those definitions is that it will
> allow the fonts to scale with the current body font size.

You can write separate typefaces and switch between typefaces for outline
and shadow styles but for many cases \definefont is enough. The keyboard
can be written with the symbol mechanism because a new font switch \kb
takes too much code:

\definefontstyle [kb,keyboard] [kb]

\starttypescript [keyboard] [default] [size]
  \definebodyfont
    [4pt,5pt,6pt,7pt,8pt,9pt,10pt,11pt,12pt,14.4pt,17.3pt]
    [kb] [default]
\stoptypescript

\definebodyfont [default] [kb]
  [tf=Keyboard sa 1]

\starttypescript [keyboard] [libertine]
  \definefontsynonym [Keyboard] [file:fxbk.otf] [features=none]
\stoptypescript

\definetypeface [mainface] [rm] [serif]    [libertine] [default]
\definetypeface [mainface] [ss] [sans]     [biolinum]  [default]
\definetypeface [mainface] [tt] [mono]     [modern]    [default]
\definetypeface [mainface] [mm] [math]     [modern]    [default]
\definetypeface [mainface] [kb] [keyboard] [libertine] [default]

\setupbodyfont[mainface]

\starttext
\rm serif \ss sans \tt mono \kb keyboard
\stoptext

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:[~2010-11-17 16:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-15 16:41 Herbert Voss
2010-11-17 15:01 ` Taco Hoekwater
2010-11-17 16:16   ` Wolfgang Schuster [this message]

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=18F50F0B-3AD3-4BCE-8DBF-BB662576370E@gmail.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).