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
The issue is
with the font:
\definefontfeature[default][default][onum=yes]
\definefontfamily[mainface][rm][TeX Gyre Pagella]
\definefontfamily[mainface][hw][Neo Euler]
\setupbodyfont[mainface]
\starttext
\startTEXpage[offset=5ex]
1110
\hw 1110
\stopTEXpage
\stoptext
Just in case it helps, LuaTeX-0.95
from TeX Live 2016 works fine with
both features in this font:
\input ifluatex.sty
\ifluatex\input luaotfload.sty\fi
\font\1="euler.otf:+salt"
\font\2="euler.otf:+onum"
\1
1110\2 1110
\bye
I don’t know why this happens. Could
anyone confirm the issue?
Many thanks for your help,
Pablo
Dear
list,
I have the following sample:
\definefontfeature[default][default][salt=yes]
\definefontfamily[mainface][rm][Neo Euler]
\setupbodyfont[mainface]
\starttext
\startTEXpage[offset=1em]
1110
\type{1110}
\stopTEXpage
\stoptext
I get the same results with or
without the first line commented out.
(I’m using latest beta from
2017.03.02 22:23.)
Is this a bug or what am I missing?