ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: showfont with xetex (syntax changed?)
Date: Thu, 06 Dec 2007 21:32:05 +0100	[thread overview]
Message-ID: <47585C45.3020705@wxs.nl> (raw)
In-Reply-To: <D946E6EB-2968-41CC-BC64-DD12803CE162@st.estfiles.de>

Steffen Wolfrum wrote:
> Am 06.12.2007 um 18:55 schrieb Hans Hagen:
> 
>> something like that ...
>>
>> keep in mind that you don't need to define a font then,
>>
>> {\setfontfeature{smallcaps}Some Text}
>>
>> will automatically give you that featureset so in practice we can do
>> with only a few real font definitions; mkiv keeps track of such  
>> dunamic
>> features and efficiently caches data;
>>
>> we sped up luatex + mkiv some 30% and when using dynamic features with
>> huge fonts (zapfino, arab, chinese) we can even gain more
> 
> 
> wow!!

gave us a good feeling too -)

luatex will always be slower than pdftex, if only because it has wide 
fonts, multi-directional typesetting etc; to some extend this can be 
compensatd by using less fonts, but then, more features also has a price

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
___________________________________________________________________________________


      reply	other threads:[~2007-12-06 20:32 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-06 10:26 Steffen Wolfrum
2007-12-06 11:32 ` Mojca Miklavec
2007-12-06 13:48   ` Hans Hagen
2007-12-06 14:30     ` Steffen Wolfrum
2007-12-06 14:37       ` Wolfgang Schuster
2007-12-06 15:50         ` Steffen Wolfrum
2007-12-06 17:33           ` Wolfgang Schuster
2007-12-06 17:58             ` Hans Hagen
2007-12-07 19:09         ` Hans Hagen
2007-12-09 12:13           ` Wolfgang Schuster
2007-12-10 12:09             ` Hans Hagen
2007-12-10 12:20               ` Wolfgang Schuster
2007-12-07 19:08       ` Hans Hagen
2007-12-06 16:30     ` Mojca Miklavec
2007-12-07  9:29       ` Hans Hagen
2007-12-07  9:33       ` Hans Hagen
2007-12-06 14:23   ` Wolfgang Schuster
2007-12-07 19:07     ` Hans Hagen
2007-12-06 15:43   ` Steffen Wolfrum
2007-12-06 16:09   ` Steffen Wolfrum
2007-12-06 16:35     ` Mojca Miklavec
2007-12-06 16:59       ` Steffen Wolfrum
2007-12-06 17:36         ` Wolfgang Schuster
2007-12-06 17:45       ` Wolfgang Schuster
2007-12-06 17:55         ` Hans Hagen
2007-12-06 20:14           ` Steffen Wolfrum
2007-12-06 20:32             ` Hans Hagen [this message]

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=47585C45.3020705@wxs.nl \
    --to=pragma@wxs.nl \
    --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).