Bug 100971 - Wrong pilcrow position when "show non printing characters" enabled for rotated text
Summary: Wrong pilcrow position when "show non printing characters" enabled for rotate...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.1.4.2 release
Hardware: All All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Formatting-Mark
  Show dependency treegraph
 
Reported: 2016-07-17 19:18 UTC by akash96j
Modified: 2025-05-27 03:12 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Sample Document (8.83 KB, application/vnd.oasis.opendocument.text)
2016-07-17 19:19 UTC, akash96j
Details
Screenshot of the bug (60.96 KB, image/png)
2016-07-17 19:22 UTC, akash96j
Details

Note You need to log in before you can comment on or make changes to this bug.
Description akash96j 2016-07-17 19:18:29 UTC

    
Comment 1 akash96j 2016-07-17 19:19:50 UTC
Created attachment 126252 [details]
Sample Document
Comment 2 akash96j 2016-07-17 19:22:02 UTC
Created attachment 126253 [details]
Screenshot of the bug
Comment 3 akash96j 2016-07-17 19:24:52 UTC
Position of Pilcrow symbol is wrong for rotated text.

To recreate:
1. Enter some text.
2. Rotate it by going to Format->Character->Position->Rotation/Scaling
3. Enable "Non-Printing characters" (Ctrl+F10)

Pilcrow shows up overlapping the text and not at the end of it.
Comment 4 Buovjaga 2016-07-27 19:45:23 UTC
Indeed. I tried searching for dupes, but did not find any.

64-bit, KDE Plasma 5
Build ID: 5.1.4.2 Arch Linux build-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: c1b665fcdacd4141137f1e369527e2c0d94513ae
CPU Threads: 8; OS Version: Linux 4.6; UI Render: default; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on July 26th 2016
Comment 5 Buovjaga 2016-07-27 19:47:36 UTC
Btw. I also noticed a huge cursor, which was previously reported only for a table: bug 91961
Comment 6 QA Administrators 2017-09-01 11:18:28 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2019-12-03 13:50:41 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2021-12-03 04:20:14 UTC Comment hidden (obsolete)
Comment 9 BogdanB 2023-05-27 08:27:30 UTC
also in Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 370533da3f07169791c0a17013ca55c57df2f3c9
CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded
Comment 10 QA Administrators 2025-05-27 03:12:14 UTC
Dear akash96j,

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