From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: bug in \definefontfamily? (was: Re: OT salt feature not working?)
Date: Sun, 19 Mar 2017 13:38:23 +0100 [thread overview]
Message-ID: <111a26b4-e666-02db-982f-b985650d8fab@gmx.es> (raw)
In-Reply-To: <58ce6920.42ba1c0a.ea8e8.7871@mx.google.com>
On 03/19/2017 12:19 PM, josephcanedo@gmail.com wrote:
> Hi Pablo,
>
> When I typeset your MWE below with latest beta version (on win 10) you
> use too, I see 2 lines of 1110 with different appearance.
Hi Joseph,
sorry, the second sample was different. The first line was TeX Gyre
Pagella and the second line was Neo Euler.
The default feature for the whole text was old numbers. TeX Gyre Pagella
works fine with it, but Neo Euler (with \definefontfamily) doesn’t
honour "onum".
But \definefont works fine, so I guess something might be improved in
\definefontfamily. See the sample:
\definefontfeature[default][default][onum=yes]
\definefontfamily[mainface][rm][TeX Gyre Pagella]
\definefontfamily[mainface][hw][Neo Euler]
\definefont[directFont][euler.otf:+onum]
\setupbodyfont[mainface]
\starttext
\startTEXpage[offset=5ex]
1110
{\hw 1110}
\directFont 1110
\stopTEXpage
\stoptext
BTW, Neo Euler has "Neo-Euler" as PostScript name (according to
otfinfo). Maybe this is causing problems to the font loading mechanism.
Wolfgang, what do you think of this issue?
Many thanks for your help,
Pablo
--
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:[~2017-03-19 12:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-18 22:05 OT salt feature not working? Pablo Rodriguez
2017-03-19 10:11 ` Pablo Rodriguez
[not found] ` <58ce6920.42ba1c0a.ea8e8.7871@mx.google.com>
2017-03-19 12:38 ` Pablo Rodriguez [this message]
2017-03-19 19:38 ` bug in \definefontfamily? Wolfgang Schuster
2017-03-19 20:07 ` Pablo Rodriguez
2017-03-19 20:32 ` Wolfgang Schuster
2017-03-19 20:40 ` Pablo Rodriguez
2017-03-19 20:46 ` Wolfgang Schuster
2017-03-19 20:58 ` Wolfgang Schuster
2017-03-19 21:08 ` Pablo Rodriguez
2017-03-19 21:22 ` Wolfgang Schuster
2017-03-20 12:59 ` Hans Hagen
2017-03-20 12:55 ` Hans Hagen
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=111a26b4-e666-02db-982f-b985650d8fab@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).