What is the status for zip files and symlinks? Any solution
possible there?

Further development of this local feature was discouraged, because the
whole layout feature is likely to be overhauled, along with our XML
format change.

In my opinion, the lyx XML format would better mimic ooffice ODF
format in the sense that a zip file is used to hold .lyx, .layout,
.bst, .bib, embeded figures, and .cls file in some cases. A 'file
manager' can be used to allow users to add, remove, extract included
files. The overall goal: I should be able to open most of the .lyx
files I receive. This would greatly help the interchangeability of lyx
files.


I have not thought about this in great detail, but I would like to
have a file manager that

1. can add/remove files to .lyx

2. embedded file can have status 'auto', 'embedded' or 'external'
 'auto': (most of the times)
   * knows the location of external file
   * use embed file if no external file is found
   * can be extracted to disk (to allow external edition)
   * use external file if possible
   * embed external file when .lyx file is saved.
 'embedded':
   * does not know the location of external file
   * can be extracted or embedded manually
   * always use the embedded version
 'external':
   * do not embed file
   * always use external version

3. when a .lyx file is opened, it extracts itself to a temporary
directory and use embedded files according to the rules specified.
Briefly,
 * insert a figure will automatically embed it in 'auto' mode
 * .layout file is embedded, and a dialog can be used to modify it
(the module idea?)
 * .bst, .cls etc can be embedded by user request

4. A lyx -> odf converter to convert .lyx to ODF format so that
ooffice or word (?) can open it. Embedded figures are really embedded,
bibtex is run to get the reference list, cross reference etc are
expanded, .layout, .cls etc are removed. Such a conversionn would
greatly help the use of lyx. I guess back conversion would be much
more difficult and should be left for later.

It is almost post 1.5.0 time so I guess such discussion is allowed. :-)

Cheers,
Bo

Reply via email to