Open dbrower opened 7 years ago
@matz-e Any ideas? This is in the corresponding section of the log file:
\pdfxsafeforxmp@toks=\toks16
LaTeX Warning: File `creationdate.lua' already exists on the system.
Not generating it from this source.
! Package pdfx Error: CreationDate is not properly supported;
PDF validation may fail..
See the pdfx package documentation for explanation.
Type H <return> for immediate help.
...
l.674 ...tput-driver="xdvipdfmx -z 0" <filename> }
? q
OK, entering \batchmode...
Package pdfx Warning: No implementation for \pdfxcreation. on input line 716.
Sorry, this hasn't popped up for me so far since I didn't test xelatex
that well. I barely use it since I migrated to lualatex
…
The documentation to pdfx
mentions that xelatex
needs to be run with -shell-escape
. Not the cleanest solution, but it works, short of removing the usage of pdfx
.
I ran into \pdfadjustspacing
, too, which trips up xelatex
, so I protected it to be only used with pdflatex
. I'm not sure what the effect on the other TeX engines is, the documentation/Q&A I've found on the command are pretty sparse.
If xetex
/xelatex
is different enough, maybe we don't support it? Even having lualatex
in addition to pdflatex
is a still a net gain.
I have never used xetex
, nor do I know much about it. It seems to cater to using unicode input and to support arbitrary system fonts. But luatex
also does both those things?
That's true, it may be wise to not support xelatex
. I found this w.r.t. feature comparisons. Since the question is already 4 years old, I ran the example locally. The spacing seems to have resolved and the other issue with the breve seems to be font dependent. Maybe this is too much of a niche?
lualatex
on the other hand is already used by some graph drawing packages, i.e., tikz
. If you don't want to have xelatex
support, I can remove the few if
s that are in the distribution already.
For reference, if someone is to dig this up, #6 was an attempt to solve this issue.
When compiling the example file with xelatex I get the following fatal error: