#175 Inconsistent names of rst2*tex.py scripts

Jakub Wilk

One of our (Debian) users noticed inconsistency in how rst2*tex.py are named.

Output of rst2latex.py is meant to be consumed to by latex, so the name makes perfect sense.
However, output of the other script, rst2xetex.py, is meant to be consumed by xelatex, rather than xetex as the name suggests.

(This inconsistency doesn't bother my personally, I'm just relying the message.)


  • Günter Milde

    Günter Milde - 2011-10-14

    I accnowledge that the naming is suboptimal and may contribute to the
    confusion about TeX engines vs. TeX macro extensions.

    Actually, the output of the xetex writer (and the rst2xetex.py front-end) is
    intended for use with either XeTeX or LuaTeX as engine and LaTeX macro
    extensions (command line commands for this are usually xelatex and

    An enquiry at comp.text.tex for a short name for a "Unicode enabled,
    OpenFont using TeX engine" resulted in (amongst others) the proposal lxtex,
    so maybe the frontend should/could be renamed to rst2lxlatex.py.

    Would this be easy to remember and use?
    Would we need a backwards compatibility symlink? If yes, for how long?

  • Günter Milde

    Günter Milde - 2011-11-10
    • priority: 5 --> 3
    • status: open --> pending-remind
  • Günter Milde

    Günter Milde - 2015-03-13
    • status: pending-remind --> closed
    • Group: --> sandbox
  • Günter Milde

    Günter Milde - 2015-03-13

    No reaction for 3 years. Closing this now.


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks