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 : [email protected] / 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 via email to