Dear fellow XeTeXnicians -- I am, for the first time ever, trying to produce a
XeTeX-generated PDF that is PDF/X-1A compliant. I am /nearly/ there, but
stumped by the need to add pdftitle and pdfinfo. Were I to use XeLaTeX, I see
that I could use :
\hypersetup
{%
pdftitle = {DocTitle}
Thank you Apostolos -- I will try that and report back.
Philip Taylor
Apostolos Syropoulos wrote:
> I would use something like the following;
>
> \special{pdf: docinfo <<
> /Author (John Holmes)
> /Title (Math Everywhere)
>
> >>}
>
> Apostolos
---
Apostolos Syropoulos wrote:
> I would use something like the following;
>
> \special{pdf: docinfo <<
> /Author (John Holmes)
> /Title (Math Everywhere)
>
> >>}
Sadly not, Apostole -- as far as Adobe Acrobat pre-flight checks are concerned,
> \special {pdf: docinfo <<
>
> /Author (Joh
Hi Philip,
you have a space between a slash and ModDate. This is a syntax error
(<< >> require key/value pairs) and this may be the reason why the
contents is ignored.
Zdeněk Wagner
http://ttsm.icpf.cas.cz/team/wagner.shtml
http://icebearsoft.euweb.cz
2016-07-10 13:43 GMT+02:00 Philip Taylor :
>
Oops, missed that Zdeněk , but even after correcting the error the diagnostics
remain the same. I have a work-around (I generate a one-page PDF using
XeLaTeX with the necessary metadata and then append the real PDF); the result
is PDF/X-1A compliant, but the printer will have to be instructed
On 10/7/16 13:28, Philip Taylor wrote:
Oops, missed that Zdeněk , but even after correcting the error the
diagnostics remain the same. I have a work-around (I generate a
one-page PDF using XeLaTeX with the necessary metadata and then
append the real PDF); the result is PDF/X-1A compliant, but
Jonathan Kew wrote:
> [Y]ou could generate a minimal .xdv file with xelatex (using -no-pdf) and
> then examine this with a binary-capable editor/viewer to see what pdf
> specials have been inserted. Then write plain-based code to generate the same
> in your xetex document.
Thank you Jonathan -
I have the following code in zwpagelayout.sty:
\edef\zwpl@pdftitle{\zwpl@title}
\ifcat$\zwpl@pdftitle$
\ifzwpl@pdfx
\ifcase\zwpl@Driver
\or
\pdfinfo{\zwpl@pdfinfo}
\or
\ifxetex \def\zwpl@crt{XeTeX}\else \def\zwpl@crt{TeX+dvipdfm}\fi
\edef\zwpl@pdfcrt{ /Creator (\zwp
Philip Taylor wrote:
> Thank you Jonathan -- that may have led me to a solution. I could generate
> the .xdv with no problem, but even looking at it using DVIASM did not give me
> sufficient information to work out what \specials might exist. So instead I
> added the following to my XeLaTeX
Philip Taylor wrote:
> I am completely confused in that I am no longer seeing the XML metadata in
> the PDF file even having (a) commented those two lines out, and then (b)
> replaced the entire LaTeX source with a clean copy taken from the web.
> Probably too tired to think straight :-(
OK,
Just to summarise (for the benefit of archives and posterity), the following is
/almost/ sufficient to achieve PDF/X-1A:2003 compliance using plain XeTeX.
Full compliance can be achieved using Adobe Acrobat.
> \newif \ifpdfxa
> \pdfxatrue
>
> \ifpdfxa
> \special {pdf: put @thispage << /ArtBo
Hi Phil,
On 10/7/16 18:40, Philip Taylor wrote:
The caveats are as follows :
1. a hook will need to be inserted into \shipout to insert the bounding
boxes on each page;
2. the colours will need to be converted to the desired output profile
using Adobe Acrobat;
3. the file will need t
Thank you Jonathan; a great improvement, and one much appreciated.
Jonathan Kew wrote:
> You could avoid the untidiness of #5 if you hook in \setboundingboxes
> differently, such that it's actually inserted into what is being shipped out,
> rather than added to the MVL to become part of the next
Hi Phil,
On Jul 11, 2016, at 3:40 AM, Philip Taylor
mailto:p.tay...@rhul.ac.uk>> wrote:
Just to summarise (for the benefit of archives and posterity), the following is
/almost/ sufficient to achieve PDF/X-1A:2003 compliance using plain XeTeX.
I note the /almost/. :-)
Full compliance can be
14 matches
Mail list logo