Format > Spacing menu is missing 1.15 line spacing entry
I confirm it. Version: 6.0.0.0.alpha1 (x64) Build ID: c1d1f859b268f650143d48f294999cda0fa57350 CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: de-DE (de_DE); Calc: group
Jim: Can you take this one on and create .uno:SpacePara115. Would be great if you can also create .uno:SpacePara25 and .uno:SpacePara3 as they will be useful as well.
Yes I have .uno:SpacePara115 implemented but ran into make check failing a unit test. Lot of different modules use .uno:SpaceParaXX. I will focus on Writer first. I will do 25 and 3 also.
Line spacing 1.15, 2.5 and 3 are added with this patch - https://gerrit.libreoffice.org/#/c/44318/ Need someone to create lc_spacepara115.png, lc_spacepara25.png, and lc_spacepara3.png
Patch for the icons https://gerrit.libreoffice.org/45038
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still repro in Version: 6.2.0.0.beta1 (x64) Build ID: d1b41307be3f8c19fe6f1938cf056e7ff1eb1d18 CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; Locale: en-US (de_DE); UI-Language: en-GB Calc: threaded
Dear Jim Raykowski, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still present in Version: 7.2.1.2 (x64) / LibreOffice Community Build ID: 87b77fad49947c1441b67c559c339af8f3517e22 CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL Jim, can you have a look at it again?
Here is a patch that adds 1.15 line spacing UNO for use in Writer text, comments, and drawing shells: https://gerrit.libreoffice.org/c/core/+/123569 It needs an image. I think patches for a 1.15 line spacing UNO for Draw/Impress and Calc and 2.5, 3 line spacing UNO commands can be a good way for a beginning LO hacker to learn how UNO commands are implemented.
Jim Raykowski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/40458226fda358bd90c25ddfe6a9b2cf25b2fcad tdf#113512 Writer: 1.15 line spacing UNO command It will be available in 7.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
I might have been too fast with resolving fixed. Rizal, there is an image missing for this entry. Should be *_SpacePara115, but please double check.
(In reply to Heiko Tietze from comment #12) > I might have been too fast with resolving fixed. Rizal, there is an image > missing for this entry. Should be *_SpacePara115, but please double check. Yes, image is missing => Back to NEW
Sorry, status should be reopen, but I can't set reopen any more
(In reply to Heiko Tietze from comment #12) > I might have been too fast with resolving fixed. Rizal, there is an image > missing for this entry. Should be *_SpacePara115, but please double check. The bug for icon is tdf#145670
(In reply to Rizal Muttaqin from comment #15) > The bug for icon is tdf#145670 Thnak you, Rizal. I think we can close this bug then => VERIFIED FIXED