Another possibility is that besides the notorious M$ code bloat, Ooo files actually consist of several files stored in a compressed archive. So when you click on an .sxw file, for example, this file as a compressed archive of several files, resulting in smaller file sizes. It's one of the advantages of Ooo. This can be see most clearly by adding an Ooo file to a standard compmression utility such as WinZip or WinRAR. When you extract it from that archive you'll get the constituent files rather than the single .sxw file.
HTH, MM -----Original Message----- From: Robin Monks [mailto:[EMAIL PROTECTED] Sent: Monday, February 21, 2005 2:30 PM To: [email protected] Subject: Re: [users] Growing MS files I would immediately suspect propriety compression systems in M$ and probably OOo saved the file to work on all M$ versions whereas M$ products themselves save for their own version. Robin Monks MozNetwork On Mon, 21 Feb 2005 19:26:29 +0000, Brian Blandford <[EMAIL PROTECTED]> wrote: > Not a problem - just curious to know. > > The other day I received a MS spread sheet which I was required to > amend and then return. There was no problem in opening it in OOo, > making some very minor amendments, and then sending it back in MS > format. But what surprised me was the the MS file I sent back was > considerably bigger than the one I received. > Why would that be? > > Brian B. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
