Bug 54257 - EDITING : RTF document containing text frames overlays textframe space background over cell boundaries leading to incorrect Page Preview and PDF export
Summary: EDITING : RTF document containing text frames overlays textframe space backgr...
Status: CLOSED DUPLICATE of bug 49403
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.6.1.2 release
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-30 09:13 UTC by Timon
Modified: 2013-11-16 13:03 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Text areas close table framing (5.87 KB, application/rtf)
2012-08-30 09:13 UTC, Timon
Details
Another file & preview (119.69 KB, application/x-zip-compressed)
2012-08-31 08:05 UTC, Timon
Details
Screenshot with LO 3.5.4 (164.71 KB, image/png)
2012-08-31 09:37 UTC, Alex Thurgood
Details
Screenshot with LO 3.6.0.4 (169.10 KB, image/png)
2012-08-31 09:38 UTC, Alex Thurgood
Details
How documents looks when opened and in a preview mode (printed) (224.08 KB, application/x-zip-compressed)
2012-08-31 11:19 UTC, Timon
Details
How to find page Preview (27.86 KB, image/jpeg)
2012-08-31 11:27 UTC, Timon
Details
rtf files, that were sucessfully opened in 3.6.X, but in 4.0.0.0 beta 2 could not be opened (crash) (11.18 KB, application/rtf)
2012-12-24 07:38 UTC, Timon
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Timon 2012-08-30 09:13:38 UTC
Created attachment 66321 [details]
Text areas close table framing

Example 15.rtf - Oracle Report document. Mostly all is fine even in
multipage document, but text areas close table framing. In preview and while
printing tables look ragged (broken). Also, the more such text areas in
document, the longer it is opened. If document have 120 rows in a table (2
pages), it is even impossible to scroll such document normally (all is
freezing).
Comment 1 Alex Thurgood 2012-08-31 07:03:46 UTC
Please provide a sample ODB file containing a report with the default, and detailed steps to reproduce the problem. For the moment, your description is too vague. The RTF document you provide is only 1 page long.

What do you mean by "text areas enclose framing" ?

For the moment, I can't determine where the problem lies, perhaps it is :

- the RTF export filter ;
- the Report generator ;
- some other unknown factor, like page or printer configuration.



In order to be able to test/confirm, we need you to provide us with the steps that led to the result that you consider buggy.

Setting NEEDINFO status.

Alex
Comment 2 Timon 2012-08-31 08:05:09 UTC
Created attachment 66388 [details]
Another file & preview

Here is another multirow file. If you try to open it, then you'll see how difficult to scroll this document. In Preview you can see how file looks like and how it is printed (tested with HP, Kyocera, Xerox). Framing disappears in document (text covers frames of the table)
Comment 3 Alex Thurgood 2012-08-31 09:37:14 UTC
I do not seem to be able to reproduce the problems you are seeing, when I test with either 3.5.4 or 3.6.0.4 on Linux Mint 12 64bit.

I am attaching screenshot from both 3.5.4 and 3.6.0.4.

Alex
Comment 4 Alex Thurgood 2012-08-31 09:37:49 UTC
Created attachment 66397 [details]
Screenshot with LO 3.5.4
Comment 5 Alex Thurgood 2012-08-31 09:38:33 UTC
Created attachment 66398 [details]
Screenshot with LO 3.6.0.4
Comment 6 Alex Thurgood 2012-08-31 09:39:01 UTC
I will have to test with a 3.6.1 version to compare.

Alex
Comment 7 Alex Thurgood 2012-08-31 09:40:33 UTC
Please also provide an ODT version of your second report document so that we can compare. I get the feeling that this isn't a database problem at all, if anything, it would be the RTF export filter.


Alex
Comment 8 Timon 2012-08-31 11:19:49 UTC
Created attachment 66401 [details]
How documents looks when opened and in a preview mode (printed)

You give screenshots of a document. If I simply open document in LibO 3.6.1 then I get the same screen as you (Example 16 open.JPG). Then I go to page preview and see, that frames are broken (Example 16 preview.JPG). Then I print page and I see the same as in preview mode.

Everything is done in Windows XP SP3 Russian.

> Please also provide an ODT version of your second report document so that we
can compare.

Where should I get it? The only type of report that I can provide - in RTF format. If you need an ODT document, then you can re-save my RTF in desired format.
Comment 9 Timon 2012-08-31 11:27:50 UTC
Created attachment 66402 [details]
How to find page Preview

As I see all that time you only opened document
You need to Preview it !!!

Start Calc
Go to menu File - Page Preview (highlighted, russian language)
Comment 10 Alex Thurgood 2012-08-31 11:34:04 UTC
OK, let's start from the beginnng :

1) How do you create your report ?

2) Is your report contained in the ODB file ? 

3) Do you save the report outside of the ODB file as a separate document (Save as... once the report has been created) ?

4) The report should be saved as ODT by default, not RTF. If your document is a RTF file, then this is not the default Save behaviour for reports created with the Oracle Report Builder. Please explain exactly how you get your RTF file.


Alex
Comment 11 Alex Thurgood 2012-08-31 11:35:31 UTC
(In reply to comment #9)
> Created attachment 66402 [details]
> How to find page Preview
> 
> As I see all that time you only opened document
> You need to Preview it !!!
> 
> Start Calc
> Go to menu File - Page Preview (highlighted, russian language)

Why should I be starting Calc to load a RTF file, this is a word processing document, not a spreadsheet.


Alex
Comment 12 Alex Thurgood 2012-08-31 11:37:44 UTC
(In reply to comment #8)


> Where should I get it? The only type of report that I can provide - in RTF
> format. If you need an ODT document, then you can re-save my RTF in desired
> format.

No, that is not the way. If the report has been created with the Oracle Report Builder extension, then the default format of the report is ODT, not RTF.

Saving the RTF file you provided is not the way to provide the document, because that would involve a return journey via the RTF import filter, which might have its own issues.

Alex
Comment 13 Alex Thurgood 2012-08-31 11:58:09 UTC
OK, so I can confirm that the Preview and PDF export of a RTF document shows that the background space occupied by the Text Frames overwrites the underlying cell borders.

What does this prove about the Report Builder ? Nothing, unless you can show me how to get from a default ODT generated report to the RTF file without doing a "Save as..." from the file menu.

As I mentioned earlier, this still appears to be an RTF import problem.

Changing title to reflect that situation.

Then I will have to look to see if this is a duplicate of already existing RTF filter bugs.

Alex
Comment 14 Timon 2012-08-31 12:05:50 UTC
Sorry, of course Writer, not Calc.

I use client software in my work that uses Oracle report to upload data. The
only choise I have - get report in RTF format. All other options are limited by  developer and I can't give you file in any other format.
Comment 15 Alex Thurgood 2012-08-31 12:12:34 UTC
Ah, so, looking at RTF problems, I see that you had already file a report with
virtually the same subject, except that in the present report, you didn't
specify that it was Oracle Crystal Reports that generated the report, thus
leading me to the conclusion that you were using the Oracle Report builder
extension provided by LibreOffice.

The report document you provided, generated by Oracle Crystal Reports, creates
a RTF formatted file. This file is incorrectly displayed in Page Preview and
PDF export.

Thus, the problem is, as I surmised a RTF import problem with regard to the
text frames that Oracle Crystal Reports produces.

This is a duplicate of 49403

*** This bug has been marked as a duplicate of bug 49403 ***
Comment 16 Timon 2012-12-24 07:38:47 UTC
Created attachment 72057 [details]
rtf files, that were sucessfully opened in 3.6.X, but in 4.0.0.0 beta 2 could not be opened (crash)

rtf files, that were sucessfully opened in 3.6.X, but in 4.0.0.0 beta 2 could not be opened (crash)

REGRESSION: Test files, that were sucessfully opened in 3.6.X, in 4.0.0.0 beta 2 could not be opened at all (crash) with "General Error. General input/output error."