Wolfgang- I can provide an example, but based on Taco's response it is unlikely to be of benefit. I have in the past tried more recent releases. I was not able to navigate the documentation and bugs to get something working. As this is merely an optimization issue, I can deal with the performance for now and (once things are all working) evaluate MkIV again in the future. Thanks, -Bryant -----Original Message----- From: ntg-context-bounces@ntg.nl [mailto:ntg-context-bounces@ntg.nl] On Behalf Of Wolfgang Schuster Sent: Saturday, January 23, 2010 8:12 PM To: mailing list for ConTeXt users Subject: Re: [NTG-context] Speed of texexec with Unicode TrueType Font Am 23.01.10 11:48, schrieb Bryant Eastham:
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.
Can you provide a example. Have you considered to use MkIV? Wolfgang ___________________________________________________________________________________ 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 ___________________________________________________________________________________