Aditya Mahajan wrote:
I get the same error as Kevin:
! Undefined control sequence.
argument ... [\bibrefprefix ][\sectionseparator
]
Add this to fix the error:
\def\preparebibreflist#1{\def\bibreflist{#1}}%
see attached files.
For Hans:
On Sat, Apr 25, 2009 at 03:44, Yue Wang wrote:
Hi, Mojca:
However, when comment the second line (\definetypeface [iwona] [mm]
[math] [iwona] [default] [encoding=ec]),
TeXExec | runtime: 1.828
total compile time is reduced to only 2 seconds. (of course, equations
are typeset in latin
Wolfgang Schuster schuster.wolfg...@googlemail.com writes:
You could try to ask Steffen Wolfrum, he's a professional typesetter [1]
and should have knowledge about word2context conversion, that's what I
got
from a few older mails from him.
Thanks for the suggesttion Wolfgang.
Best wishes,
Hi,
On Sat, Apr 25, 2009 at 5:39 PM, Mojca Miklavec
mojca.miklavec.li...@gmail.com wrote:
On Sat, Apr 25, 2009 at 03:44, Yue Wang wrote:
Hi, Mojca:
However, when comment the second line (\definetypeface [iwona] [mm]
[math] [iwona] [default] [encoding=ec]),
TeXExec | runtime: 1.828
total
On Sat, Apr 25, 2009 at 03:08, Yue Wang wrote:
On Sat, Apr 25, 2009 at 4:29 AM, Mojca Miklavec wrote:
Where is that cache located? (Are you talking about windows?) Maybe we
could prevent deleting the font cache. This might solve your problem.
I think it is in the
On Sat, Apr 25, 2009 at 13:18, Yue Wang wrote:
But LM should suffer from the same problem.
I think LM tfm/otf metrics information are dumped to fmt statically.
See the TeX82 source code (don't know xetex's situation, but i am sure
tex82 works like that).
That's possible. But if you remove
Mojca Miklavec wrote:
The current clever scheme causes more problems longer load times
than it brings advantages, but unless Hans changes core macros,
there's not much that you can do about it to speed up the loading
time.
I assume Context could add support for an explicit tfm: prefix,
that
Yue Wang wrote:
Hi,
On Sat, Apr 25, 2009 at 5:39 PM, Mojca Miklavec
mojca.miklavec.li...@gmail.com wrote:
On Sat, Apr 25, 2009 at 03:44, Yue Wang wrote:
Hi, Mojca:
However, when comment the second line (\definetypeface [iwona] [mm]
[math] [iwona] [default] [encoding=ec]),
TeXExec | runtime:
I see, no font is defined when dumping the formats... pretty unlike plain TeX...
then why so much time is used for iwona, while only 1.2 sec is used to
load lm roman?
On Sat, Apr 25, 2009 at 8:43 PM, Hans Hagen pra...@wxs.nl wrote:
Yue Wang wrote:
Hi,
On Sat, Apr 25, 2009 at 5:39 PM, Mojca
Hi,
Taco Hoekwater wrote:
Aditya Mahajan wrote:
I get the same error as Kevin:
! Undefined control sequence.
argument ... [\bibrefprefix ][\sectionseparator
]
Add this to fix the error:
\def\preparebibreflist#1{\def\bibreflist{#1}}%
see
Yue Wang wrote:
I see, no font is defined when dumping the formats... pretty unlike plain TeX...
then why so much time is used for iwona, while only 1.2 sec is used to
load lm roman?
see previous mail ... because xetex rebuilds the fc cache each time; so
it's not related to context as all
Hi, Hans
On Sat, Apr 25, 2009 at 9:41 PM, Hans Hagen pra...@wxs.nl wrote:
Yue Wang wrote:
I see, no font is defined when dumping the formats... pretty unlike plain
TeX...
then why so much time is used for iwona, while only 1.2 sec is used to
load lm roman?
see previous mail ... because
On Sat, Apr 25, 2009 at 15:33, Yue Wang wrote:
I see, no font is defined when dumping the formats... pretty unlike plain
TeX...
then why so much time is used for iwona, while only 1.2 sec is used to
load lm roman?
I have a bit of a problem to test all that since running fc-cache only
takes
in short, can you please explain to us why
%engine=xetex
\usetypescript[modern] [ec]
Once you explain why you use [ec] ...
Mojca
___
If your question is of interest to others as well, please add an entry to
On Sat, Apr 25, 2009 at 16:09, Mojca Miklavec wrote:
in short, can you please explain to us why
%engine=xetex
\usetypescript[modern] [ec]
Once you explain why you use [ec] ...
I thought it made a difference, but I indeed don't see any timing
difference when [ec] is added, but you need
Hi, Mojca:
Once you explain why you use [ec] ...
Hans uses [ec] in the previous mail.
anyway,
%engine=xetex
\usetypescript[palatino]
\setupbodyfont[palatino,10pt]
\starttext
\input zapf
\stoptext
uses
TeXExec | runtime: 6.516
while
%engine=xetex
\usetypescript[modern]
On Sat, Apr 25, 2009 at 16:07, Yue Wang wrote:
Hi, Hans
in short, can you please explain to us why
%engine=xetex
\usetypescript[modern] [ec]
\switchtobodyfont[modern, 10pt]
\starttext
\input zapf
\stoptext
uses
TeXExec | runtime: 1.577
while
%engine=xetex
Hi,
what's the difference between lm and palatino? (I think lm contains
more fonts.)
Out of curiosity: does timing change if you delete everything but
iwona from type-otf.mkii?
maybe just set cont-sys.rme, and enable palatino there, then the
palatino loading time can be very short.
Hi,
context never dumps fonts in the format
there is one line in cont-en.tex:
\setupencoding[default=ec] \usetypescript[fallback][\defaultencoding]
\setupbodyfont[rm,12pt]
also in context.tex:
\setupencoding[default=ec]
\usetypescript[fallback][\defaultencoding]
\setupbodyfont[rm,12pt]
the
Mojca Miklavec wrote:
On Sat, Apr 25, 2009 at 15:33, Yue Wang wrote:
I see, no font is defined when dumping the formats... pretty unlike plain TeX...
then why so much time is used for iwona, while only 1.2 sec is used to
load lm roman?
I have a bit of a problem to test all that since running
[I got no answers to my previous post]
With page imposition, in luatex, background overrides text
\setuppapersize[A4][A3,landscape]
\setuparranging[2SIDE] % --bug here
\setupcolors[state=start]
\definetextbackground[intro]
[backgroundcolor=gray,
backgroundoffset=.25cm,
offset=.5cm,
Mojca Miklavec wrote:
in short, can you please explain to us why
%engine=xetex
\usetypescript[modern][ec]
Once you explain why you use [ec] ...
because i also run the test for pdftex -)
-
Am 25.04.2009 um 18:12 schrieb Mohamed Bana:
Hi guys,
How can i get a somewhat recent and stable version where things just
work.
I've tried --stable and --context=stable which both insist of
getting luatex 0.40.
the names of stable versions is 'current' but you need also a older
Mojca Miklavec wrote:
Out of curiosity: does timing change if you delete everything but
iwona from type-otf.mkii?
unrelated
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061
Yue Wang wrote:
Hi,
what's the difference between lm and palatino? (I think lm contains
more fonts.)
Out of curiosity: does timing change if you delete everything but
iwona from type-otf.mkii?
maybe just set cont-sys.rme, and enable palatino there, then the
palatino loading time can be
Am 25.04.2009 um 18:15 schrieb Diego Depaoli:
[I got no answers to my previous post]
With page imposition, in luatex, background overrides text
context --arrange filename
Wolfgang
___
If your question is of
2009/4/25 Wolfgang Schuster schuster.wolfg...@googlemail.com:
Am 25.04.2009 um 18:15 schrieb Diego Depaoli:
[I got no answers to my previous post]
With page imposition, in luatex, background overrides text
context --arrange filename
Thanks!
but I'm a bit confused...
in pdftex or xetex the
Mojca Miklavec wrote:
On Sat, Apr 25, 2009 at 18:19, Hans Hagen wrote:
Yue Wang wrote:
maybe just set cont-sys.rme, and enable palatino there, then the
palatino loading time can be very short.
loaded at runtime anyway so unrelated
as mentioned several times before now ... it has nothing to
On Sat, Apr 25, 2009 at 18:12, Mohamed Bana wrote:
Hi guys,
How can i get a somewhat recent and stable version where things just work.
I've tried --stable and --context=stable which both insist of getting luatex
0.40.
True. We only provide a single version of LuaTeX and current (that
often
Mohamed Bana wrote:
There's a lot of things broken in the current minimals, e.g., bib
module, hanging, a error about front and I can't to even seem to use OT
fonts.
bibtex fixing is in progress (at least it runs here)
otf fonts ... well, i use them all day so ...
I think context should
On Sat, 25 Apr 2009, Mojca Miklavec wrote:
On Sat, Apr 25, 2009 at 18:12, Mohamed Bana wrote:
Hi guys,
How can i get a somewhat recent and stable version where things just work.
I've tried --stable and --context=stable which both insist of getting luatex
0.40.
True. We only provide a single
Mojca Miklavec wrote:
On Sat, Apr 25, 2009 at 18:12, Mohamed Bana wrote:
Hi guys,
How can i get a somewhat recent and stable version where things just work.
I've tried --stable and --context=stable which both insist of getting luatex
0.40.
True. We only provide a single version of LuaTeX and
On Sat, Apr 25, 2009 at 6:17 PM, Wolfgang Schuster
schuster.wolfg...@googlemail.com wrote:
I think context should complain when a CLI options hasn't been spelt
correctly:
CLI?
http://en.wikipedia.org/wiki/Command-line_interpreter
--
luigi
33 matches
Mail list logo
