On Wed, Apr 10, 2013 at 4:37 PM, Adrián Pereira <adrian.pere...@udc.es> wrote: > Absolutely, i didn't know about XSLT. > i'm actually forking lyx. Then i'll take a look at the code in the repo. > So, the problem is to find a schema for doing the translation between .lyx > and XML. If you have a Python script that does .lyx -> XML it's almost half > work done. I think that looking and studying both codes it'll be possible to > get some translate patterns. The hard work is to find this for everything in > lyx.
Look in the mail archives. There was some discussion of this but the developers (and I'm not a LyX developer) thought that XML export should be native in LyX and not via an external Python script. In particular there was no desire to maintain yet another script that embeds knowledge of the .lyx format (which isn't exactly stable), thus requiring even more pre-commit checking. I don't want to lead you astray here :) If you think the XML approach is better (I do) you may well actually have more work to do in some ways. As for XSLT making things easy, I agree, but first you have to feel comfortable with XSLT, and probably XSLT 2.0 at that. Also, as Pavel points out, you might still end up being more comfortable working on the existing XHTML export code than on XML export + XML style sheets. > Nico, are you a mentor? Cause maybe you could tell me some hint about where > i can start. Debugging something about this project or something. To get in > touch with the source and to increase my possibilities in GSoC. No, I'm not, but I can give you some hints. I'm not a C++ programmer, and I'm utterly unfamiliar with LyX source code, but you can find my XML export script here: https://github.com/nicowilliams/lyx2rfc/blob/master/src/lyx2xml and you can find some XSLs in that same repo. Nico --
