> It is an "Open Standard" with open flexibility written in. Anyone can > write an incompatible format but why would you unless the intention was > to create anarchy? >
With the assumption that Microsoft's motives are to create anarchy, what should OOo do? Deliberately force incompatibility issues, or be compatible? >> There are two choices: have a reference implementation or don't. Which >> do you think is better for the standard? > > We had a large list of programs already vcoexisting as a reference > implementation. 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. > If Microsoft wanted to change the format then they > should and are doing it in 1.2. They did not change the format. > All shall be well, and all shall be well, and all manner of things shall > be well > OT: Could you please explain this quote? I've seen it several times, yet I fail to see how the third part differs from the first two, or how the first two differ from each other. Thanks. -- Dotan Cohen http://what-is-what.com http://gibberish.co.il --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
