<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><DIV><DIV>On 1 Aug 2006, at 6:54 am, Toralf Senger wrote:</DIV><BLOCKQUOTE type="cite"><P><FONT size="2" face="Arial">The last option I see is to compile xdvipdfmx and let this program make the pdfs-like on w32.</FONT></P></BLOCKQUOTE></DIV>As Will says, the issue is that xdv2pdf does not support .vf files; this reflects the fact that xetex was primarily developed to work with unicode/aat/opentype fonts, and the "legacy" tex font support has not been such a high priority for me.<BR><DIV><BR class="khtml-block-placeholder"></DIV><DIV>But you have identified the right answer: check out the current xdvipdfmx code, and build and install this; then you can run</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV> xetex -output-driver="xdvipdfmx -q -E"</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>and the .vf fonts should work.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>The Mac support in xdvipdfmx is not completely finished (I think old "classic" Type 1 fonts in LWFN files will not work, for example), but it's working well enough that I hope to include a binary in the next xetex package, so that users can choose which driver to use. For most purposes, xdvipdfmx will be preferable (much faster; better legacy tex font compatibility), but there are some features it does not support (Quartz effects such as shadows and transparency; variation/multi-master fonts; not as many graphics file formats).</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>(In principle, it shouldn't be very difficult to add .vf support to xdv2pdf as well, but I doubt that I'll work on this any time soon -- if at all.)</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>JK</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><BR class="khtml-block-placeholder"></DIV></BODY></HTML>