From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: Pavneet Arora <pavneet_arora@waroc.com>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Specifying font style variant with \definefontfamily
Date: Thu, 09 Jun 2016 22:59:34 +0200 [thread overview]
Message-ID: <5759D8B6.2060308@gmail.com> (raw)
In-Reply-To: <20160609203743.GO39769@lahore>
[-- Attachment #1.1: Type: text/plain, Size: 1926 bytes --]
> Pavneet Arora <mailto:pavneet_arora@waroc.com>
> 9. Juni 2016 um 22:37
> I'm still a bit at a loss on how one goes about correctly specifying the
> variants in \definefontfamily using the default form given in the wiki.
> Usually adding "* Light", etc. is sufficient (see commented line using
> Junction font).
>
> (As an aside, is it also possible to combine \sc\bf? I haven't been
> able to figure that out).
>
> My application is using the (free) Andada font family, and I need to
> point the smallcaps style to the correct font
> (https://www.fontsquirrel.com/fonts/andada).
>
> In the following MWE I tried the following without success:
>
> 1. [sc=* SC Regular]
> 2. [sc=Andada SC Regular]
> 3. [sc=* SC-Regular]
> 4. [sc=Andada SC-Regular]
>
> All give the following (or similar) error to stdout:
>
> ...ext/tex/texmf-context/tex/context/base/mkiv/font-sel.lua:121:
> attempt to index local 'file' (a nil value)
> stack traceback:
> ...ext/tex/texmf-context/tex/context/base/mkiv/font-sel.lua:121: in
> function 'selectfont_savefile'
> ...ext/tex/texmf-context/tex/context/base/mkiv/font-sel.lua:151: in
> function <...ext/tex/texmf-context/tex/context/base/mkiv/font-sel.lua:142>
> ...ext/tex/texmf-context/tex/context/base/mkiv/font-sel.lua:526: in
> function 'registerfiles'
> ...ext/tex/texmf-context/tex/context/base/mkiv/font-sel.lua:567: in
> function 'action1'
> [string "local function scan1()..."]:55: in function <[string "local
> function scan1()..."]:42>
>
> 1 \definefontfamily[mainface][rm][Latin Modern]
> 2 >> \definefontfamily[mainface][rm][Andada][sc=Andada SC Regular]
>
>
> I end up finally settling on the form using the explicit file:
> [sc=file:AndadaSC-Regular.otf], which does work.
>
> But I really would like to understand how the first form as given in the
> wiki should be used properly? What patterns should I be looking for?
There was a bug in the code but I fixed it.
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 3149 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 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
___________________________________________________________________________________
prev parent reply other threads:[~2016-06-09 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 20:37 Pavneet Arora
2016-06-09 20:59 ` 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=5759D8B6.2060308@gmail.com \
--to=schuster.wolfgang@gmail.com \
--cc=ntg-context@ntg.nl \
--cc=pavneet_arora@waroc.com \
/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).