Bug 50226 - FILEOPEN RTF: TABLE VIEWING isn't correct
Summary: FILEOPEN RTF: TABLE VIEWING isn't correct
Status: RESOLVED DUPLICATE of bug 59393
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.4 RC1
Hardware: x86 (IA32) Windows (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-22 12:03 UTC by Ivan
Modified: 2013-01-31 08:57 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
wrong file rtf (207.85 KB, application/rtf)
2012-05-22 12:03 UTC, Ivan 		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 Ivan 2012-05-22 12:03:30 UTC 
Created attachment 61974 [details]
wrong file rtf

File taken (and problem) from here https://bugs.freedesktop.org/show_bug.cgi?id=47802

RTF file should be placed on a 1 page, in v.3.5.4RC1, I see two pages =(


Sorry for my English.
Comment 1 bfoman (inactive) 2012-11-05 17:49:23 UTC 
Confirmed with:
LO 3.6.3.2
Build ID: 58f22d5
Windows XP Professional SP3

In this version I see 3 pages. One page in Word 2007.
Comment 2 Ivan 2012-11-25 15:03:00 UTC 
LibO-Dev_4.0.0.0.alpha1_Win_x86_install_multi.msi 25.11.12
Windows XP Prof SP3 3

In this version I see 2 pages. (this is better =))
Comment 3 bfoman (inactive) 2012-11-26 13:02:25 UTC 
Confirmed with:
LO 4.0.0.0.alpha1+ 
Build ID: 6aabe09
Windows 7 Professional SP1 64 bit

In this version I see 3 pages (last one seems to be blank). One page in Word 2010.
Comment 4 Ivan 2013-01-13 11:35:40 UTC 
LibreOffice 4.0.0 RC1 (2013-01-12)
Windows XP Professional SP3

in this version it is impossible to read the file because of shift of tables
Comment 5 headsup 2013-01-31 08:57:15 UTC 
Confirmed on w8 pro x86 32 bit libreoffice Version 4.0.0.2 .0.2 (Build ID: 5991f37846fc3763493029c4958b57282c2597e) and ms office. 5 pages on libreoffice 4.0.0.2.

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