> They're not trying for anarchy. They're trying to kill any hope of > competition, as is shown by their track record. Destroy ODF, so that > their own proprietary formats become the only choice. >
Having ODF render differently in MSO and OOo will certainly help to destroy ODF. That is why I argue that OOo should render as MSO does. >> With the assumption that Microsoft's motives are to create anarchy, >> what should OOo do? Deliberately force incompatibility issues, or be >> compatible? >> >> > They want to make their formats appear to be the only usable choice. > Given all the open source projects that use ODF, it wouldn't take much > effort to see how others manage to be compatible. > So you leave it up to MS to code the interoperability? That does not sound wise. >> That is debatable, and it is unreasonable to assume that the player >> with 95%+ market share would look at any other implementation as a >> reference implementation. >> > That's the same as saying they get to decide the format for everyone. > This is the same company that periodically changes formats and forces > users to buy newer versions. Yes, the market leader gets to decide the format for everyone. That is, the market leader gets to decide the parts of the format not explicitly stated in the standards, for their market share of users. >>> If Microsoft wanted to change the format then they >>> should and are doing it in 1.2. >>> >> >> They did not change the format. >> >> > Read a bit more from Rob Weir. > I see that the MS effort is not 100% ODF compatible. Neither is the OOo effort. -- Dotan Cohen http://what-is-what.com http://gibberish.co.il --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
