Jim Harris wrote:
How is it possible to blame a software crash on data input? Is not one of the rules of good software (which, of course, OOo is) that it must detect bad input, e.g. the "problem with the document", provide a rational response (e.g. fix it, explain it), and keep going?
Is a software crash, other than one induced by an error in the underlying platform and/or OS, _ever_ an acceptable response to _any_ problem?
Jim
[EMAIL PROTECTED] 2:26 AM 5/8/20078/2007 >>>
Hi Gary,
first of all, this isn't the correct mailing list to discuss bugs in
OOo. Please discuss this in [EMAIL PROTECTED], there you will get
the help you needed.
I took a look into our data base for stacktraces. I could found only one
with your email address and this stack looks like a problem with the
document and not with the system.
If it isn't possible for you to write a issue in IssueTracker for your
problem, please send me in a private mail a document, which crashes on
your system.
Here are some links for QA on OOo :
QA pages on OOo :
http://qa.openoffice.org/
Information how to write a bug :
http://qa.openoffice.org/ooQAReloaded/ooQA-ReportBugs.html
IssueTracker :
http://qa.openoffice.org/issue_handling/pre_submission.html
Thorsten
The .sxw file that repeatedly crashed when attempting to save it to .odt
was the style guide drafted in 2003 (written by the OOo doc team for
their docs)... It eventually "took" after a dozen tries.
Gary
