I am trying to create a label type for a full sheet of 3/4 inch by 1/2 inch labels of 9 columns and 16 rows. They are on standard letter-sized (8.5 by 11 inch) sheets. The margins and pitches are in 1/8ths and 1/16ths of an inch.
When I put in the correct horizontal pitch, vertical pitch, and margins, the number is rounded to two decimal digits. The rounding error, when multiplied by the number of labels, destroys the alignment to the actual labels when printed.
I have tried inputting the measurments in the following ways:
0.625" which is converted to 0.63"
15.88mm which is converted to 0.63"
5/8 which is converted to 0.63"
The problem is that this is not just a "display" rounding, where the actual measurement is correct internally. The internal number also seems to be rounded to two decimal digits in inch units. I was hoping that it would also use two decimal digits in millimeters, but no luck.
This issue makes the label creation unworkable. I have 1/2 by 1/2 and 3/4 by 1/2 labels that require pitches and margins with greater resolution to make them work.
I can find no work around.
I see that there are other bug reports related to the two decimal digit issue, but not for labels in writer. So, I am adding this to the list since it makes printing to small labels useless. To further justify the need, these are small asset tags that will have sequential numbers and company logo printed. There is a need for the labels to work properly and be used with a database merge.
Steps to Reproduce:
1. File/New/Labels -> format tab
2. Horizontal Pitch 7/8"
3. Vertical Pitch 5/8"
4. Width 3/4"
5. Height 1/2"
6. Columns 9
7. Rows 16
8. print out set of labels and see that the vertical and horizontal pitches do not match the numbers entered and cannot print properly on label sheet.
Labels do not print at correct (entered) pitches. Rounding error causes accumulated error in label placement and printing not within label bounds.
Printing would be properly positioned on the labels in the positions as entered into the label creation form.
User Profile Reset: No
Version: 184.108.40.206 (x64)
Build ID: 144abb84a525d8e30c9dbbefa69cbbf2d8d4ae3b
CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug.
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
(Please note that the attachment will be public, remove any sensitive information before attaching it)
> I see that there are other bug reports related to the two decimal digit
Could you please add them in See also field? Thank you.
This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
Please read this message in its entirety before proceeding.
Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):
a) Provide details of your system including your operating
system and the latest version of LibreOffice that you have
confirmed the bug to be present
b) Provide easy to reproduce steps – the simpler the better
c) Provide any test case(s) which will help us confirm the problem
d) Provide screenshots of the problem if you think it might help
e) Read all comments and provide any requested information
Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:
a) respond via email
b) update the version field in the bug or any of the other details
on the top section of our bug tracker