dep : please don't use reply-to headers
It makes it difficult to reply to a message to the list.

> > probably because it is not exactly easy for users to look at the
> > koffice snapshots since the project was moved to kde 2.0 
> development.
> As I said, the fact that it uses XML is mentionned in the FAQ.
> 
> And the current snapshots work really fine, BTW. ;)
> 
> > |And yes, at saving time a tar.gz file is created with the 
> graphics added
> > |into it.
> > |Create a word document, save it (.kwd), run "tar xvzf" on 
> > the .kwd file, and
> > |behold :
> > |one XML file per part (including the main doc, of course), 
> > and pictures and
> > |the rest
> > |saved natively.
> > 
> > good. now, as i understand it, there's some sort of dynamic data
> > exchange possible within the koffice apps. 
> Ah - you refer to what we call "embedding" I suppose.
> 
> > if you'll forgive a very elementary question, 
> > how is this effected when i document is taken to
> > a machine that doesn't contain the parent documents? are all the
> > linked documents saved with the instant document in their entirety,
> > or only such portions as have been incorporated into the instant
> > compound document? (ie, nine cells from a 150x500 spreadsheet).
> Currently, the document that is embedded is an unnamed document.
> It is fully included in the saving of the parent one, and 
> doesn't exist
> as standalone on the disk. This is the most needed case I 
> think, the case
> where you have a graph in your spreadsheet, an vector image 
> in your text document,
> or in your presentation program, ...
> 
> The koffice libraries support saving references to external 
> document, but there 
> is currently no support in the user interface (nor even in 
> the apps) for that.
> 
> That's where input from users is helpful. Is this a needed feature ?
> How should it be handled exactly ?
> [One example of problems : what if the referred file has 
> moved or has been destroyed,
> or as you said if you copy the doc to a machine which doesn't 
> have the file]
> -> That's why it's not handled currently. Always the simplest 
> case first :-)

--
David Faure
faure@kde.org - KDE developer
david@mandrakesoft.com - Mandrake
david.faure@cramersystems.com - Cramer Systems