Bug 101177 - FORMATTING PRINTING issue in Title of Control Field
Summary: FORMATTING PRINTING issue in Title of Control Field
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.1.4.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Form-Controls
  Show dependency treegraph
 
Reported: 2016-07-28 15:19 UTC by Chris
Modified: 2022-08-06 03:33 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments
Example of bug file (17.10 KB, application/vnd.oasis.opendocument.spreadsheet)
2016-07-28 15:19 UTC, Chris
Details
Printout compare (88.46 KB, application/force-download)
2016-07-28 15:21 UTC, Chris
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Chris 2016-07-28 15:19:35 UTC
Created attachment 126451 [details]
Example of bug file

Hi, we use control fields to tick Yes or No. Now we up-dated to V5.1.4 When printing on different printers the titles are not correct any more, it looks as strange symbols. This was not the case in previous versions up to my last 5.0.3.2
This prevents to use new LibreOffice Versions since we have many such templates in place.
Moreover, the positioning of the Titles with respect to Anchor and the cell is difficult to handle on screen and also vary on print-outs. This was on old versions before and would be nice to get an improvement.
I add an example file creating the bug as well as a foto of the printout compare, before and after the up-date.
Comment 1 Chris 2016-07-28 15:21:37 UTC
Created attachment 126452 [details]
Printout compare
Comment 2 Buovjaga 2016-08-05 19:24:21 UTC
I can reproduce the problem when selecting "print to file" in 5.2 - it is also visible in the preview window of the printing dialog (the box labels are messed up).
Fortunately, however, the issue is not present in 5.3.

Chris: you might want to test with a daily build of 5.2 (from August): http://dev-builds.libreoffice.org/daily/libreoffice-5-2/?C=M;O=A

You did not mention your operating system. If you are using Linux, see these instructions: https://wiki.documentfoundation.org/Installing_in_parallel/Linux

Let's hope that the next version of 5.2 has the fix, but I'll set to NEW for now.

Arch Linux 64-bit, KDE Plasma 5
Version: 5.2.0.4
Build ID: 5.2.0-1
CPU Threads: 8; OS Version: Linux 4.6; UI Render: default; 
Locale: fi-FI (fi_FI.UTF-8)

Arch Linux 64-bit, KDE Plasma 5
Version: 5.3.0.0.alpha0+
Build ID: f3d26af51588af441f62fb69bb7a5432845226ac
CPU Threads: 8; OS Version: Linux 4.6; UI Render: default; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on August 5th 2016
Comment 3 QA Administrators 2018-08-05 02:47:06 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2020-08-05 04:56:05 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2022-08-06 03:33:57 UTC
Dear Chris,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug