On Thu, Feb 27, 2014 at 9:18 AM, Richard Heck <rgh...@lyx.org> wrote: > On 02/27/2014 03:44 AM, Prannoy Pilligundla wrote: >> >> >> I also had a look at pandoc and tex4ht but as they are converters from >> Latex,i feel we should only consider them as secondary options. > > > I believe pandoc is pretty modular. One would only need to add LyX to the > list of formats that it handles and then, like magic, we could convert the > LyX format to anything else that pandoc handles. It seems to me that this > would be a very good approach. >
Well, pandoc handles LaTex already (although not very successfully in my tests. Management of citation, for instance leaves a lot to be desired), so all it's missing is a docx "reader" to make the back-conversion possible. That is, I understand pandoc to work this way: Reader module from format X produces ---> internal representation in pandoc format which is used by --> writer module to produce format Y So we would need to add a doc writer module and possibly a lyx reader module. I assume both would have to be written in Haskell (haven't really looked carefully into this). > The downside to any python-based approach, though, is that the LyX format is > a moving target. The script would need to be updated with every syntax > change. I assume this problem would persist with a pandoc approach, isn't it? The Lyx reader module would still be format-dependent, unless we go with LaTeX. Stefano -- __________________________________________________ Stefano Franchi Associate Research Professor Department of Hispanic Studies Ph: +1 (979) 845-2125 Texas A&M University Fax: +1 (979) 845-6421 College Station, Texas, USA stef...@tamu.edu http://stefano.cleinias.org
