> > > (AFAIK only kspread saved in raw XML).
> > 
> >   And kchart (unless something really major was changed since I wrote it). 
> 
> Hmm, right (of course - since kchart can have no child parts it made sense
> there). 
> 
> Should I revert this fix and simply make kspread always save in a KTar ?
> 
> -> we could define that hasToWriteMultiPart() should NOT depend
> on whether child objects are there or not, but ONLY on the application...
> Makes sense to me.
> 
> What do you think ?
> 
> (NOTE : this change doesn't prevent loading old files saved in raw XML, 
> by the way. The loading code still detects that.)

   I don't think there were too many charts saved this way. The main
usage of kchart is in kspread, but there it is a special relationship. I
would leave it as it is. 

        Lotzi