<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div style="-webkit-text-size-adjust: auto; "><span></span></div><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div style="-webkit-text-size-adjust: auto; "><span></span></div><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div style="-webkit-text-size-adjust: auto; "><span></span></div><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0); "><br></span><div style="-webkit-text-size-adjust: auto; "><font color="#000000"><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">My question was redirected here from the tex-live list because I'm told that this bug is XeTeX-specific.</span></font></div><div style="-webkit-text-size-adjust: auto; "><font color="#000000"><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);"><br></span></font></div><div style="-webkit-text-size-adjust: auto; "><font color="#000000"><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">I'm trying to generate PDF/X-1a2001 spec-compliant PDF files with </span></font><span style="background-color: rgba(255, 255, 255, 0); -webkit-text-size-adjust: auto; ">xetex/xdvipdfmx (xdvipdfmx-0</span><span style="background-color: rgba(255, 255, 255, 0); -webkit-text-size-adjust: auto; ">.7.8 from TeXLive 2012), and I'm running into </span><span style="background-color: rgba(255, 255, 255, 0); -webkit-text-size-adjust: auto; ">one small bug that I can't find a good way to work around. The xdvipdfmx</span></div><div style="-webkit-text-size-adjust: auto; "><font color="#000000"><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">backend is omitting the /ID field in the PDF trailer.<br></span></font></div><div style="-webkit-text-size-adjust: auto; "><br></div><div><font color="#000000" style="-webkit-text-size-adjust: auto; "><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">For spec conformance, if I understand correctly, this key must exist and must contain a unique value. It is usually computed as an </span></font><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0); ">array of two MD5 hashes of the body of the document, not including the </span><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0); ">trailer (presumably both containing the same value, given that it is a newly </span><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0); ">created file).</span></div><div style="-webkit-text-size-adjust: auto; "><span style="background-color: rgba(255, 255, 255, 0); -webkit-text-size-adjust: auto; "><br></span></div><div style="-webkit-text-size-adjust: auto; "><span style="background-color: rgba(255, 255, 255, 0); -webkit-text-size-adjust: auto; "><br></span></div><div style="-webkit-text-size-adjust: auto; "><span style="background-color: rgba(255, 255, 255, 0); -webkit-text-size-adjust: auto; ">Ideas?</span></div><div style="-webkit-text-size-adjust: auto; "><span style="-webkit-text-size-adjust: auto;">David</span></div></div></div></div></body></html>