To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=104660
                 Issue #|104660
                 Summary|Multiple attributes style:writing-mode= in content.xml
               Component|xml
                 Version|OOO310m11
                Platform|Opteron/x86_64
                     URL|
              OS/Version|Linux
                  Status|UNCONFIRMED
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|code
             Assigned to|jsi
             Reported by|relf





------- Additional comments from [email protected] Mon Aug 31 16:52:18 +0000 
2009 -------
This problem is similar to bug 48731. But I see it in OO Impress (OpenOffice.org
3.1.0 OOO310m11 Build 9399) under Debian/unstable.

OO Impress writes the attribute style:writing-mode= for the same object
in content.xml several times, resulting in a broken presentation file.

Here is a testcase.zip containing testcase.odp (working presentation) and
broken.odp (broken presentation with multiple style:writing-mode= attributes):

http://slil.ru/27937599

To reproduce:
1. Start OO Impress and load testcase.odp
2. "Save As..." it under a new name, say, result.odp
3. Close OO Impress
4. Start OO Impress and try to load result.odp
5. Observe reading error

The file result.odp should be identical to broken.odp

---------------------------------------------------------------------
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]

Reply via email to