Re: [PATCH 1/3] Documentation/sphinx: let the user specify PDFLATEX and LATEXOPTS

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Am 02.11.2016 um 10:40 schrieb Jani Nikula <jani.nikula@xxxxxxxxx>:

> Refer to xelatex and latex options via variables. This allows the user
> to override the pdflatex and latex options to use on the make command
> line for experimenting. As a side effect, this makes the makefile a bit
> tidier.
> 
> Signed-off-by: Jani Nikula <jani.nikula@xxxxxxxxx>
> ---
> Documentation/Makefile.sphinx | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/Makefile.sphinx b/Documentation/Makefile.sphinx
> index 92deea30b183..1314e3ee31c4 100644
> --- a/Documentation/Makefile.sphinx
> +++ b/Documentation/Makefile.sphinx
> @@ -10,6 +10,8 @@ _SPHINXDIRS   = $(patsubst $(srctree)/Documentation/%/conf.py,%,$(wildcard $(src
> SPHINX_CONF   = conf.py
> PAPER         =
> BUILDDIR      = $(obj)/output
> +PDFLATEX      = xelatex

IMO, this is not a good idea since it could awakening expectations
we can not fulfill, even not for "experimenting" with 'latex'.

(pdf)latex and xelatex differ in many ways, e.g. pdflatex needs inputenc
and uses babel, while xelatex has utf-8 support and uses polyglossia.

 http://tex.stackexchange.com/questions/2984/frequently-loaded-packages-differences-between-pdflatex-and-xelatex

Thats why Mauros adds:

+# Don't mangle with UTF-8 chars
+'inputenc': '',
+'utf8extra': '',
+

to the conf.py 

 https://www.mail-archive.com/linux-doc@xxxxxxxxxxxxxxx/msg05182.html

Further IMO this way to use xelatex is just a "ugly hack", sphinx
itself has no xelatex support. E.g. the sphinx team added 
polyglossia only now:

 https://github.com/sphinx-doc/sphinx/commit/5af1713d604f54b1aaf9e35f9c0fb4433b0f6e7a 

The problem here is, that the sphinx team tries to extend a latex-writer
with some "xelatex" features, where a xelatex-writer is needed.
Another problem is, that Sphinx's TeX approach has no theming, this means
everything is placed in the sphinx.sty and there is no API for
a theming which is version compatible. Combined with the fact that we 
want support from Sphinx 1.2, we have also no chance to ship our
own sphinx.sty.

I'am working on such a xelatex-writer, addressing those aspects, but there is
a lot of work to do (will take months of my spare-time).

In short: Sphinx's TeX support is ugly, we should not try to support 
more variants than xelatex which was introduced by the patch from Mauro.

-- Markus --

--------

For those of us who are german readers, here is a good answer about
in what ways pdflatex and xelatex differ (sorry only in german):

 http://texwelt.de/wissen/fragen/5868/was-ist-der-unterschied-zwischen-latex-pdflatex-lualatex-und-xelatex 


--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux