Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | WW8: corrupt format leads to loop in import | ||||||
---|---|---|---|---|---|---|---|
Product: | Writer | Reporter: | signey <signey.john> | ||||
Component: | open-import | Assignee: | AOO issues mailing list <issues> | ||||
Status: | REOPENED --- | QA Contact: | |||||
Severity: | Trivial | ||||||
Priority: | P3 | CC: | issues | ||||
Version: | OOo 2.0.4 | ||||||
Target Milestone: | --- | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||
Developer Difficulty: | --- | ||||||
Attachments: |
|
Description
signey
2006-11-01 16:17:00 UTC
Created attachment 40227 [details]
the file
Not a P1. MRU->HBRINkM: the format may be slighlt corrupted. At least it is not possible to edit the table on page 2 in MS Word. Though, the import should not loop; it does not in OO 1.1.x. SBA->signey: Next time, please provide a short description and DO NOT paste such an amount of data into the description. Please have a look at http://qa.openoffice.org/issue_handling/basic_rules.html#attachments <QUOTE> "Use attachments where possible Don't paste large files into the description. For instance, if you're asked to provide a stack of a crash, copy this stack into a file, then attach this file. If you have some Basic macro or Java code which triggers a problem, copy it into a separate file, and attach this file." <UNQUOTE> Thank you for your comprehension. target 3.0 imports without loops on OOo 2.4 and up. Does not import the corrupted table though. Reopened as P3 - no crash, but faulty import *** Issue 95550 has been marked as a duplicate of this issue. *** May anyone make this bug for 3.1? In a kind of http://qa.openoffice.org/issues/show_bug.cgi?id=96567 I use ОО as a server for documents processing. And periodically employers load into system broken files. It stops a server, that it is difficult to watch. And causes many problems. Please. Reset assigne to the default "issues@openoffice.apache.org". |