To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=71757
------- Additional comments from [email protected] Thu May 7 17:40:56 +0000 2009 ------- I think that you can always bring OOo to crash or loop by insering useless content as "text". The question is, how to deal with it? How can we detect if something is text or just a bunch of bytes, especially if you don't know the encoding. Some options: - repeat type detection after the user has entered an encoding and then reject all files that still contain zero bytes or have lines with more than n characters - try a language guessing and reject all files that can't be detected; this way files could become rejected just because we don't check for their language, though we check for a lot of them - the assertions show us that at least deep below, in the text formatter, we detect that something is wrong, so at least here we could stop. But it seems that this is very late (insertion already done) and it might be tricky to recover from the detected error without creating new problems. The first two options have the advantage that they try to reject files before they are actually inserted So far I think the first option is the best one to start with. --------------------------------------------------------------------- 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]
