To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=77098
------- Additional comments from [EMAIL PROTECTED] Thu May 10 07:12:22 +0000 2007 ------- That can easily be. That's up to you to decide when you look up the code. Still even if the cause was the broken dictionary the office should not crash. If that can be done you have two choice - disable the broken dictionary or - run with whatever you mentioned to successfully obtain from it Since lingucomponent can hardly report errors in the UI (after all it can be called via the API only) I think disabling would be a good choice in that case one does at least know that something went wrong. The other way it remains unclear what works and what not. But the choice is left up to you. In any way I have confirmed that there should never be error messages printed to stderr or stdout. Ideally there should be an appropriate exception to report such a problem, but that is unfortunately missing and a RuntimeException should not be misused this way. --------------------------------------------------------------------- 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]
