Debian Codegraph @

texmf-dist/doc/man/man1/xetex-unsafe.1

raw
1 .TH XETEX-UNSAFE 1 "20 November 2021"
2 .SH NAME
3 xetex-unsafe, xelatex-unsafe \- run xe(la)latex unsafely
4 .SH SYNOPSIS
5 .B xetex-unsafe
6 .RI [ xetex-options ]
7 .B xelatex-unsafe
8 .RI [ xetex-options ]
9 .SH DESCRIPTION
10 \fBxetex-unsafe\fP (\fBxelatex-unsafe\fP) runs XeTeX (XeLaTeX) unsafely;
11 specifically, using the \fBdvipdfmx-unsafe.cfg\fP configuration file.
12 .PP
13 As of TeX Live 2022, doing this is necessary only when running XeTeX on
14 documents using PSTricks features which require transparency. We strongly
15 recommend using Lua(La)TeX with PSTricks instead of XeTeX in this case.
16 .PP
17 At all costs, avoid using this, or any, unsafe invocation with documents
18 off the net or that are otherwise untrusted in any way.
19 .SH WHY?
20 You might well ask why using transparency features is unsafe in XeTeX.
21 The answer lies in the implementation history of Ghostscript, starting
22 as a PostScript interpreter before PDF was invented, when it was
23 acceptable to abort on an error, whereas with PDF, it must keep going.
24 The transparency operators, if abused in relation to this error
25 recovery, can cause internal inconsistencies in Ghostscript's state.
26 .PP
27 Thus, to be safe, we must disallow transparency with Ghostscript by
28 default. The \fBxdvipdfmx\fP backend for XeTeX calls Ghostscript under
29 certain circumstances, notably when using PSTricks.
30 \fB(x)dvipdfmx\fP itself is not a PostScript interpreter, which is
31 exactly what PSTricks requires.
32 .PP
33 Thus, to enable transparency, \fBxe(la)tex-unsafe\fP run XeTeX with
34 arguments to the \fBxdvipdfmx\fP backend (-output-driver="xdvipdfmx -i
35 dvipdfmx-unsafe.cfg -q -E") to use \fBdvipdfmx-unsafe.cfg\fP, which in
36 turn tells Ghostscript to enable the transparency operators
37 (-dALLOWPSTRANSPARENCY). They're disabled by default.
38 .PP
39 There have been further complications related to reading from the
40 filesystem, but as of TL22, these have been solved. The transparency
41 issue cannot be solved without a different Ghostscript implementation,
42 and the Ghostscript developers say they have no timeline for this.
43 .PP
44 To repeat the above: when using PSTricks and transparency, we strongly
45 recommend playing it safe and using Lua(La)TeX instead of Xe(La)TeX.
46 .SH OPTIONS
47 All command-line arguments except \fB--help\fP and \fB--version\fP are
48 passed to Xe(La)TeX.
49 .SH BUGS
50 For more about XeTeX: https://tug.org/xetex
51 .PP
52 For more about PSTricks: https://tug.org/PSTricks
53 .PP
54 Email for xe(la)tex-unsafe specifically: https://lists.tug.org/dvipdfmx