Bug 40278 - Printing range form letter or mail merge 1 short.
Summary: Printing range form letter or mail merge 1 short.
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.3.2 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-21 19:41 UTC by Steve Edmonds
Modified: 2012-08-31 10:07 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Edmonds 2011-08-21 19:41:46 UTC
When printing a mail merge/form letter you have the option to select a record range for the form data.
If you select From 1 to 100 then records 1 to 99 inclusive are printed, record 100 is not.
If you select record From 50 to 50 (so you can print just record 50) then a letter prints with no data from the data source. To print record 50 you need to print From 50 to 51.
Comment 1 Tom 2011-08-22 03:30:41 UTC
Hi :)
A fence-post error?
http://catb.org/jargon/html/F/fencepost-error.html

The word "To" is not inclusive and that is sometimes not intuitive for people.  I think it's right tho.
Regards from
Tom :)
Comment 2 Steve Edmonds 2011-08-22 11:24:36 UTC
If it is right (and technically I agree) there become 2 bugs.
1. Prevent printing a page empty of data for range n to n (i.e. 5 to 5)
2. General print dialogue in all LO applications where range is specified 5-7 needs to be non-inclusive of the last value, i.e. only 5 and 6 print.

It would make more sense to fix the merge and add the text "inclusive" to the range so that it matches other page selections.
Comment 3 Björn Michaelsen 2011-12-23 12:41:30 UTC
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Comment 4 Florian Reisinger 2012-08-14 14:04:40 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 5 Florian Reisinger 2012-08-14 14:05:28 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 6 Florian Reisinger 2012-08-14 14:09:55 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 7 Florian Reisinger 2012-08-14 14:11:53 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian