I had to rename CAMBRIA.TTC to cambria.ttc, now mtxrun lists the same
features.
Perhaps a luatex problem?
Tlig now works, but with Cambria ligatures i had no luck yet with following
testfile:
-
\definefontfeature[default][default][script=latn,language=dflt]
Hi Hans, hi all,
First:
in the last 2 Betas (today and yesterday) the parameter --interface
for texexec seems not to work anymore.
my log:
texmfstart texexec --interface=xp --autopdf --luatex ligtest.tex
TeXExec | processing document 'ligtest.tex'
TeXExec | no ctx file found
TeXExec | tex
Am 04.03.2009 um 14:32 schrieb Lutz Haseloff:
Hi Hans, hi all,
First:
in the last 2 Betas (today and yesterday) the parameter --interface
for texexec seems not to work anymore.
Use 'context --interface=xp ...'
Second:
The command || like in knuth.tex seems not to work properly in mkiv.
Lutz Haseloff wrote:
Hi Hans, hi all,
First:
in the last 2 Betas (today and yesterday) the parameter --interface
for texexec seems not to work anymore.
my log:
texmfstart texexec --interface=xp --autopdf --luatex ligtest.tex
TeXExec | processing document 'ligtest.tex'
TeXExec | no ctx
Lutz Haseloff wrote:
I can't enable fontfeatures for the Vista-Fonts for instance Cambria.
They are simply ignored. They are OTF with TTF extensions, ist this
the reason?
mtxrun --script font --list --info cambria
lists a whole lot; but in cambria there is no dflt, dflt so you need to
be
On Wed, Mar 4, 2009 at 4:35 PM, Hans Hagen pra...@wxs.nl wrote:
Lutz Haseloff wrote:
I can't enable fontfeatures for the Vista-Fonts for instance Cambria.
They are simply ignored. They are OTF with TTF extensions, ist this
the reason?
mtxrun --script font --list --info cambria
lists a
Wolfgang Schuster wrote:
On Wed, Mar 4, 2009 at 4:35 PM, Hans Hagen pra...@wxs.nl wrote:
Lutz Haseloff wrote:
I can't enable fontfeatures for the Vista-Fonts for instance Cambria.
They are simply ignored. They are OTF with TTF extensions, ist this
the reason?
mtxrun --script font --list
Taco Hoekwater wrote:
Peter Rolf wrote:
hi,
i'm still trying to make my code run with mkiv. here are two minor
problems. the first one is easy to deal with, but the second one
currently breaks my testbed.
% engine=luatex
\setupcolors[state=start]
\starttext
\startMPcode
label(no
hi,
i'm still trying to make my code run with mkiv. here are two minor
problems. the first one is easy to deal with, but the second one
currently breaks my testbed.
% engine=luatex
\setupcolors[state=start]
\starttext
\startMPcode
label(no color,origin) withcolor red; % always black
Peter Rolf wrote:
hi,
i'm still trying to make my code run with mkiv. here are two minor
problems. the first one is easy to deal with, but the second one
currently breaks my testbed.
% engine=luatex
\setupcolors[state=start]
\starttext
\startMPcode
label(no color,origin)
On Fri, May 16, 2008 at 1:12 PM, Peter Rolf [EMAIL PROTECTED] wrote:
hi,
i'm still trying to make my code run with mkiv. here are two minor
problems. the first one is easy to deal with, but the second one
currently breaks my testbed.
% engine=luatex
\setupcolors[state=start]
\starttext
Taco Hoekwater schrieb:
Peter Rolf wrote:
hi,
i'm still trying to make my code run with mkiv. here are two minor
problems. the first one is easy to deal with, but the second one
currently breaks my testbed.
% engine=luatex
\setupcolors[state=start]
\starttext
\startMPcode
Wolfgang Schuster schrieb:
On Fri, May 16, 2008 at 1:12 PM, Peter Rolf [EMAIL PROTECTED] wrote:
hi,
i'm still trying to make my code run with mkiv. here are two minor
problems. the first one is easy to deal with, but the second one
currently breaks my testbed.
% engine=luatex
13 matches
Mail list logo
