From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Speed of texexec with Unicode TrueType Font
Date: Sat, 23 Jan 2010 12:10:44 +0100 [thread overview]
Message-ID: <4B5AD934.7090605@elvenkind.com> (raw)
In-Reply-To: <9B8AEA80E937434D9720A1330A8C18760A223D@exch.pewla.com>
Bryant Eastham wrote:
> All-
>
> Apologies if the question should go to another list - let me know if
> so.
The pdftex list would have been better, but I think I can answer
anyway.
> I am using texexec with MSPMincho on a Japanese utf-8 document. I
> followed the instructions and it appears to work well.
> Texexec runs several passes, and on each pass spends a *long* time
> integrating each font "page". I get many lines saying:
>
> {<path to enc>/MSPMinchoXX.enc}<<path to tt>/MSPMincho.ttf>
>
> The time taken in this process is many times that of the rest of the
> conversion. The resulting PDF font properties lists "MS-PMincho
> (Embedded Subset), Type: TrueType, Encoding: Built-in" 75 times. I
> imagine that I am glad that the whole font is not included (for file
> size). However, during development it is painful to wait.
Large font support in pdftex is suboptimal: for each encoding block
of 256 characters, it has to reload and re-subset the complete ttf font.
It is unlikely this situation will ever improve, and the best option is
to switch to using one of the two new engines: xetex or luatex. This
will need different font commands from the ones you used for pdftex,
though.
Best wishes,
Taco
___________________________________________________________________________________
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-01-23 11:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 10:48 Bryant Eastham
2010-01-23 11:10 ` Taco Hoekwater [this message]
2010-01-23 11:12 ` Wolfgang Schuster
2010-01-23 13:19 ` Bryant Eastham
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=4B5AD934.7090605@elvenkind.com \
--to=taco@elvenkind.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).