On Fri, Feb 7, 2014 at 10:02 AM, Rainer M Krug <rai...@krugs.de> wrote:
> The idea would be that a round-trip framework is envisaged, which > provides the facilities to easily expand it from one export backend > (docx) to another (possibly odt? markdown?). This sounds like a sort of testing framework which would indicate for each export backend which features are exported and imported successfully. It would be cool to have some matrix showing how mature each of the supported formats is. >> >> Perhaps we could define the goals as: >> >> 1. Define a minimal-lyx feature set (I.e. the supported LyX/LaTeX features) > > Agreed. > >> 2. Write a corresponding lyx-layout > > As I said, non-supported formats / features should be available to the > user and handled gracefully, i.e. stored in a metadata file which will > be re-applied when re-iporting the round-trip file. > Would this also solve some of the LyX->LaTeX->LyX roundtrip issues ? > > Yes - although I see one problem which I could not find in any of the > .lyx <-> .docx : comments and track changes. These *have to be handled*. > I somehow have the feeling, that an inclusion of comments and track > changes into pandoc would be the best way forward... What is the problem you see ? Vincent
