On 31-5-2010 12:08, Michael Saunders wrote:
add mode=node to the 'body' feature definitions
I added it. I get the same results.
you can try
\usemodule[fnt-20]
\setvariables
[otftracker]
[font=somefont,
features=default,
size=48pt,
sample=your short text]
and see what is
On 30-5-2010 11:24, Michael Saunders wrote:
\definefontfeature[body][default][script=latn,onum=yes,pnum=yes,calt=yes,protrusion=quality,expansion=quality]
\definefontfeature[in][body][sinf=yes]%inferior
\definefontfeature[su][body][sups=yes,ordn=yes]%superior
Michael Saunders wrote:
In addition, everything involving inferiors, superiors, numerators and
denominators is now broken. For example:
\definefontfeature[in][body][sinf=yes]%inferior
Cs{\setff{in}133}
has no effect.
This depends on whether the font supports the sinf feature. The
default
How is the [body] feature defined?
\definefontfeature[body][default][onum=yes,pnum=yes,calt=yes,protrusion=quality,expansion=quality]
\definefontfeature[in][body][sinf=yes]%inferior
\definefontfeature[su][body][sups=yes,ordn=yes]%superior
\definefontfeature[nu][body][numr=yes]%numerator
Thanks, I added the line to the \@@bk block in str-flt.mkiv, but I
don't know how to remake the formats. I tried:
mtxrun --script fonts --reload
luatools --generate
texexec --make --all
texexec --make --all --pdftex
texexec --make --all --xetex
luatools --generate
luatools --ini --compile
Michael Saunders wrote:
How is the [body] feature defined?
\definefontfeature[body][default][onum=yes,pnum=yes,calt=yes,protrusion=quality,expansion=quality]
Please add script=latn, that works for Palatino Nova, and I think
there possibly was in change in that a while back (some months).
Please add script=latn, that works for Palatino Nova, and I think
there possibly was in change in that a while back (some months).
Thanks, I have added script=latn to \definefontfeature[body], but
those Open Type features still aren't back to normal. I should have
mentioned that I had:
Michael Saunders wrote:
Please add script=latn, that works for Palatino Nova, and I think
there possibly was in change in that a while back (some months).
Thanks, I have added script=latn to \definefontfeature[body], but
those Open Type features still aren't back to normal. I should have
There is no test file, and I still do not know which font you are
using. Attempting to find the problem is closer to tea-gazing
than to debugging at the moment. Font features cannot be debugged
independent of the actual font.
Thanks, I understand. I had been using GaramondPremrPro (which has
On 30-5-2010 10:36, Michael Saunders wrote:
There is no test file, and I still do not know which font you are
using. Attempting to find the problem is closer to tea-gazing
than to debugging at the moment. Font features cannot be debugged
independent of the actual font.
Thanks, I understand. I
you can try
mtxrun --script font --list --info garamondpremrpr
...
to see what happens with features
Thanks. This seems to confirm that the features are there:
MTXrun | dnom cyrl dflt
MTXrun | grek dflt
MTXrun | latn aze crt deu dflt fra ita mol rom srb
On 30-5-2010 11:24, Michael Saunders wrote:
you can try
mtxrun --script font --list --info garamondpremrpr
to see what happens with features
Thanks. This seems to confirm that the features are there:
MTXrun | dnom cyrl dflt
MTXrun | grek dflt
MTXrun |
add mode=node to the 'body' feature definitions
I added it. I get the same results.
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
This problem we have seen before, and I think it was a luatex bug then.
Which luatex is this ? 0.60.1 ?
It was .50, so I updated to .60. I'm still getting errors with the
same behavior, e.g.:
% block of text
block of text
and
block of text
% block of text
work, but
block of text
block of
Michael Saunders wrote:
In addition, everything involving inferiors, superiors, numerators and
denominators is now broken. For example:
\definefontfeature[in][body][sinf=yes]%inferior
Cs{\setff{in}133}
has no effect.
This depends on whether the font supports the sinf feature. The
default
In addition, everything involving inferiors, superiors, numerators and
denominators is now broken. For example:
\definefontfeature[in][body][sinf=yes]%inferior
Cs{\setff{in}133}
has no effect.
This depends on whether the font supports the sinf feature. The
default fonts do not.
I keep running into errors that look like this:
! LuaTeX error ...imal/tex/texmf-context/tex/context/base/lpdf-ini.lua:345:
pdf.immediateobj() object in use
I can't find anything specific that's causing them. For example:
input{chapter1}
input{chapter2}
fails, but:
%input{chapter1}
Michael Saunders wrote:
Or, I may make a small change, get the error, reverse the change, and
continue to get the error. Maybe I need to allocate more memory
somehow? what's wrong?
This problem we have seen before, and I think it was a luatex bug then.
Which luatex is this ? 0.60.1 ?
18 matches
Mail list logo
