Bug 76446

Summary: FILEOPEN: DOCX: incorrect rotation of VML shapes
Product: LibreOffice Reporter: Jacobo Aragunde Pérez <jaragunde>
Component: filters and storageAssignee: Not Assigned <libreoffice-bugs>
Status: NEW --- QA Contact:
Severity: normal    
Priority: medium    
Version: 4.2.2.1 release   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments: Test case
Side-by-side comparison

Description Jacobo Aragunde Pérez 2014-03-21 11:51:00 UTC
Created attachment 96156 [details]
Test case

Compare the look of the attached file opening it with Word and with LibreOffice; the rotation value is different.
Comment 1 Jacobo Aragunde Pérez 2014-03-21 11:52:27 UTC
Created attachment 96157 [details]
Side-by-side comparison
Comment 2 Jacobo Aragunde Pérez 2014-03-21 13:32:34 UTC
I opened the document with Word 2007 (which uses VML for the shapes) and the UI says the shape rotation value is 329. The rotation value inside the document is: rotation:-2050306fd

I did some changes to the document and saved it again. The newly generated document says: rotation:329

The "fd" modifier is the key but I don't know what it means and I find no examples nor references in the VML definition. 2.050306 radians are 117.47 degrees, which is a "similar" angle...

I think I generated this document with Office 2007, which usually saves the rotation in degrees, so this is a bit weird :P
Comment 3 Jacobo Aragunde Pérez 2014-04-04 17:50:22 UTC
(In reply to comment #2)
> I think I generated this document with Office 2007, which usually saves the
> rotation in degrees, so this is a bit weird :P

Now I know how it happened: I opened a Word 2010 document (like attachment #96913 [details]) with Word 2007 and saved it with a different name. It stored the DML shape as VML but with that weird angle format.

If you edit the angle of the shape and save again, it will be saved in degrees.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.