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 do
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 do with the
Yue Wang wrote:
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]
\setupbodyf
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
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
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 -)
-
Yue Wang wrote:
Hi, Hans
On Sat, Apr 25, 2009 at 9:41 PM, Hans Hagen 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 xet
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 f
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
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 shor
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, 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]
\setupbodyf
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
> 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
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
take
Hi, Hans
On Sat, Apr 25, 2009 at 9:41 PM, Hans Hagen 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 xet
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 name
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 wrote:
> Yue Wang wrote:
>>
>> Hi,
>>
>> On Sat, Apr 25, 2009 at 5:39 PM, Mojca Miklav
Mojca Miklavec wrote:
Hans wanted to implement
\definefontsynonym [a] [b]
to automatically work whether b is a font name, font filename or the
old good tfm font.
Even though the idea sounds OK and works well in LuaTeX, there's a big
problem with it, namely, it becomes so annoyingly slow tha
Yue Wang wrote:
Hi,
On Sat, Apr 25, 2009 at 5:39 PM, Mojca Miklavec
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 compile time is red
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
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
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 C:\context\tex\tex
Hi,
On Sat, Apr 25, 2009 at 5:39 PM, Mojca Miklavec
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 compile time is redu
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 m
Hi, Mojca:
you are absolutely right!
When load iwona with the following two typeface, the loading time
takes up 7-8 seconds.
TeXExec | runtime: 8.296
\definetypeface [iwona] [ss] [sans] [iwona] [default] [encoding=ec]
\definetypeface [iwona] [mm] [math] [iwona] [default] [encoding=ec]
\setupbod
On Sat, Apr 25, 2009 at 4:29 AM, Mojca Miklavec
wrote:
> On Fri, Apr 24, 2009 at 13:33, Yue Wang wrote:
>> Hi, Hans
>>
>> Each time first-setup.bat runs, it erase the user fontforge cache.
>
> Where is that cache located? (Are you talking about windows?) Maybe we
> could prevent deleting the font
On Fri, Apr 24, 2009 at 22:57, Hans Hagen wrote:
> Mojca Miklavec wrote:
>>
>> Iwona? There are lines like
>> \definefontsynonym [Iwona-Regular] [file:Iwona-Regular]
>> [features=default]
>> which means that it first searches on texmf tree, but I suspect that
>> math fonts are being searched via
Mojca Miklavec wrote:
On Fri, Apr 24, 2009 at 13:33, Yue Wang wrote:
Hi, Hans
Now I know why XeTeX uses 1-2 minutes to compile a simple document:
Each time first-setup.bat runs, it erase the user fontforge cache.
So if I compile a document right after updating ConTeXt minimals,
XeTeX will autom
On Fri, Apr 24, 2009 at 13:33, Yue Wang wrote:
> Hi, Hans
>
> Each time first-setup.bat runs, it erase the user fontforge cache.
Where is that cache located? (Are you talking about windows?) Maybe we
could prevent deleting the font cache. This might solve your problem.
Mojca
_
On Fri, Apr 24, 2009 at 13:33, Yue Wang wrote:
> Hi, Hans
>
> Now I know why XeTeX uses 1-2 minutes to compile a simple document:
> Each time first-setup.bat runs, it erase the user fontforge cache.
> So if I compile a document right after updating ConTeXt minimals,
> XeTeX will automatically run f
Hi, Hans
Now I know why XeTeX uses 1-2 minutes to compile a simple document:
Each time first-setup.bat runs, it erase the user fontforge cache.
So if I compile a document right after updating ConTeXt minimals,
XeTeX will automatically run fc-cache to generate the font cache.
Today I test a littl
Yue Wang wrote:
is that normal?
%engine=xetex
\usetypescript[palatino]
\setupbodyfont[palatino]
\starttext
$$\int_0^t$$
\stoptext
uses
(see the transcript file for additional information)
Output written on test.pdf (1 page).
i get
(c:/data/develop/context/sources/sort-def.tex)
(c:/data/deve
is that normal?
%engine=xetex
\usetypescript[palatino]
\setupbodyfont[palatino]
\starttext
$$\int_0^t$$
\stoptext
uses
(see the transcript file for additional information)
Output written on test.pdf (1 page).
Transcript written on test.log.
TeXUtil | parsing file test.tui
TeXUtil | shortcuts : 1
Yue Wang wrote:
Hi,
When I use XeTeX, font searching through texmf- tree is very slow.
search font through fontconfig is very fast.
plain TeX or LaTeX does not have that problem.
why is that? anyway to improve it?
afaik xetex perfers to look in the database first and then on the file
system
Hi,
When I use XeTeX, font searching through texmf- tree is very slow.
search font through fontconfig is very fast.
plain TeX or LaTeX does not have that problem.
why is that? anyway to improve it?
Yue Wang
___
If yo
36 matches
Mail list logo
