ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Bryant Eastham <beastham@pewla.us.pewg.panasonic.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Speed of texexec with Unicode TrueType Font
Date: Sat, 23 Jan 2010 10:48:04 +0000	[thread overview]
Message-ID: <9B8AEA80E937434D9720A1330A8C18760A223D@exch.pewla.com> (raw)


[-- Attachment #1.1.1: Type: text/plain, Size: 1067 bytes --]

All-

Apologies if the question should go to another list - let me know if so.

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.

Is there a way to optimize the process?

Thanks,
-Bryant

[Panasonic]





Panasonic Electric Works Laboratory of America - SLC Lab
4525 So. Wasatch Blvd., Suite 100, 84124
Salt Lake City, UT 84124



T 801.993.7124
F 801.993.7260
beastham@pewla.us.pewg.pansonic.com

Bryant Eastham
Chief Architect


[Panasonic]


[-- Attachment #1.1.2: Type: text/html, Size: 10240 bytes --]

[-- Attachment #1.2: image001.gif --]
[-- Type: image/gif, Size: 3779 bytes --]

[-- Attachment #1.3: image003.gif --]
[-- Type: image/gif, Size: 2360 bytes --]

[-- Attachment #1.4: image004.png --]
[-- Type: image/png, Size: 168 bytes --]

[-- Attachment #1.5: image005.png --]
[-- Type: image/png, Size: 168 bytes --]

[-- Attachment #2: Type: text/plain, Size: 486 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

             reply	other threads:[~2010-01-23 10:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-23 10:48 Bryant Eastham [this message]
2010-01-23 11:10 ` Taco Hoekwater
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=9B8AEA80E937434D9720A1330A8C18760A223D@exch.pewla.com \
    --to=beastham@pewla.us.pewg.panasonic.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).