On 2013-04-23, Rainer M. Krug wrote: > Cyrille Artho <c.ar...@aist.go.jp> writes:
>> Sounds reasonable. I would recommend, though, that no information is >> duplicated across files. If LyX is used to edit a "pure tex" document, >> then a separate lyx-specific file should keep only additional >> information, to avoid duplication of contents. Also, the extra file >> would be kept under revision control as well, as there may be multiple >> LyX and multiple TeX users working on the same document. > Absolutely - duplication is bad, as it can (will?) lead to problems in > the roundtrip: if the info is changed in the tex (or docx) file and not > in the lyx-specific file, there will be problems on re-import. I don't think there is need to remove the content from the lyx file if it is exported to LaTeX (or any other format). Instead, re-import should be in two steps: 1. conversion to LyX format with default values for LyX-internal settings. 2. merging with the "old" .lyx file, where customized LyX-internal settings will replace the defaults if appropriate. Note, that even with a "contentless" specific .lyx file you will need some means of aligning the stored values to the right place in the re-imported document and care for added or removed objects that (may) have such settings. > Let me re-iterate another point which was made earlier (unfortunately I > don't remember the thread): these discussions are effectively > independent of the second format in the round-trip: if it is tex, docx, > rtf, even txt - the basic discussion is the same. What is different, is > a) the set of features which can be maintained in the target format > (tex, docx, rtf, txt even, ...) > b) the actual creation of the content file (tex, docx, rtf, ...) > If this is designed right, I think one get an incredibly powerful > framework which can easily be extended to be used for other text > formats. This even more speaks for keeping the complete lyx file and postponing the merging to the re-import: otherwise we would require one contentless "lyx-special" file per target format. Günter
