Florent Rougon writes: > Bastian Kleineidam <[EMAIL PROTECTED]> wrote: > > > python2.1 (2.1.3-3) from sid > > py2texi.el is a generated file > > it is included in debian/patches/info-docs.dpatch > > the fixinfo.el is replaced by it, fixinfo.el is not run. > > OK, py2texi and fixinfo have nothing in common.
fixinfo is obsolete. py2texi is now included upstream. > > Dont know, seems that a lot of string-scanning and -replacing is done. > > Yes, it converts a TeX file (the official Python documentation is > written in TeX) to texinfo. This is a hack (just have a look at the > Commentary at the top). Converting TeX to anything without acting at the > TeX driver level is always hard (and/or not robust) and hackish. > > As it is only a build-dependency of python2.1, I can't see how it can be > a *real* problem. You don't build python packages on an embedded system. > Emacs packages are seldom updated (and you could put them on hold), so > bandwidth is not an excuse either. and it's even a Build-Depends-Indep dependency ... > Converting a hack to another hack with no strong reason nor fun is not > exactly what I dream of every night. > > So, I am not sure that such a conversion would be worth the time spent. > If despite all of this you still want to tackle on this task and have > some ELisp questions (I think it should be OK with Python ;-), feel > free to ask me, but don't count on me to do this. Sorry. somebody to volunteer for a pythonic conversion of the docs? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
