From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: LM typsescript problem
Date: Tue, 24 Feb 2009 21:32:29 +0100 [thread overview]
Message-ID: <fe8d59da0902241232y4c1d6b7fv73a6ef192b58d045@mail.gmail.com> (raw)
In-Reply-To: <13B0D3C6-37C6-4A67-BB40-AF2450D52030@princeton.edu>
On Tue, Feb 24, 2009 at 9:12 PM, Alan Bowen <acbowen@princeton.edu> wrote:
> That is what he means, Aditya! *–) Many thanks. A.
ah ok. this one
\usetypescript[serif,sans,mono][hanging][pure]
\setupalign[hanging]
\usetypescript[modern-base][texnansi] % a simplified latin-modern typescript
\setupbodyfont[reset]
\setupbodyfont[modern]
In mkii usually with "font installation" one means run texfont (with
appropriate switches ) on a set of fonts .
If a font is installed correctly, this font can be "loaded" , or
.better, made available to the engine
But in in mkiv there is no need for texfont so fonts installation is
more easy: just copy them into the right places, and it's all ok.
--
luigi
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-02-24 20:32 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-22 15:56 Alan Bowen
2009-02-23 17:22 ` Alan Bowen
2009-02-23 17:40 ` Thomas A. Schmitz
2009-02-23 17:52 ` Alan Bowen
2009-02-23 18:26 ` luigi scarso
2009-02-23 19:20 ` Alan Bowen
2009-02-23 20:03 ` Alan Bowen
2009-02-23 20:15 ` luigi scarso
2009-02-23 20:24 ` Aditya Mahajan
2009-02-23 21:59 ` Alan Bowen
2009-02-23 22:37 ` Aditya Mahajan
2009-02-24 12:43 ` Alan Bowen
2009-02-24 12:57 ` Thomas A. Schmitz
2009-02-24 13:04 ` luigi scarso
2009-02-24 13:20 ` Alan Bowen
2009-02-24 13:28 ` Hans Hagen
2009-02-24 13:54 ` Alan Bowen
2009-02-24 14:05 ` Thomas A. Schmitz
2009-02-24 14:46 ` Alan Bowen
2009-02-24 15:01 ` Thomas A. Schmitz
2009-02-24 15:13 ` Alan Bowen
2009-02-24 15:22 ` Thomas A. Schmitz
2009-02-24 15:42 ` Alan Bowen
2009-02-24 16:00 ` Thomas A. Schmitz
2009-02-24 16:52 ` Alan Bowen
2009-02-24 17:36 ` Alan Bowen
2009-02-24 17:47 ` Thomas A. Schmitz
2009-02-24 18:23 ` Alan Bowen
2009-02-24 18:41 ` luigi scarso
2009-02-24 18:49 ` Alan Bowen
2009-02-24 18:59 ` luigi scarso
2009-02-24 19:51 ` Alan Bowen
2009-02-24 19:57 ` Aditya Mahajan
2009-02-24 20:12 ` Alan Bowen
2009-02-24 20:32 ` luigi scarso [this message]
2009-02-24 20:52 ` Alan Bowen
2009-02-24 21:05 ` luigi scarso
2009-02-24 20:21 ` Hans Hagen
2009-02-24 20:26 ` Alan Bowen
2009-02-24 20:49 ` Hans Hagen
2009-02-24 15:53 ` Alan Bowen
2009-02-24 16:03 ` Thomas A. Schmitz
2009-02-24 16:12 ` Alan Bowen
2009-02-24 13:31 ` Alan Bowen
2009-02-24 13:50 ` Thomas A. Schmitz
2009-02-25 13:23 ` Mojca Miklavec
2009-02-25 14:01 ` Alan Bowen
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=fe8d59da0902241232y4c1d6b7fv73a6ef192b58d045@mail.gmail.com \
--to=luigi.scarso@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).