Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#175 Inconsistent names of rst2*tex.py scripts

pending-remind
nobody
None
3
2011-11-10
2011-10-07
Jakub Wilk
No

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.)

Discussion

  • 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
    lualatex).

    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.

    However:
    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