On Thu, Mar 8, 2012 at 4:36 PM, Rob Oakes <lyx-de...@oak-tree.us> wrote:
> I'm sympathetic to this point. I understand that having a way to go from one 
> to the other is important. I've deliberately avoided creating an export to 
> Word option, though, because it would essentially require that I recode large 
> portions of LyX in Python. I'm resistant to doing that because it's a a lot 
> of extra code to maintain. There are already two implementations of LyX 
> document parsing libraries: eLyXer and that found in LyX itself. Adding a 
> third and trying to keep it in some sort of synchronization would be a huge 
> pain. I'm looking into using eLyXer for Word conversion from LyX, but that is 
> lesser priority than making Word import work correctly. (At least at the 
> moment.) If there is someone (maybe Alex or another eLyXer dev) who would be 
> interest in collaborating and handling the export part, I'd be happy to 
> coordinate with them so that we're able to round-trip.

That would be great. Unfortunately eLyXer is pretty much a solo
project at the moment, and I don't have the time (or even the
inclination) to do the job. But it might be a great project to have
someone else started on the eLyXer codebase, and I would provide all
the assistance needed to learn their way around. Interested parties
are encouraged to contact me if you
feel that you might want to tackle this project, always with Rob's coordination.


Reply via email to