To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=49553
------- Additional comments from [EMAIL PROTECTED] Sun May 22 01:12:54 -0700 2005 ------- There is a balance to find between helping the user to work around an exception and gathering useful information for the engineering to understand the issue. My perception is that in this particular instance, we are nowhere: - The exception does not spot the problem back to a malformed content.xml, so the report is of little help. - The user has lost its work, anyway. So my feeling is that the exception should be better catched, at least for the engineers, since it can't help the user. Having said that, I have succeeded in rescueing the document: - There were a missing *opening* <text:ruby-base> tag and a missing *closing* <text:p> tag. I'm not sure how this can help. Thank you for your time and efforts, Jean-Pierre --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
