Bug 68196

Summary: Writer does not read Indexes created in MS Word
Product: LibreOffice Reporter: UCLAgeek <scorp1979>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal CC: pje335-lo
Priority: medium    
Version: 4.1.0.4 release   
Hardware: x86-64 (AMD64)   
OS: macOS (All)   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: Screen shots of the errors
Word2013 example
Same doc as Word example, saved in Writer (+LO created index)
Screenshot.

Description UCLAgeek 2013-08-16 17:55:00 UTC
Created attachment 84150 [details]
Screen shots of the errors

Writer does not read indexes created in MS word. This also has the side effect of completely altering the page counts and positions. 

Document was created using: MS Word:MAC 2011 version 14.0 (100825)
system info:
OS: OSX 10.8.4
LibreOffice Version: 4.1.0.4
Comment 1 retired 2013-08-17 08:18:20 UTC
Any chance you could duplicate the document giving those errors, remove sensitive information and attach that for testing purposes? Otherwise it's very difficult to really solve this bug.
Comment 2 Luuk 2013-08-17 09:07:18 UTC
I created a simple example in Word2013  (Figuur 1.docx), 
saved the document,
and added the same index with writer (Figuur 1.odt)
Comment 3 Luuk 2013-08-17 09:07:59 UTC
Created attachment 84165 [details]
Word2013 example
Comment 4 Luuk 2013-08-17 09:09:03 UTC
Created attachment 84166 [details]
Same doc as Word example, saved in Writer (+LO created index)
Comment 5 UCLAgeek 2013-08-19 05:35:18 UTC
Created attachment 84222 [details]
Screenshot.
Comment 6 UCLAgeek 2013-08-19 05:36:28 UTC
Hi Luuk, 

I opened your document in Writer and got the same result as mine I attached a screenshot.
Comment 7 Thomas van der Meulen [retired] 2013-08-23 08:45:14 UTC
Thank you for your bug report, I CAN'T reproduce this bug running Version: 4.1.1.2
Build ID: 7e4286b58adc75a14f6d83f53a03b6c11fa2903 on Mac osx 10.8.4. 

seems to be fixed since 4.1.1.1 because I could reproduce this in 4.1.0.3, I recommend you to update to version 4.1.1.x ones it comes out to verify that it is fixed.