To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=70858 Issue #|70858 Summary|occasional corruption upon saving file containing ruby Component|Word processor Version|OOo 2.0.4 Platform|PC URL| OS/Version|Linux Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|save-export Assigned to|mru Reported by|lddubeau
------- Additional comments from [EMAIL PROTECTED] Wed Oct 25 08:07:08 -0700 2006 ------- The problem manifests itself while loading a file but the corruption is created while saving a file, hence the choice of "save-export" subcomponent. I do not know yet how to create the corruption. However, I have a file showing the corruption that I am going to attach to this bug report. Here is the procedure to follow to produce the error message and highlight the fact that oowriter produces incorrect XML when saving: [In the following all chinese characters have been replaced with XXX. Somehow, I can't get those characters to cut and paste properly from emacs to firefox. At any rate, the actual data is in the attached file.] 1. Open the file with oowriter. 2. You get the following error message: Read Error. Format error discovered in the file in sub-document content.xml at 2,116906(row,col). 3. Unzip the odt file and run xmllint on content.xml: $ xmllint content.xml content.xml:2: parser error : Opening and ending tag mismatch: p line 2 and ruby-base le-name="Ru1"><text:ruby-base/><text:p text:style-name="P2">XXX</text:ruby-base> 4. Open content.xml with your editor of choice. 5. Replace the following: <text:ruby text:style-name="Ru1"><text:ruby-base/><text:p text:style-name="P2">XXX</text:ruby-base><text:ruby-text>yan2</text:ruby-text></text:ruby> with: <text:ruby text:style-name="Ru1"><text:ruby-base>XXX</text:ruby-base><text:ruby-text>yan2</text:ruby-text></text:ruby> The offending text should be easy to find since there is only one empty text:ruby-base element in the entire file. (I search for "ruby-base/".) 6. Run xmllint again. There should be no problem reported by xmllint at this point (it will just output the entire file to stdout after delinting it). 7. If you rezip the content of the odt file after the editing above, it can be loaded by oowriter without problem. (So in effect, I'm also providing a workaround here.) I'm going to try to find a method to create the corruption at will but it may take a while. --------------------------------------------------------------------- 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]
