Bug 35589 - xlsx import print area error
Summary: xlsx import print area error
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.3.2 release
Hardware: x86 (IA32) Windows (All)
: medium minor
Assignee: Muthu
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-23 04:47 UTC by forevry
Modified: 2012-02-29 01:55 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Sample document create with Excel 2007. (9.97 KB, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
2011-04-18 10:20 UTC, forevry 		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 forevry 2011-03-23 04:47:22 UTC 
Hello 
there are import problems of xlsx document from a excel when print areas are/ not are defined.

Steps to Reproduce:

in excel file
sheet1 not print area defined
sheet2 print area defined
sheet3 print area defined

in sheet1 print range is -none- (format > print ranges>edit) and is not possible print this sheet (in xls document is -entire sheet-).
Comment 1 Katarina Behrens 2011-03-24 06:45:22 UTC 
Muthu, can you please look into this one?
Comment 2 Muthu 2011-04-13 09:42:07 UTC 
@forevry: Sorry for the delayed reply...Can you please provide sample document, please?
Comment 3 forevry 2011-04-18 10:20:16 UTC 
Created attachment 45778 [details]
Sample document create with Excel 2007.
Comment 4 forevry 2011-04-18 10:28:18 UTC 
Comment on attachment 45778 [details]
Sample document create with Excel 2007. 

Page preview from sheet1 is not working.
Comment 5 Muthu 2011-07-01 03:12:37 UTC 
This seems to be fixed in master now. Needs to be verified on 3.4 branch thou...
Comment 6 Muthu 2011-12-15 03:08:16 UTC 
@Rainer: I need your help in confirming that this is indeed fixed in 3.5.
If so, shall we close this? Thank you so much.
Comment 7 Muthu 2012-02-29 01:55:54 UTC 
Closing this fixed. Please reopen if necessary (i.e. if it is still a problem in 3.5.x). Thank you.