Bug 95967 - Formatting: bug when saving odt file in rtf
Summary: Formatting: bug when saving odt file in rtf
Status: RESOLVED DUPLICATE of bug 84832
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.0 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Miklos Vajna
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-21 10:00 UTC by Markus Mueller
Modified: 2016-07-22 21:28 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
original formatting in odt file (200.03 KB, image/png)
2015-11-21 10:00 UTC, Markus Mueller 		Details
formatting after export to rtf (208.24 KB, image/png)
2015-11-21 10:01 UTC, Markus Mueller 		Details
sorry, source file was missing ... (12.70 KB, application/vnd.oasis.opendocument.text)
2015-11-24 11:39 UTC, Markus Mueller 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Mueller 2015-11-21 10:00:35 UTC 
Created attachment 120697 [details]
original formatting in odt file

Hello,

I found another bug concerning the rtf format. When I export a document to rtf which was saved as odt, formatting of tables get screwed up!
Please watch the files attached.
Export in ooO 4.1.1 works. But when the file is opened in libre office formatting is lost, again.
Comment 1 Markus Mueller 2015-11-21 10:01:20 UTC 
Created attachment 120698 [details]
formatting after export to rtf
Comment 2 Markus Mueller 2015-11-24 11:39:15 UTC 
Created attachment 120759 [details]
sorry, source file was missing ...

Try to export to rtf and watch the result for yourself ...
Comment 3 Buovjaga 2015-11-28 18:09:02 UTC 
Repro.

Win 7 Pro 64-bit, Version: 5.0.3.2 (x64)
Build ID: e5f16313668ac592c1bfb310f4390624e3dbfb75
Locale: fi-FI (fi_FI)

LibreOffice 3.5.0rc3 
Build ID: 7e68ba2-a744ebf-1f241b7-c506db1-7d53735
Comment 4 Miklos Vajna 2016-07-22 21:28:31 UTC 
Bisect points out that this was fixed by the commit for bug 84832, so closing as a duplicate.

*** This bug has been marked as a duplicate of bug 84832 ***