Bug Hunting Session
Bug 66090 - FILEOPEN: MS 97 .doc Fails to import properly. Indent and placement errors
Summary: FILEOPEN: MS 97 .doc Fails to import properly. Indent and placement errors
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.1.0.1 rc
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-23 16:21 UTC by Luke
Modified: 2013-06-23 16:47 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
MS .doc file fails to import correctly (552.50 KB, application/msword)
2013-06-23 16:21 UTC, Luke
Details
Comparison of Doc in Word vs Writer (1.15 MB, image/png)
2013-06-23 16:25 UTC, Luke
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Luke 2013-06-23 16:21:35 UTC
Created attachment 81271 [details]
MS .doc file fails to import correctly

This bug was tested LibreOffice v4.1 RC1 running in windows 7 and XP. It appears that LibreOffice loses formatting when importing MS Word 2003 .doc files. I have attached an example.

Steps to reproduce the bug:
1. Open attached Demo-Hayden-Management.doc document in writer 
2. Open attached Demo-Hayden-Management.doc document in Word2003/Office 365
3. Compare the documents. 

There 5 major areas where the import fails. Should submit 5 separate reports for each one?
Comment 1 Luke 2013-06-23 16:25:03 UTC
Created attachment 81272 [details]
Comparison of Doc in Word vs Writer

Here I highlight the 5 major areas where the import fails.
Comment 2 retired 2013-06-23 16:47:26 UTC
Hi Luke,

thanks for taking the time to report this problem.

Could you please create separate bugs for each specific issue you notice? I can confirm that the layout looks different than in MS Word when opening in LO.

The general rule is one bug per problem. That's the best way to track duplicates and progress when something get's fixed. otherwise we'd have a bug with 60 comments and no obvious info which of the issues are remaining.

Setting this to INVALID. Please don't be discouraged. We greatly appreciate you taking the time to report this. And look forward to confirm your separate bug reports once they come in.

Best, james