As I was one of the ones who initially raised this issue, let me coment on it.
On 02/06/14, 18:35 , stefano franchi wrote: > The first project in our wiki page for GSOC 2014: > > http://wiki.lyx.org/GSoC/GSoCProjectIdeasFor2014 > > is, at the same time, the most ambitious and the least well-defined > (possibly because the former implies the latter). Exactly - this was thought of as a starting point to develop a GSoC project - so it is not complete, but could also be split into different aspects which can be treated separately. > > It is not clear to me if this a coding project or if it defines the > outline of a preliminary non-coding feasibility study that would, at > most, produce a document describing the minimal-lyx and minimal-docx > feature sets (plus, possibly, a minimal-lyx-layout and a > minimal-doc-template). Well - the entry is about the mainly non-coding framework, and the project would be about implementing it. > > Any thought on how to make it more focused? 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?). IMPORTANT: this would NOT change ANYTHING in the existing export / import features, as these are geared to export / import the documents as good as possible, with maintaining as many features as possible in the document. The round-trip would guarantee that: A document authored in LyX would result in a e.g. docx with a LIMITED set of features, but that a re-import would result in the SAME .lyx file. features and formats not supported by the backend should be stored in a metadata file. The important point here is *limited set of features*! In addition, the framework should be easily, possibly only by using config files, able to be extended to other formats. > > 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. > 3. Define a minimal-doc feature set (Word/ODF features corresponding to (1) Yes - but these have to be the same as in 1). > 4, Write a Word/OO template (the set of styles corresponding to 2) Might be a good idea. > 5. Provide an automated path from 1 to 4 and back using glue-code and > existing internal and external tools (e.g.: LyX export functions to > XHTML/EPub, eLyxer, pandoc, writer2latex, etc). 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... > > I am not sure points 1-5 above capture the existing description, partly > because I am not sure about what is meant by "develop a framework". > Perhaps my summary caputeres the subgoal only? Well - "framework" in the sense that the coded "framework" would not be specific to .lyx <-> .docx but that it would be applicable to other export backends as well: Roundtrip from lyx: .lyx --> extract non-maintained formats / features and store these in metadata / sidecar file (based on converter X) --> convert .lyx to .??? using converter X .??? and back after the .??? has been edited: .??? --> extract non-maintained formats / features and store these in metadata / sidecar file (based on converter Y) --> convert .??? to .lyx --> apply formats from metadata / sidecar file .lyx and back to .??? after editing: .lyx --> extract non-maintained formats / features and store these in metadata / sidecar file (based on converter X) --> convert .lyx to .??? using converter X --> it would be great if there is a way of applying the sidecar file, but I think this won't be possible .??? Hope this clarifies some questions, Rainer > > 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 > > [email protected] <mailto:[email protected]> > http://stefano.cleinias.org -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Stellenbosch University South Africa Tel : +33 - (0)9 53 10 27 44 Cell: +33 - (0)6 85 62 59 98 Fax : +33 - (0)9 58 10 27 44 Fax (D): +49 - (0)3 21 21 25 22 44 email: [email protected] Skype: RMkrug
signature.asc
Description: OpenPGP digital signature
