Issue 20566 - Spreadsheet does not properly rener PDF
Summary: Spreadsheet does not properly rener PDF
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Calc
Classification: Application
Component: code (show other issues)
Version: OOo 1.1
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: frank
QA Contact: issues@sc
URL: http://www.blu.org/bug.balance.sheet.sxc
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-01 19:28 UTC by gaf
Modified: 2003-10-02 13:43 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
Boston User Group spreadsheet that renders poorly to pdf (7.42 KB, application/octet-stream)
2003-10-01 19:31 UTC, gaf
no flags Details
PDF rendered by the spread sheet (17.37 KB, application/octet-stream)
2003-10-01 19:35 UTC, gaf
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description gaf 2003-10-01 19:28:12 UTC
The attached spreadsheet messes up the last few lines of this spreadsheet. 
The spreadsheet was created with rc5, but also tested on 1.1.
The spreadsheet is also referenced in the URL, but the pdf is attached.
Comment 1 gaf 2003-10-01 19:31:18 UTC
Created attachment 9888 [details]
Boston User Group spreadsheet that renders poorly to pdf
Comment 2 gaf 2003-10-01 19:35:47 UTC
Created attachment 9889 [details]
PDF rendered by the spread sheet
Comment 3 frank 2003-10-02 10:22:32 UTC
Hi Jerry,

I can't detect any glitches in the rows of the exported spreadsheet.
The only thing I can see is that the last two columns are on the
second page. This is caused by the print ranges set. If you want the
whole spreadsheet on one page, just go to Format Page Sheet and select
Fit Printout to 1 Page.

So I have to set it to worksforme.

Please drop a line if this is the problem you are facing. If not,
please describe more precise what the problem is and reopen the Issue.

Frank
Comment 4 frank 2003-10-02 10:36:35 UTC
Worksforme I've said ;-)
Comment 5 gaf 2003-10-02 13:43:47 UTC
That is correct, and this should be closed as a cockpit error.