Hi all,
Gordon Burgess-Parker schrieb:
On 14/04/2010 21:44, Regina Henschel wrote:
Hi Lars, hi Jonathon,
Lars Nooden schrieb:
On 04/14/2010 08:14 PM, Regina Henschel wrote:
> not all of you are familiar with the problem.
The fact that MSO intentionally breaks ODF is very familiar to many,
perhaps everyone. That is not news.
It does not break ODF. The documents are valid ODF 1.1, at least our
validator [http://tools.services.openoffice.org/odfvalidator/] says
so. The users, who are forced by government or company policy to
produce ODF conform documents, can do this with Excel 2010. Therefore
I guess that there will be an increasing number of Excel-ods documents.
Hmmm. How do you work that one out?
I write an ods-document with Excel 2010 Beta and let the validator
examine it.
Open an ods file using the Sun ODF
plug-in in Excel 2007, everything is OK. Open an ods file natively in
Excel 2007 SP2 with it's alleged ODF compatibility and ALL the formulae
become values only
The start "Open an ods file" is not exact enough. There are Excel-ods
and Calc-ods. Both are valid ODF documents. You can work with Excel-ods
in Excel without problems and you can work with Calc-ods in Calc without
problems. But you get problems in Calc, when you open a Excel-ods document.
And you call that "not broken"? Are you REALLY saying that the Office
developers are so lacking in knowledge that they couldn't do what the
Sun developers did?
Come on!
The Excel-ods documents are surely valid ODF documents. If someone, for
example a government, demands the use of ODF documents, this can be done
with Excel-ods documents. That is the reason, why I suspect, that there
will be much more such documents in future.
The crucial point for me is not, what Excel does with Calc-ods
documents, but what Calc does with Excel-ods documents.
kind regards
Regina
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
