From: Stefan M. <sm...@oe...> - 2012-11-11 11:17:47
|
Hi all! 20 minutes ago Stefan Merten wrote: > I finally installed rst2pdf from the sandbox at > > https://docutils.svn.sourceforge.net/svnroot/docutils/trunk/sandbox/rst2pdf/ > > I also discovered > > https://docutils.svn.sourceforge.net/svnroot/docutils/trunk/sandbox/rst2pdf-rubber/ > > which seems to be extremely close to the other rst2pdf tree. > > However, neither of the two is probably the rst2pdf you are talking > about :-( . The one I tried follows the normal rst2* conventions and > uses `-o` for specifying an output encoding: > > --output-encoding=<name[:handler]>, -o <name[:handler]> > Specify the text encoding and optionally the error > handler for output. Default: UTF-8:strict. > > It seems that the rst2pdf you are talking about is not in the Docutils > SVN. > > @Developers: Any idea what is going on here? Ah, I think I found out. Robert Alsina seems to prefer to maintain an own project at http://rst2pdf.ralsina.com.ar/ which is not reflected in the sandbox. In this project the command line conventions do not follow the usual rst2* conventions and even collide with them. That is really, really bad. So I'm pretty much inclined to say: The behavior of `rst.el` conforms to the reStructuredText standards and thus should not be changed. Instead the external project should be fixed. A simple fix could be to make the `-o/--output` optional. Grüße Stefan |