From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: Fonts from various .otf to work with \bold, \emph, \bf, \bfa ...
Date: Fri, 7 Feb 2020 21:22:41 +0100 [thread overview]
Message-ID: <cab4123c-6645-5259-3142-83ebc3a357c2@gmx.es> (raw)
In-Reply-To: <b50eb6a7e6765f1ce7546597fc8de6c3@vivaldi.net>
On 2/7/20 8:34 AM, context@vivaldi.net wrote:
> Hello Pablo,
>
> thank you for showing the way; unfortunately, still something is
> missing:
Hi Lukas,
I’m afraid you missed to install the fonts in ConTeXt.
> - the resulting file uses LMRoman instead of WorkSans,
Otherwise, \definefontfamily won’t work (even if using
"tf={file:work-sans.light.otf}").
Do you have any problem installing fonts in ConTeXt? This would make
things easier.
> - Note that all WorkSans files:
> [...]
> are placed in the same directory as the main source file. (I can zip
> them and upload somewhere for testing purposes.)
This was a feature already discussed in the past.
"\definefont[Test][file:your-font-file.otf]" should work, but I never
used this approach.
I think you need to mix fonts into a typeface with something similar to
a typescript (but this is all Greek to me).
--
http://www.ousia.tk
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2020-02-07 20:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 9:04 context
2020-02-06 19:24 ` Pablo Rodriguez
2020-02-07 7:34 ` context
2020-02-07 20:22 ` Pablo Rodriguez [this message]
2020-02-07 21:58 ` Henning Hraban Ramm
2020-02-08 11:49 ` 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=cab4123c-6645-5259-3142-83ebc3a357c2@gmx.es \
--to=oinos@gmx.es \
--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).