ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Steffen Wolfrum <st.wolfrum@estfiles.de>
Subject: Do typescripts slow down ConTeXt?
Date: Sun, 28 Sep 2003 13:44:38 +0200	[thread overview]
Message-ID: <a05210600bb9c75b5c37c@[217.184.8.20]> (raw)

Hi,

since I switched from LaTeX to ConTeXt I am wondering why ConTeXt (actually pdfeTeX, Version 3.14159-1.10b-2.1 (Web2C 7.4.5) \write18 enabled) gets so extremely slow when I use my own PostScript font.

Here is my little statistics (ConTeXT with default/my font - the same in LaTeX):

1)  \starttext
    W619Q
    \stoptext

(5 seconds)

2)  \usetypescriptfile[type-agaramond]
    \usetypescript[AGaramond]
    \setupencoding[default=ec]
    \setupbodyfont[AGaramond,10.5pt]%

    \starttext
    W619Q
    \stoptext

(12 seconds)

3)  \documentclass{book}
    \begin{document}
    W619Q
    \end{document}

(less then 1 second)

4)  \documentclass[pdftex]{book}
    \usepackage[T1]{fontenc}
    \usepackage{textcomp}
    \usepackage[scaled,osf]{xagaramon}
    \begin{document}
    W619Q
    \end{document}

(1 second)

So it's 12 seconds compared to 5 seconds (or just 1 with LaTeX).
Is this normal?

Do I have a good chance that my typescript (see below) could be speeded up,
or is this -unfortunately- the regular way ConTeXt deals with PostScript fonts?


I'd be very happy for any help,

Steffen


"type-agaramond.tex" (for AGaramond Type1):

\usetypescriptfile[type-buy]
%
\starttypescript [serif] [agaramond] [ec]
  \definefontsynonym [AGaramond-Regular]        [padr9e]  [encoding=ec]
  \definefontsynonym [AGaramond-Italic]         [padri9e] [encoding=ec]
  \definefontsynonym [AGaramond-Bold]           [padb9e]  [encoding=ec]
  \definefontsynonym [AGaramond-BoldItalic]     [padbi9e] [encoding=ec]
%  
  \definefontsynonym [AGaramond-Regular-OSF]        [padr9d]  [encoding=ec]
  \definefontsynonym [AGaramond-Italic-OSF]         [padri9d] [encoding=ec]
  \definefontsynonym [AGaramond-Bold-OSF]           [padb9d]  [encoding=ec]
  \definefontsynonym [AGaramond-BoldItalic-OSF]     [padbi9d] [encoding=ec]
%
  \definefontsynonym [AGaramond-Semibold]       [pads9e]  [encoding=ec]
  \definefontsynonym [AGaramond-SemiboldItalic] [padsi9e] [encoding=ec]
  \definefontsynonym [AGaramond-Semibold-OSF]       [pads9d]  [encoding=ec]
  \definefontsynonym [AGaramond-SemiboldItalic-OSF] [padsi9d] [encoding=ec]
%
  \definefontsynonym [AGaramond-RegularSC]         [padrc9e]  [encoding=ec]
  \definefontsynonym [AGaramond-SemiboldSC]        [padsc9e]  [encoding=ec]
  \definefontsynonym [AGaramond-RegularSC-OSF]         [padrc9d]  [encoding=ec]
  \definefontsynonym [AGaramond-SemiboldSC-OSF]        [padsc9d]  [encoding=ec]
\stoptypescript
%
\starttypescript [serif] [agaramond] [name]
  \usetypescript[serif][fallback]  
  \definefontsynonym [Serif]             [AGaramond-Regular]  
  \definefontsynonym [SerifBold]         [AGaramond-Bold]
  \definefontsynonym [SerifItalic]       [AGaramond-Italic]
  \definefontsynonym [SerifBoldItalic]   [AGaramond-BoldItalic]
  \definefontsynonym [SemiBold]          [AGaramond-Semibold]
  \definefontsynonym [SemiBoldItalic]    [AGaramond-SemiboldItalic]
  \definefontsynonym [SerifCaps]         [AGaramond-RegularSC]
  \definefontsynonym [SerifSemiCaps]     [AGaramond-SemiboldSC]
  \definefontsynonym [OldStyle]          [AGaramond-RegularSC-OSF]% the regular old-style figures are in the small-caps file
\stoptypescript
%
\starttypescript [AGaramond] 
  \definetypeface [AGaramond] [rm] [serif] [agaramond] [default] [encoding=ec]
\stoptypescript

             reply	other threads:[~2003-09-28 11:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-28 11:44 Steffen Wolfrum [this message]
2003-09-28 12:18 ` Patrick Gundlach
2003-09-29  8:52   ` Hans Hagen
2003-09-28 13:36 ` Henning Hraban Ramm
2003-09-29 10:39 Steffen Wolfrum
2003-09-29 11:37 Steffen Wolfrum

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='a05210600bb9c75b5c37c@[217.184.8.20]' \
    --to=st.wolfrum@estfiles.de \
    --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).