The reverted patch was buggy, incomplete and did not solve the problem of
non-reproducible builds due to timestamps in rst2man output.
Debian could solve the problem with a patch setting the config value::
# Disables datestamp; equivalent to --no-datestamp:
datestamp:
in
That is, if you open such document in a modern browser, it will happily
download some JavaScript code from a remote site. I feel this violation
of our users privacy (and a security concern).
This depends on the browser settings of the user. Users concerned for
privacy and security will have
On 4.07.12, Julian Taylor wrote:
On 07/04/2012 01:56 PM, Guenter Milde wrote:
That is, if you open such document in a modern browser, it will happily
download some JavaScript code from a remote site. I feel this violation
of our users privacy (and a security concern).
This depends
Oh it would rock my world if the rst2* scripts could read options
from a configuration file...
But they already do! Since ages!
See http://docutils.sourceforge.net/docs/user/config.html
By default, Docutils checks the following places for configuration files,
in the following order:
When I see command name rst2latex, I understand immediately, that it
takes RST-code and outputs LaTeX-code.
...
And that's fine: rst2latex really works exactly as its name suggests.
Actually, it expects LaTeX2e and a pdfTeX engine in a version not earlier
than 2005-02-04 (see [1]). On a not
5 matches
Mail list logo
