Steps

The local process converter compiles an exported LaTeX package by running a pdflatex installed on the XWiki server itself. PDF Conversion says when it is the one to choose.

1. Install the LaTeX to PDF Converter using local process extension. It does not come with the LaTeX exporter, which carries the Docker converter instead. In Administration > Extensions the plain search lists recommended extensions only and does not find it, so use Advanced search, with the extension identifier org.xwiki.contrib.latex:latex-pdf-process and the version of the LaTeX exporter you have installed.

   

2. Install a LaTeX distribution providing pdflatex on the server machine where XWiki runs. It has to be on the PATH of the process XWiki itself runs in, which is often narrower than the one your shell has; where it is not, name it by its absolute path in latex.pdf.process.commands.
3. Point the exporter at this converter in xwiki.properties, then restart XWiki: the file is read at startup, so nothing changes until you do.

   latex.pdf.export.hint=process

   latex.pdf.process.commands needs no change unless your installation compiles differently; Configuration Properties gives its default and how to override it.

4. Export a page to PDF (LaTeX). The job runs pdflatex on the server and offers the compiled PDF for download.

   

FAQ

The export fails. How do I see why?

Open the Job log of the failed export: it holds the output of the pdflatex run, or the command that could not be executed at all. The PDF (LaTeX) entry is offered even where pdflatex is missing, for the reason given in PDF Conversion.

Is there a time limit on a conversion?

Yes. A command that has not returned after one hour is killed and the export fails.

Related

• PDF Conversion
• Configure PDF Conversion with Docker
• Configuration Properties