>Aha! Caught you!
>
>There are some bugs mentioned in the reLyX man page. There's also a BUGS
>file in lib/reLyX in the distribution. Since then, there have been several
>gazillion messages about it, some of which I might be able to forward to
>you.
One single location of all the problems would make my life easier. There's
a reLyx section in the sourceforge bugs section and I guess that would be
the easiest thing for me to use. If people send me the problems via e-mail
I can put them in sourceforge.
>Seriously, if you poke around a bit and decide it' s not totally hopeless,
>I could go through my mail/relyx folder and find you a bunch more. I would
>be thrilled to know someone's taken over for my slacking, and a bunch of the
>hardcore LaTeXers on the list would be happy too.
I'm not a hard-core LaTeXer so I don't know how suitable a maintainer I'd
be. If the bugs are explained in detail I should be able to fix them, but
bug reports relying on detailed knowledge of TeX will go unfixed. :/
The perl style is different to mine so if I *did* take over maintenance I'd
have to spend a while restructuring it so I feel at home. If there are
more python programmers I think that that 'refactor' time could be better
spent rewriting reLyx in python (classes and functions should map over
rather simply). What are people's thoughts on this?
I think we should start centralising the reLyx problems, Amir's mailbox
sounds like the place to start and from there decide whether reLyx should
remain in perl or be changed to python.
Cheers
Koz
