From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Questions regarding simplefonts
Date: Tue, 19 Jan 2010 21:15:12 +0100 [thread overview]
Message-ID: <4B5612D0.2010501@googlemail.com> (raw)
In-Reply-To: <51b0095d1001190956q3141f38ao127fbb54ed25cd4@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1962 bytes --]
Am 19.01.10 18:56, schrieb Nicolas Girard:
> Hi again,
> although simplefonts seems very promising and I put the highest hopes
> on it, the lack of proper documentation simply prevents me to use it,
> which is somewhat frustrating.
I try to provide a proper documentation when I release the next
version of my module.
> Here are some of my unanswered questions about simplefonts ; I'm
> willing to update the wiki with any informations this thread could
> bring.
>
> 1) How can I specify that the default font features should enable the
> standard ligatures (liga) ?
> I blindly tried several possibilities like
> \setupsimplefonts[features={liga}] but none worked
Ligatures are enabled in ConTeXt default fontfeature and simplefonts
applies only
the default features to the font, when you don't get them in your
document this could
be a font problem, in most cases it helps to select a different script.
\setupsimplefonts[script=latin]
or
\setmainfont[...][script=latin]
> 2) How can I get \sc to work with a font family whose small caps are
> defined as a font feature, rather than dedicated .otf files ?
The caps font is loaded by default by the smallcaps fontfeature,
if this did not work the problem could be the same as for the ligatures.
> 3) How can I get font expansion and protrusion to work using
> simplefonts' dedicated keywords ? There again, I spent more than 30
> minutes trying every combination I could think of, unsuccessfully.
> I think it would be useful to have a complete example of code
> involving simplefonts and expansion/protrusion that people could copy
> & paste from the wiki
You can use the two keys expamsion ans protrusion, their values are
the same as you have e to write in \definefontfeature.
\setupsimplefonts[expansion=quality,protrusion=quality]
or
\setmainfont[...][expansion=quality,protrusion=quality]
Examples are available on bitbucket:
http://bitbucket.org/wolfs/simplefonts/src/tip/files/
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 3432 bytes --]
[-- Attachment #2: Type: text/plain, Size: 486 bytes --]
___________________________________________________________________________________
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:[~2010-01-19 20:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-19 17:56 Nicolas Girard
2010-01-19 18:03 ` Nicolas Girard
2010-01-19 18:16 ` Wolfgang Schuster
2010-01-19 20:15 ` Wolfgang Schuster [this message]
2010-01-20 7:58 ` Marius
2010-01-20 12:59 ` Wolfgang Schuster
2010-01-20 13:52 ` Marius
2010-01-20 14:03 ` 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=4B5612D0.2010501@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).