Bug 64785 - EDITING: Print ranges (rows to repeat) changes after document is closed and open again
Summary: EDITING: Print ranges (rows to repeat) changes after document is closed and o...
Status: RESOLVED DUPLICATE of bug 62938
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
Whiteboard: BSA
Depends on:
Reported: 2013-05-20 08:48 UTC by Ljiljan
Modified: 2013-05-20 09:32 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Steps to reproduce (steps 1-6) (9.59 KB, application/vnd.oasis.opendocument.spreadsheet)
2013-05-20 08:48 UTC, Ljiljan

Note You need to log in before you can comment on or make changes to this bug.
Description Ljiljan 2013-05-20 08:48:16 UTC
Created attachment 79564 [details]
Steps to reproduce (steps 1-6)

Problem description: 

If print range (rows to repeat) is defined as "$1:$2" and among that range merged cells exit, when document is saved, closed and opened again it only shows "$2"... this affects printing next time document is open because it only uses second row to repeat on every page.

Steps to reproduce:
1. In A1 write "Name"
2. Merge A1 and A2
3. In B1 write "Test"
3. Merge B1 and C1
4. In B2 write "Mark"
5. In C2 write "Comment"
6. Fill some data for these columns so at least two pages appear
7. Select from menu Format -> Print Ranges -> Edit
8. In "Rows to repeat" field type "$1:$2"
9. Go to Print Preview so check that both two rows are repeated at every page
10. Save and close document
11. Open document again and check print preview, as well as menu Format -> Print Ranges -> Edit... now only second row is repeated. 

Current behavior:

Print range is not saved correctly (only $2)
Only second row is repeated even though both rows are defined.

Expected behavior:

Print ranges should be saved correctly ($1:$2)
Both rows should be repeated at every page.
Operating System: Ubuntu
Version: release
Comment 1 ign_christian 2013-05-20 09:32:45 UTC

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