From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040518 Firefox/0.8 Description of problem: I'm trying to edit a word document in OO writer. The document has embedded MathType 5.0 equations. These appear as graphic objects as they should. However, when I delete them, it corrupts the document. Hitting "undo" after deleting will cause character deletions in unrelated parts of the document. It looks like the entire internal structure of the document gets hosed. Deleting one equation will end up deleting many paragraphs of text. I get weird overlapping insertions and deletions. You get the idea. I'm sure this is a tricky one to debug. MathType often screws up MS Word as well. Version-Release number of selected component (if applicable): openoffice.org-1.1.1-4 How reproducible: Always Steps to Reproduce: 1. Open MS Word document with embedded MathType 5 equations 2. Delete text in and around equations 3. Actual Results: Garbled document structure Expected Results: I just wish they would go a way.... :-0 Additional info:
Whole bunch of upstream MathType related bugs, one of which was: http://qa.openoffice.org/issues/show_bug.cgi?id=24340 Supposed to be fixed in upstream 1.1.2 (at least the looping), so you might want to give that a shot, to report back if it works - upstream 1.1.2 is currently in rc3, so you might want to give that a try to see if it fixes the issue - if it does, report back here! Thanks.
caolan->Tim: Can you attach an example of such a word document which I can play with to track the problem down ?
Seems to work fine in the current version of oowriter. I'll upload a document anyway. I don't remember if I fixed this version in word. Oops. Too big to make an attachment. Can I email it to you?
Sure, mail it to me.
Received document and verified that it's ok now. What I was concerned about was "tools->options->load/save->Microsoft Office->load/save convert MathType to OpenOffice.org Math". And checking if it was ok on both settings. But as you say it seems good now in both settings with OpenOffice.org 1.1.2-3. I do recall fixing a ole2 import resource leak which might have resulted in the dodgy reported behaviour