ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Yue Wang <yuleopen@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Why searching fonts in xetex is so slow?
Date: Fri, 24 Apr 2009 19:33:27 +0800	[thread overview]
Message-ID: <68bfdc900904240433p3e47c85dj271b7452ceb0b94d@mail.gmail.com> (raw)
In-Reply-To: <49B4D328.6050503@wxs.nl>

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 little bit, the time used for fc-cache -r is
approximately the xetex's first running time.

Next compilation uses about 7-8 seconds, which is reasonable (it first
searches the fc cache, then the texmf tree)
btw, can we change the type-otf.tex to force mkii to search fonts like
iwona and tex gyre in the texmf tree first?
Then the compilation will run much faster than before.

Yue Wang


On Mon, Mar 9, 2009 at 4:28 PM, Hans Hagen <pragma@wxs.nl> wrote:
> 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/develop/context/sources/sort-lan.tex) [1.1]stdin -> test.pdf
> [1]
> 4770 bytes written
>
> systems         : end file test at line 8
>  )
> (see the transcript file for additional information)
> Output written on test.pdf (1 page).
>
> it's indeed not so fast, maybe because one of the used files cannot be found
> fast
>
> eventually we might end up with extending the xtx typescript
>
> Hans
>
>
> -----------------------------------------------------------------
>                                          Hans Hagen | PRAGMA ADE
>              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>     tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
>                                             | www.pragma-pod.nl
> -----------------------------------------------------------------
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to
> the Wiki!
>
> maillist : ntg-context@ntg.nl /
> http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive  : https://foundry.supelec.fr/projects/contextrev/
> wiki     : http://contextgarden.net
> ___________________________________________________________________________________
>
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2009-04-24 11:33 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-04  5:24 Yue Wang
2009-03-04  8:04 ` Hans Hagen
2009-03-09  2:14   ` Yue Wang
2009-03-09  8:28     ` Hans Hagen
2009-04-24 11:33       ` Yue Wang [this message]
2009-04-24 20:27         ` Mojca Miklavec
2009-04-24 20:57           ` Hans Hagen
2009-04-24 21:17             ` Mojca Miklavec
2009-04-25  1:44           ` Yue Wang
2009-04-25  9:39             ` Mojca Miklavec
2009-04-25 11:18               ` Yue Wang
2009-04-25 11:49                 ` Mojca Miklavec
2009-04-25 12:43                 ` Hans Hagen
2009-04-25 13:33                   ` Yue Wang
2009-04-25 13:41                     ` Hans Hagen
2009-04-25 14:07                       ` Yue Wang
2009-04-25 14:09                         ` Mojca Miklavec
2009-04-25 14:13                           ` Mojca Miklavec
2009-04-25 14:13                           ` Yue Wang
2009-04-25 16:18                           ` Hans Hagen
2009-04-25 14:15                         ` Mojca Miklavec
2009-04-25 14:31                           ` Yue Wang
2009-04-25 16:19                             ` Hans Hagen
2009-04-25 18:06                               ` Mojca Miklavec
2009-04-25 18:17                                 ` Hans Hagen
2009-04-25 16:18                           ` Hans Hagen
2009-04-25 16:17                         ` Hans Hagen
2009-04-25 14:08                     ` Mojca Miklavec
2009-04-25 16:15                       ` Hans Hagen
2009-04-25 14:41                   ` Yue Wang
2009-04-25 16:21                     ` Hans Hagen
2009-04-25 12:14               ` Taco Hoekwater
2009-04-25 13:27               ` Hans Hagen
2009-04-24 20:29         ` Mojca Miklavec
2009-04-25  1:08           ` Yue Wang
2009-04-25 11:45             ` Mojca Miklavec

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=68bfdc900904240433p3e47c85dj271b7452ceb0b94d@mail.gmail.com \
    --to=yuleopen@gmail.com \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).