[odf-discuss] A story of TIFF

[Alex Hudson]

marbux wrote:
> Do you have proposal for mapping all of the ODF to Microsoft Office
> that does not require MIcrosoft's cooperation? Or any alternative to
> declaring an MS Office interoperability subset that can enable
> interop?

I think you're missing Daniel's point.

An "MS Office interop subset" is an interesting idea, but entirely 
beside the point: if OOo can generate ODF files that are too complex for 
MS Office to read, even with a "perfect" converter, that is too bad and 
maybe we want to address that. It's a different issue though: Daniel is 
talking about the MSO -> OOo ODF trip, not the other way around.

If the MSO converter generates ODF which is only 65% ODF and is 45% 
Microsoft binary-encoded-as-XML-stuff, that's not really ODF, and the 
ability to a. not lose that data and b. mark it "Here be Dragons" 
doesn't actually get you any further to understanding it, or having that 
data in _real_ ODF.

Given OOo gets 85% fidelity, by those figures, we're saying that OOo 
users would get better quality documents by swapping .doc files around 
rather than ODF. That's the problem: setting up proprietary ODF formats 
which only certain apps have any hope of reading. It's detrimental to ODF.

Alex.