Dear Jonathan and Will,<div>I suspected that there was some problem like this with the font management via fontspec: I will try to apply your hints.</div><div>thanks a lot!</div><div>A.K.</div><div><br class="webkit-block-placeholder">
</div><div>P.S. A MicroType support is what lacks for my happiness, but I know it is not among the priorities...<br><br><div><span class="gmail_quote">2007/9/14, Jonathan Kew <
<a href="mailto:jonathan_kew@sil.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">jonathan_kew@sil.org</a>>:</span><blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">
On 13 Sep 2007, at 10:15 pm, jadolov k wrote:
<br><br>> Actually, I use the standard xetex installation that comes with Tex<br>> Live 2007; I use the xdvipdfmx via the TexShop engine.<br><br>OK.<br><br>> But, unfortunately, the speed ratio is really the one I mentioned.
<br>> I thought it was the normal speed in TeX (since I always use<br>> xetex), but once I've tried pdfLaTeX and I have been astonished<br>> about the speed...<br><br>Well, it's true that if you use only "traditional" TeX fonts via TFM
<br>files, typesetting is faster... that's true also if you use xetex to<br>process such a document. There is a speed penalty for using Unicode/<br>OpenType fonts directly. But it shouldn't be *that* bad!....<br>
<br>
> I will provide an example file soon.<br><br>Looking at your example, I can't run it directly as it stands, as I<br>don't have all the same Adobe fonts. But I suspect that one factor,<br>at least, may be the way you're defining font features, using
<br>\addfontfeature within commands such as \bass, \prim,<br>\cftchapterfont, \@makefnmark, and many others. While \addfontfeature<br>can be handy, it makes the fontspec package and xetex engine work<br>very hard, constructing a new font specification (which involves
<br>considerable examination of the fonts available), even if it ends up<br>re-using the same final font as a previous time.<br><br>If you look in the .log file, you'll see many, many reports from<br>fontspec of the form:
<br>> Package fontspec Info: Defining font family for "Minion Pro" with<br>> options [Mapp<br>> ing=tex-text, Numbers={OldStyle,Proportional},,Numbers=<br>> {Monospaced,OldStyle}] o<br>> n input line 515.
<br>Each of these represents a relatively time-consuming operation, so it<br>would be good to minimize them.<br><br>It's much more efficient, therefore, to use fontspec's<br>\newfontinstance command to pre-define commands for any font
<br>instances you will be using frequently, and then use these within<br>your other macros.<br><br>(I see that Will has just responded with a similar comment while I've<br>been writing! But I'll go ahead and send this too.)
<br><br><br>JK<br>_______________________________________________<br>XeTeX mailing list<br><a href="mailto:postmaster@tug.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">postmaster@tug.org</a>
<br><a href="http://tug.org/mailman/listinf" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://tug.org/mailman/listinf
</a>o/xetex<br></blockquote></div><br></div>