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: Sat, 25 Apr 2009 22:31:53 +0800	[thread overview]
Message-ID: <68bfdc900904250731n327c7b2cwc64c50c242536e5@mail.gmail.com> (raw)
In-Reply-To: <6faad9f00904250715s54f05d2m92bd53d8a8517e98@mail.gmail.com>

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.

Yue Wang
___________________________________________________________________________________
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-25 14:31 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
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 [this message]
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=68bfdc900904250731n327c7b2cwc64c50c242536e5@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).