From: Martin Althoff <martin.althoff@yahoo.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: using \definebodyfont with multiple size declarations -- Why?
Date: Wed, 28 Jul 2010 02:08:04 -0700 (PDT) [thread overview]
Message-ID: <974039.831.qm@web56306.mail.re3.yahoo.com> (raw)
In-Reply-To: <4C4F416C.8080308@googlemail.com>
> Can you show me a example where simplefonts is so slow.
Sure, here goes.
I should say, most of my documents are 1-5 pages and build time is usually under 5 seconds (2nd and higher runs).
One (relatively) slow use of simplefonts is the Chinese example (1) below. The way I pasted it, it runs just under 13 seconds on 2nd and consecutive runs. Not using the adobe but eg the ht series is a whee faster.
It's not that I am doing huge amounts of Chinese, but jumping from, say, 3 to 12 seconds, is considerably slower. I was hoping by creating a typescript I could speed things up a bit. Any suggestions welcome.
Standing corrected, the impact using eg. CharisSIL for phonetic/IPA symbols the impact is much less: eg. a jump from 2.8 to 4.8 seconds in Example (2) given below. The impact of 2 seconds is bearable!
Let me know if you want to see any output or whatever.
cheers, Martin
%Example (1)
\usemodule[simplefonts]
\setmainfont[texgyrepagella]
\setsansfont[texgyreheros]
\setmonofont[texgyrecursor]
\setcjkmainfont[adobesongstd]
\setcjksansfont[adobeheitistd]
\setcjkmonofont[adobefangsongstd]
% ttf fonts htsong, hthei, htkai, htfs from:
% http://ftp.ctex.org/pub/tex/fonts/truetype/ttf/
%\setcjkmainfont[htsong] % serif, regular
%\setcjksansfont[hthei] % sans
%\setcjkmonofont[htsong] % mono
\setscript[hanzi]
\starttext
Where there is a will, there is a way.
我命由我不由天
\blank
{\rm Serif: 兡也包因沘氓侷柵苗孫孫財 text 兡也包因沘氓侷柵苗孫孫財}
%{\ss Sans: 兡也包因沘氓侷柵苗孫孫財 text 兡也包因沘氓侷柵苗孫孫財}
%{\tt Mono: 兡也包因沘氓侷柵苗孫孫財 text 兡也包因沘氓侷柵苗孫孫財}
\stoptext
% Example (2) - Not sure if the IPA symbols post properly...
\usemodule[simplefonts]
\setmainfont[CharisSIL]
\starttext
besser [ˈbɛsɐ], der [deːɐ]
d͡ʒ
\stoptext
___________________________________________________________________________________
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2010-07-28 9:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 9:36 Martin Althoff
2010-07-27 17:42 ` Hans Hagen
2010-07-28 9:47 ` Martin Althoff
2010-07-28 10:41 ` Hans Hagen
2010-07-28 10:46 ` luigi scarso
2010-07-28 10:54 ` Arthur Reutenauer
2010-07-29 1:35 ` Martin Althoff
2010-07-27 20:28 ` Wolfgang Schuster
2010-07-28 9:08 ` Martin Althoff [this message]
2010-07-28 9:20 ` Arthur Reutenauer
2010-07-28 9:20 ` Hans Hagen
2010-07-28 9:30 ` Martin Althoff
[not found] <4C4FFA8F.9000904@wxs.nl>
2010-07-28 9:50 ` Martin Althoff
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=974039.831.qm@web56306.mail.re3.yahoo.com \
--to=martin.althoff@yahoo.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).