Bug 42817 - TABLE: RTF with table doesn't open with 3.4.* and it does with 3.3.*
Summary: TABLE: RTF with table doesn't open with 3.4.* and it does with 3.3.*
Status: CLOSED DUPLICATE of bug 39337
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.4.3 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA target:3.5.0
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-11 05:56 UTC by Dimas
Modified: 2012-03-19 22:36 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
The document with bad format in lo3.4 and good format in lo3.3 (105.20 KB, application/msword)
2011-11-11 05:56 UTC, Dimas 		Details
Screenshot of the bad render with LO 3.4 (59.76 KB, image/jpeg)
2012-01-09 01:31 UTC, Dimas 		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 Dimas 2011-11-11 05:56:09 UTC 
Created attachment 53399 [details]
The document with bad format in lo3.4 and good format in lo3.3

Problem description: The attached document can't be viewed correctly with LibreOffice 3.4.3 (neither 3.4.4). With 3.3.3 and 3.3.4 the table inside have a good format.

Steps to reproduce: Open the file (attached)

Current behavior: Bad table format

Expected behavior: Good table format
              
Browser: Mozilla/5.0 (Windows NT 6.1; rv:9.0) Gecko/20100101 Firefox/9.0
Comment 1 tester8 2012-01-06 17:28:56 UTC 
Can you please upload screenshot of incorrect rendering or pdf? I can't see big problems with 3.5.

Is problems still there for you with LO3.5?
Comment 2 Dimas 2012-01-09 01:31:16 UTC 
Created attachment 55323 [details]
Screenshot of the bad render with LO 3.4
Comment 3 Dimas 2012-01-09 02:11:17 UTC 
With 3.3 and 3.5beta it's OK. I attached a screenshot with 3.4 bad render.
Comment 4 Jean-Baptiste Faure 2012-03-19 22:36:12 UTC 
Was a duplicate of bug 39337.
Works as expected in LO 3.5.1. Closing. Thank you.

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