Bug 68432 - MS WORD conversion error with numbering
Summary: MS WORD conversion error with numbering
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.1.1.2 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-22 13:12 UTC by Orwel
Modified: 2014-07-25 09:45 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
File was created in LO - numbering was TimesNewRoman, opened and saved in MSO2010 - broken numbering (32.00 KB, application/msword)
2013-08-22 13:12 UTC, Orwel
Details
original file created from own template (16.30 KB, application/vnd.oasis.opendocument.text)
2013-08-22 13:12 UTC, Orwel
Details
original .odt saved as .doc in LO (19.50 KB, application/msword)
2013-08-22 13:13 UTC, Orwel
Details
original odt saved as docx in Lo (7.44 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2013-08-22 13:14 UTC, Orwel
Details
docx file resaved in MS-O with no problems of reading in LO (18.85 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2013-08-22 13:15 UTC, Orwel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Orwel 2013-08-22 13:12:06 UTC
Created attachment 84452 [details]
File was created in LO - numbering was TimesNewRoman, opened and saved in MSO2010 - broken numbering

If I use in .odt file numbering (customized is Position and options) and save the file as *.doc, reopen it in Ms Word (2010), save it and reopen it in LO, the numbering charakter format changes from Times new roman to Wingdings (or Symbol) and has to be manually changed back to TNR.
These causes a lot of problems if you work on one document with somebody who uses MSO.

I add 4 files. 
1. Files is original clear .odt file I use from a self-created template. 
2. File is the same file saved as .doc in LO.
3. File is the same file saved as .docx in LO.
4. File is reopened and saved file .doc in MS-O 2010. - IF YOU OPEN THIS FILE IN LO, you can see how the format of numbering has changed.
5. File is reopened and saved file .doc in MS-O 2010.

Summary:
1. Open a clear .odt file.
2. Use numbering (I think and hope it should not depend on customized numbering or customized template).
3. Save the file as *.doc.
4. Open it in MS-O and SAVE IT.
5. Reopen the file in LO.
Comment 1 Orwel 2013-08-22 13:12:50 UTC
Created attachment 84453 [details]
original file created from own template
Comment 2 Orwel 2013-08-22 13:13:40 UTC
Created attachment 84454 [details]
original .odt saved as .doc in LO
Comment 3 Orwel 2013-08-22 13:14:24 UTC
Created attachment 84455 [details]
original odt saved as docx in Lo
Comment 4 Orwel 2013-08-22 13:15:10 UTC
Created attachment 84456 [details]
docx file resaved in MS-O with no problems of reading in LO
Comment 5 Joel Madero 2014-07-21 03:43:42 UTC
Cannot confirm with:
Ubuntu 14.04 x64 and Windows 7
LibreOffice 4.3.0.2 rc & Microsoft Office 2010

I downlaoded the original file, opened with LibreOffice 4.3 rc, saved a new copy as a .doc, opened it with MSO 2010, saved it as a new filename same extension (.doc), then opened the new file with LibreOffice 4.3 rc. Everything looks right.

Setting as WFM - if you can reproduce with 4.3 rc (or release when it comes out shortly) set to UNCONFIRMED again and I'll have another person test. Thanks!
Comment 6 Orwel 2014-07-21 08:42:18 UTC
Thank you for checking my post.
I have repeated the test.
I can confirm in Win7/LO 4.3.0.2/MS Off2010 the problem is less significant than in the past. But I do not think it is fully solved. In the origin document the numbering (as the whole text) is Times New Roman. After saving the .odt file to .doc/ opening it in MSO2010 and adding and deleting something in the text (I have track changes on), re-saving it in MS Office and opening in LO again, the numbering format changes to Liberation Sarif (if you click on the numbering you can see it) although the text itself remain in TNR. So the good new is, the font does not change to Symbol anymore, but I think the numbering font should not be changed neither. 
Let's continue...If you change manually the Liberation Sarif numbering font in .doc document in LO again to TNR, save it, open it in MS Office and save it again, now the font remains TNR also when opened in LO (BUT only the level you have manually changed in previous step, the next sub level - if not changed to TNR - still changes to Liberation Sarif). 

IMPORTANT! THIS DOES NOT HAPPEN TO DOCX file, the numbering font remains TNR if you reproduce the same steps as with the .doc.

I am not sure if this is enough to re-open the bug, but will do it so you can take a look at it one more time. If you think it should be even though closed be free to do so.
Thank you.
Comment 7 retired 2014-07-25 09:45:33 UTC
I think this is WORKSFORME.

Tested on OSX 10.9.4 LO 4.3RC3

Resaved .doc with Word 2011 as another .doc file. Reopen with LO still all test is Times New Roman.

Not sure what's going on on Windows. But also I'm not sure if, maybe this is a Word issue (since saving it with Word, seems to break things). Could be LO not correctly importing as well of course.

To keep things clean, since the original bug was solved and has dramatically improved (obviously this no longer even is a problem on OSX, linux) I suggest opening a new bug for the remaining problem if you are bothered by it.

Thanks for your feedback!