From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [OT] creating-a-style-file-in-context
Date: Tue, 27 Oct 2009 09:45:12 +0100 [thread overview]
Message-ID: <2950D330-A52F-46C6-9F92-984FED68C00A@googlemail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.0910270144470.18841@ybpnyubfg.ybpnyqbznva>
Am 27.10.2009 um 07:13 schrieb Aditya Mahajan:
>> Not yet, what do you want to know?
>
> 1. What should be the argument of \setmainfont so that all font
> switches work. From a few examples that I tried, it should be the
> font name (2nd column in mtxrun --script font --list output) after
> removing Regular/Regu ending. Is that correct?
Yes, you need the fontname without any extension /regular, italic,
bold ...)
because the module use the extension to find all alternatives.
> 2. When does \sc work? It works with Fontin, but does not work with
> Iwona, although both have the smcp feature.
In the same way as you do it with typescript and fontfeatures, enable
the latin script.
\setmainfont[Iwona][script=latin]
It was Hans decision to use script=dflt in ConTeXt and I'm uncertain
if I should change
this in the module and make latin as the default script.
> 3. Should \simplefonts!weight also include lightcondensed and heavy?
Can you provide a list for them.
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
___________________________________________________________________________________
next prev parent reply other threads:[~2009-10-27 8:45 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
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 [this message]
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=2950D330-A52F-46C6-9F92-984FED68C00A@googlemail.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).