ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <wolfgang.schuster@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Defining a title font.
Date: Thu, 4 Oct 2012 18:19:48 +0200	[thread overview]
Message-ID: <F48318EF-2723-4388-A0F5-A11D562CD266@gmail.com> (raw)
In-Reply-To: <20121004120331.447d58df@sda3.wexfordpress.net>


Am 04.10.2012 um 18:03 schrieb john Culleton <John@wexfordpress.com>:

> On Wed, 3 Oct 2012 10:45:39 +0200
> Wolfgang Schuster <wolfgang.schuster@gmail.com> wrote:
> 
>> 
>>> 
>> The command ___ mkluatexfontdb___ creates a font database for LaTeX
>> (or more concrete the luaotfload package) but context has always used
>> it___s own font database.
>> 
>> To update the font database for context you have to call ___mtxrun
>> --script fonts --reload___ but the script searches for system fonts
>> only on windows and mac machines. When you___re working on a linux
>> system you have to set the ___OSFONTDIR___ variable first.
>> 
>> Read also this:
>> http://wiki.contextgarden.net/Fonts_in_LuaTeX#Building_the_font_database
>> 
>> Wolfgang
>> 
> followed the advice in the wiki but with modifications. On my
> Slackware single-user system the OTF fonts are in
> /usr/share/fonts/OTF
> So my Context script now contains just two commands:
> 
> export OSFONTDIR=/usr/share/fonts/OTF
> context $1
> 
> And the title.tex file now looks like this:
> 
> ------------------------------------
> \usemodule[simplefonts]
> \definefont [titlefont][MyriadPro-Bold at 70bp]       
> \definefont [subtitle][MyriadPro-Bold at 25bp]       
> \startstandardmakeup
> \titlefont 
> \centerline{Scribus}
> \vskip 10pt
> \subtitle
> \centerline {for}
> \vskip 10pt
> \titlefont
> \centerline{Book Covers}
> \subtitle
> 
> \vfil
> \centerline{Free Publishing Software Series}
> \vfil
> \rm
> \stopstandardmakeup

I changed your mixed code into ConTeXt code:

\definefont [titlefont] [MyriadPro-Bold*default at 70bp]
\definefont [subtitle]  [MyriadPro-Bold*default at 25bp]

\starttext

\startstandardmakeup[align=middle]

\startstyle[titlefont]
  Scribus
  \blank[10pt]
  \style[subtitle]{for}
  \blank[10pt]
  Book Covers
\stopstyle

\vfil

\style[subtitle]{Free Publishing Software Series}

\vfil

\stopstandardmakeup

\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:[~2012-10-04 16:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-02 21:38 john Culleton
2012-10-03  8:45 ` Wolfgang Schuster
2012-10-04 16:03   ` john Culleton
2012-10-04 16:19     ` 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=F48318EF-2723-4388-A0F5-A11D562CD266@gmail.com \
    --to=wolfgang.schuster@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).