ZapfDingbats is configurable in the default "Base Adobe fonts" section of XEP within the xep.xml configuration file. But default installations of XEP should already have this configuration.<br><br>Can you check whether he has the font installed on his machine? i.e. ask him to open up an application such as Word and check to see if he can see ZapfDingbats in the fonts dropdown list.<br clear="all">
<br>Regards,<br><br>Mark Cilia Vincenti<br>
<br><br><div class="gmail_quote">2009/5/13 Cutter <span dir="ltr"><<a href="mailto:cutter1994@gmail.com">cutter1994@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>I am using XEP (unsure of the version #) to create PDF from XSLT. The output looks correct on my system but when the client runs the same XSLT/FO (using a different version of XEP, unsure what #) none of the ZapfDingbats characters output. We have gone round and round about this but currently the client is coming back with “If the font is not embedded, the rendered file can only be viewed on systems that have the font configured for use with viewing or printing the application.” <br>
</div><div></div><div>My understanding is, once the PDF is rendered, and unless it is then reopened in some program capable of editing it, the PDF is set in stone. So any PDF viewer on any machine (Linux, Mac, Windows) with any (or no) fonts installed will show it as rendered. The problem with rendering the font is located on the machine doing the rendering not the machines later doing the viewing. Is this correct and could someone explain the quoted sentence above with an example?</div>
<div></div><div>What else might be making their rendering not output the correct fonts while my output (using the exact same transformations) renders correctly?</div><div></div><div>Thanks!</div>
</blockquote></div><br>