Harold Fuchs wrote:
On 27/06/07, jonathon <[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED] wrote:
> If an MS Office-compatible output format is crashing MSOffice, this
is a
bug and should be reported.
Want to explain how an OOo developer can fix a bug in MSO,
under Windows?
xan
jonathon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On the one hand, If OO is capable of producing something that can crash
Windows, perhaps it (OO) ought to be changed so it can no longer produce
that. That's self interest so OO doesn't get a bad reputation and it's a
job
for an OO developer.
On the other hand, under the conventional "full disclosure" philosophy
predominant in the field of computer security, if a way is found of
seriously compromising company X's product, company X is notified and given
a "reasonable time" to fix the problem after which, if no fix appears, the
details are fully and publicly disclosed. In this case, "company X" is
Microsoft.
Thus, IMHO, details of the document ought to be sent, confidentially in the
first instance, to both the OO development team *and* to Microsoft. I don't
know what constitutes a "reasonable time" - a month?
I think that the document should be sent as a bug report to OOo and then
to MSO. If it is an issue with MSO, then let them deal with it in the
public forum such as this. Heck, could make a press issue out of it.
"Open Source helps Microsoft."
On a side note, I have had MSO created documents crash Windows which
would open great in OpenOffice. :)
--
Due to the move to M$ Exchange Server,
anything that is a priority, please phone.
Robin Laing
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
