On Fri, 2002-12-20 at 20:56, Jean-Marc Lasgouttes wrote: > >>>>> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes: > > Andre> On Fri, Dec 20, 2002 at 06:06:29PM +1030, Darren Freeman wrote: > >> Any objections? Comments? > > Andre> I'd rather make .lyx gzipped by default. Doesn't Staroffice do > Andre> something similar? > > We could have both the plain .lyx format and a compressed .lyz format.
Yeah I like the two format idea. Make .lyz default and maybe detect the extension when saving to decide what to do. Minimum UI impact, maybe add a tooltip to remind old timers about the new feature. > Or use the plain old .lyx.gz. Makes it obvious what the file is, at least. With a gzipped file, you don't even get the name of LyX in plaintext in the file. Somebody receiving a .lyz might not think to pipe it through gunzip to figure out what it is. > We could also do what emacs does: if the file is already compressed, > uncompress it and compress it back on saving. If it is not compressed, > leve it alone. Until LyX crashes =) Leaving you with the uncompressed format which you might not remember to convert back. Also theres the issue of emergency saving. I wouldn't want emergency saves to use zlib in case they don't succede. Hence you automatically need to be able to handle uncompressed files. One other question, is are we supporting LyX on platforms too slow to be expected to use compression? On a huge document, like a book, it might take a while. But then do we say that if you write a book, use a better computer? =) (hint: yes yes yes) > Andre> This is an extra burden for people like me who regularly do > Andre> search&replace in the .lyx file itself, but I'd guess that's > Andre> the minority. > > I would not be so sure about that. But it's not hard to decompress on the command line: gunzip x.lyx.gz ; kwrite x.lyz ; gzip x.lyx > JMarc Darren
