From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [OT] creating-a-style-file-in-context
Date: Mon, 26 Oct 2009 01:42:41 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.00.0910260131150.26191@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <C39374A0-6562-4D0F-B48E-D5813AB294B3@googlemail.com>
On Sun, 25 Oct 2009, Wolfgang Schuster wrote:
>
> Am 21.10.2009 um 11:05 schrieb luigi scarso:
>
>> http://randomdeterminism.wordpress.com/2009/10/21/creating-a-style-file-in-context/
>
> Why not simplefonts instead of typescript files,
I understand typescripts, so there was never a need to try out
simplefonts. I did that right now and it setting the document fonts is
really easy. I might end up not using typescripts any more :-)
> there is also a definefont command
>
> \definesimplefont[interludefont][Museo700 at 28pt]
This does not work, I get latin modern mono instead!
\definesimplefont[interludefont][Museo700]
works correctly, but at the main font size.
\definesimplefont[interludefont][Museo700][size=28pt]
does not change the font size.
> For the interlude text the standard- or textmakeup environments are perfect
> suited.
True. I will post an update "soon".
Aditya
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2009-10-26 5:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 9:05 luigi scarso
2009-10-25 9:15 ` Jan-Erik Hägglöf
2009-10-25 9:23 ` Wolfgang Schuster
2009-10-25 9:27 ` Taco Hoekwater
2009-10-25 9:37 ` Wolfgang Schuster
2009-10-25 10:27 ` Jan-Erik Hägglöf
2009-10-25 10:40 ` Wolfgang Schuster
2009-10-25 11:05 ` Aditya Mahajan
2009-10-25 12:09 ` Jan-Erik Hägglöf
2009-10-25 12:17 ` Aditya Mahajan
2009-10-25 12:28 ` Jan-Erik Hägglöf
2009-10-25 12:32 ` Jan-Erik Hägglöf
2009-10-25 12:45 ` Wolfgang Schuster
2009-10-25 14:17 ` Jan-Erik Hägglöf
2009-10-25 14:29 ` Wolfgang Schuster
2009-10-25 14:53 ` Jan-Erik Hägglöf
2009-10-26 5:42 ` Aditya Mahajan [this message]
2009-10-26 7:43 ` Wolfgang Schuster
2009-10-26 16:13 ` Aditya Mahajan
2009-10-26 21:20 ` Wolfgang Schuster
2009-10-27 6:13 ` Aditya Mahajan
2009-10-27 8:45 ` Wolfgang Schuster
2009-10-27 8:50 ` Hans Hagen
2009-10-27 8:56 ` Wolfgang Schuster
2009-10-27 9:11 ` Hans Hagen
2009-10-27 9:13 ` luigi scarso
2009-10-27 13:38 ` Aditya Mahajan
2009-10-27 22:08 ` 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=alpine.LNX.2.00.0910260131150.26191@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--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).