[Libreoffice-bugs] [Bug 141723] Dictionary is deactivated on selection
https://bugs.documentfoundation.org/show_bug.cgi?id=141723 --- Comment #5 from Shantanu --- Can not reproduce: Version: 7.5.2.2 (X86_64) / LibreOffice Community Build ID: 53bb9681a964705cf672590721dbc85eb4d0c3a2 CPU threads: 1; OS: Windows 10.0 Build 14393; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded But I remember it behaved as mentioned in the bug report on atleast one computer that I used in the past and it was very annoying. :) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 154933] Rename "Text body" to "Body text"
https://bugs.documentfoundation.org/show_bug.cgi?id=154933 Telesto changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 154933] Rename "Text body" to "Body text"
https://bugs.documentfoundation.org/show_bug.cgi?id=154933 Telesto changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 45065] Clipping issue (was: Problem with EDITING of technical pdfs)
https://bugs.documentfoundation.org/show_bug.cgi?id=45065 --- Comment #27 from V Stuart Foote --- (In reply to QA Administrators from comment #26) Issue remains. Missing clipping mask handling with the pdfio "import" filter, but very high fidelity using the pdfium based "insert" filter. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-23.05' - i18npool/source
i18npool/source/localedata/data/en_US.xml |8 1 file changed, 4 insertions(+), 4 deletions(-) New commits: commit b894ae643214aad27bd606c8ae5a3d34dabb915e Author: Justin Luth AuthorDate: Fri Jan 6 10:03:40 2023 -0500 Commit: Justin Luth CommitDate: Fri Apr 21 05:43:43 2023 +0200 tdf#56258 i18npool en-US: extend outline 1.a) to 4 levels Change 1. a) -> 1) a) 1) A) This is intended as a clean, modern style of outline that has good visual spacing in LibreOffice. This differentiates it a bit more from the first option, and extends the numbered level to the typical depth of 4, while still keeping a logical suffix pattern and maintaining the general "theme" of the previous definition. Yes, it is a bit odd to have a capital A following a smaller case a. However, this is at the fourth level, which isn't reached very often, and I wanted to keep a choice that focuses on a small a. Surprisingly, with the default 12pt/Liberation font, a 10) still fits in the allotted space before the tabstop, so in most cases this outline will have proper visual spacing all the way up to 99). There are plenty of choices that start with 1 followed by a dot, so I used this opportunity to create the only list that starts with a ")" suffix. Google docs for example has a 1) a) i) choice, but for modern lists I don't think we want to use roman numerals. Change-Id: I34725d6aa113831eaeaa88c295b3b3f1294f8998 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150666 Tested-by: Justin Luth Reviewed-by: Justin Luth diff --git a/i18npool/source/localedata/data/en_US.xml b/i18npool/source/localedata/data/en_US.xml index e137cdbe5f7a..5f4b9d903c2f 100644 --- a/i18npool/source/localedata/data/en_US.xml +++ b/i18npool/source/localedata/data/en_US.xml @@ -576,11 +576,11 @@ - - + + - - + +
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-23.05' - i18npool/source
i18npool/source/localedata/data/en_US.xml | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) New commits: commit 26728c899e84d5d4dbd9ed700f27f1a1fb40f037 Author: Justin Luth AuthorDate: Fri Jan 6 10:31:41 2023 -0500 Commit: Justin Luth CommitDate: Fri Apr 21 05:43:22 2023 +0200 tdf#56258 i18npool en-US: replace illogical outline 1.(a).i.A Change 1.(a).i.A. -> A.1.a.1. This is intended as a clean, modern style of outline that has good visual spacing in LibreOffice. It provides a simple alternative to the second style, reversing the order while still keeping a logical suffix pattern. This design will easily allow large/long lists to fit in the allotted space before the tabstop. There was no attempt to match the theme of the previous definition, since it neither looked good in LO's default spacing, nor was it consistent/logical. Change-Id: If7de1302110a3c97922bd2eeba7a917444110b27 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/145156 Tested-by: Jenkins Reviewed-by: Justin Luth Reviewed-by: Vernon, Stuart Foote Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150665 Tested-by: Justin Luth diff --git a/i18npool/source/localedata/data/en_US.xml b/i18npool/source/localedata/data/en_US.xml index d604a98791e2..e137cdbe5f7a 100644 --- a/i18npool/source/localedata/data/en_US.xml +++ b/i18npool/source/localedata/data/en_US.xml @@ -584,11 +584,11 @@ - - - - - + + + + +
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-23.05' - i18npool/source
i18npool/source/localedata/data/en_US.xml |8 1 file changed, 4 insertions(+), 4 deletions(-) New commits: commit 678263bd8f7ce5b8f0fe85a067e02102f5362e80 Author: Justin Luth AuthorDate: Fri Jan 6 09:05:39 2023 -0500 Commit: Justin Luth CommitDate: Fri Apr 21 05:43:05 2023 +0200 tdf#56258 i18npool en-US: change outline order to match MLA style Changed I.A.i.a) -> I.A.1.a.i. The overwhelming result of a google search for "official/correct outline list format" indicates that the third level should be a 1, not an i. MLA Handbook (according to wikipedia) uses the order I.A.1.a.i. (a) (1) i) Chicago Mode of Style is usually interpreted as I.A.1.a) or I.A.1.a. with varying lower sublevels/suffixes. Wikipedia also suggest the logical order of I.A.1.a.i.I) A) 1) a) i) (I) (A) (1) (a) (i) Change-Id: I7fcc8a1ee727d6cddca4bf0c6a8461538769cf5d Reviewed-on: https://gerrit.libreoffice.org/c/core/+/145147 Tested-by: Justin Luth Reviewed-by: Justin Luth Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150664 diff --git a/i18npool/source/localedata/data/en_US.xml b/i18npool/source/localedata/data/en_US.xml index b83c64489238..d604a98791e2 100644 --- a/i18npool/source/localedata/data/en_US.xml +++ b/i18npool/source/localedata/data/en_US.xml @@ -600,12 +600,12 @@ - + - - - + + +
[Libreoffice-bugs] [Bug 122457] Worse text rendering in newer versions of LibreOffice (OpenGL)
https://bugs.documentfoundation.org/show_bug.cgi?id=122457 Dieter changed: What|Removed |Added URL|https://www.rivasol.com.tr/ | |solucan-gubresi | --- Comment #27 from Dieter --- (In reply to Timur from comment #25) > There's no OpenGL anymore. Please retest master 7.1+ with and without Skia. Sam, could you please retest with LO 7.5? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154931] Spell check not working correctly in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=154931 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151307] Mac Address Book ODB file causes crash in LO when contact data edited in Contacts.app(macOS)
https://bugs.documentfoundation.org/show_bug.cgi?id=151307 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154781] Pasting into a cell should make it change to edit mode
https://bugs.documentfoundation.org/show_bug.cgi?id=154781 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154931] Spell check not working correctly in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=154931 --- Comment #4 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154781] Pasting into a cell should make it change to edit mode
https://bugs.documentfoundation.org/show_bug.cgi?id=154781 --- Comment #13 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 154781] Pasting into a cell should make it change to edit mode
https://bugs.documentfoundation.org/show_bug.cgi?id=154781 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 154781] Pasting into a cell should make it change to edit mode
https://bugs.documentfoundation.org/show_bug.cgi?id=154781 --- Comment #13 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 154479] Writer don't attach the document when using the attach at email button
https://bugs.documentfoundation.org/show_bug.cgi?id=154479 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154479] Writer don't attach the document when using the attach at email button
https://bugs.documentfoundation.org/show_bug.cgi?id=154479 --- Comment #11 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153451] LO Input line switched from white to gray (as rest of the toolbar) making it harder to find
https://bugs.documentfoundation.org/show_bug.cgi?id=153451 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153451] LO Input line switched from white to gray (as rest of the toolbar) making it harder to find
https://bugs.documentfoundation.org/show_bug.cgi?id=153451 --- Comment #9 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107836] [META] Page and section column bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107836 Bug 107836 depends on bug 150775, which changed state. Bug 150775 Summary: Adding footnotes conflicts with columns (document specific?) https://bugs.documentfoundation.org/show_bug.cgi?id=150775 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150775] Adding footnotes conflicts with columns (document specific?)
https://bugs.documentfoundation.org/show_bug.cgi?id=150775 --- Comment #3 from QA Administrators --- Dear csongor, 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 Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150775] Adding footnotes conflicts with columns (document specific?)
https://bugs.documentfoundation.org/show_bug.cgi?id=150775 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103164] [META] Footnote and Endnote bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103164 Bug 103164 depends on bug 150775, which changed state. Bug 150775 Summary: Adding footnotes conflicts with columns (document specific?) https://bugs.documentfoundation.org/show_bug.cgi?id=150775 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 53358] FILEOPEN Certain non-keyword formula literals in curly braces (e.g., "{*}") in imported DOCX document result in errors in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=53358 --- Comment #13 from QA Administrators --- Dear Stephan van den Akker, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 67929] Graphics lists not saved
https://bugs.documentfoundation.org/show_bug.cgi?id=67929 --- Comment #9 from QA Administrators --- Dear Olivier Hallot, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151381] FILEOPEN: Embedded Objects in .DOCX No Longer Rendering Properly
https://bugs.documentfoundation.org/show_bug.cgi?id=151381 --- Comment #2 from QA Administrators --- Dear Bobby, 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: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO 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! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146320] Base Report generator Java error
https://bugs.documentfoundation.org/show_bug.cgi?id=146320 --- Comment #15 from QA Administrators --- Dear Dennis Rice, 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: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO 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! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 45065] Clipping issue (was: Problem with EDITING of technical pdfs)
https://bugs.documentfoundation.org/show_bug.cgi?id=45065 --- Comment #26 from QA Administrators --- Dear brian.bj.parker99, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 52543] framework: broken links under /opt/lodev-3.6/share points to no longer existing OOo websites
https://bugs.documentfoundation.org/show_bug.cgi?id=52543 --- Comment #9 from QA Administrators --- Dear Sabri Unal, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 123668] Cursor focus moves outside Quick find bar when reaching results in Notes view
https://bugs.documentfoundation.org/show_bug.cgi?id=123668 --- Comment #6 from QA Administrators --- Dear David F Smith, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 123665] Inconsistent behavior of "find next" in slides and notes
https://bugs.documentfoundation.org/show_bug.cgi?id=123665 --- Comment #10 from QA Administrators --- Dear David F Smith, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 101368] Print selected area does not wrap text
https://bugs.documentfoundation.org/show_bug.cgi?id=101368 --- Comment #11 from QA Administrators --- Dear Houman, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154948] The color gradation in objects does not function.
https://bugs.documentfoundation.org/show_bug.cgi?id=154948 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #1 from m.a.riosv --- Please paste here the information on Menu/Help/About LibreOffce (There is an icon to copy) and add a sample file to test. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154947] Editing a formula should not remove range overlays; instead they should be updated
https://bugs.documentfoundation.org/show_bug.cgi?id=154947 m.a.riosv changed: What|Removed |Added Keywords||needsUXEval CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- +1 I think it is already reported, but I can't find. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153441] LibreOffice OpenType font features list is blocked
https://bugs.documentfoundation.org/show_bug.cgi?id=153441 خالد حسني changed: What|Removed |Added OS|All |Linux (All) Status|REOPENED|NEW --- Comment #7 from خالد حسني --- Might be GTK- or Ubuntu-specific, I’m on macOS and it works fine here. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152517] Navigator: Ctrl+Minus collapses the whole Headings tree, not the selected node
https://bugs.documentfoundation.org/show_bug.cgi?id=152517 Jim Raykowski changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #10 from Jim Raykowski --- Bit late in setting this one as fixed. It appears to be working as expected in: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 80a0d3b44cd6edb6419ab66588548ba169f2567b CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: x11 Locale: en-US (C); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103030] [META] Navigator sidebar deck and floating window
https://bugs.documentfoundation.org/show_bug.cgi?id=103030 Bug 103030 depends on bug 152517, which changed state. Bug 152517 Summary: Navigator: Ctrl+Minus collapses the whole Headings tree, not the selected node https://bugs.documentfoundation.org/show_bug.cgi?id=152517 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154825] Edit Sections: Hide Status is not reflected in Icons (hidden/unhidden) except Karasa Jaga and Sukapura
https://bugs.documentfoundation.org/show_bug.cgi?id=154825 --- Comment #5 from Rizal Muttaqin --- (In reply to Buovjaga from comment #4) > The file is sw/uiconfig/swriter/ui/editsectiondialog.ui > > Rizal: maybe you can look into it for the other themes. I could not quickly > locate the icon names. I can see that Karasa Jaga used copied version of previous Galaxy as KJ was meant to be complete as possible. Here the icon files list: icon-themes//sw/res/re01. icon-themes//sw/res/re02. icon-themes//sw/res/re03. icon-themes//sw/res/re04. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137946] Automatic cell calculation dont'works
https://bugs.documentfoundation.org/show_bug.cgi?id=137946 --- Comment #2 from Nanisa Han --- Try it on https://bitlifegame.io -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-23.05' - cui/source i18npool/source svx/source
cui/source/tabpages/numpages.cxx |6 +-
i18npool/source/localedata/LocaleNode.cxx |3 ++-
i18npool/source/localedata/data/en_US.xml | 10 +-
i18npool/source/localedata/data/locale.dtd |1 +
i18npool/source/localedata/localedata.cxx |9 +
svx/source/sidebar/nbdtmg.cxx | 13 +++--
6 files changed, 29 insertions(+), 13 deletions(-)
New commits:
commit 72e2ec361acc2b57ec3fc08325a16846d3c7df33
Author: Justin Luth
AuthorDate: Mon Jan 2 10:48:33 2023 -0500
Commit: Justin Luth
CommitDate: Fri Apr 21 03:07:07 2023 +0200
tdf#56258: allow i18npool to define SvxAdjust for outline
This is a squashed commit, including pre-requisite
commit b1226e1f225de4fa67a0d4f5a6aa4017284c7deb
and follow-up commit 6cabd7d9bfed37799a344f872d5f8fcf3214116a
Deciding whether the numbering should be Left, Right, or Center
is a rather important setting. Specifically for Roman numerals
(which grow very wide as they increment to 7 and 8)
the numbering styles set these to right aligned.
This really helps for keeping the text nicely aligned.
The numbering styles are built-in LO defaults,
but locale files can define numbering and outline
choices. This patch add the setting for "adjust" on
the outline levels.
For en_US, it makes sense to right-align roman numeral levels.
[The only other highly likely candidate for this that I could find
was old Hungarian (SZEKELY_ROVAS), but it doesn't seem
to be used in any locale definitions.]
I only changed en_US for now, but of course many other
locales are also using NumType="3" and NumType="4".
This only applies to the toolbar/sidebar SVX code path.
The Bullets and Numbering dialog does not currently
modify any spacing, so I didn't apply the adjustment either.
It also doesn't make sense to do this on single numbering changes
(aka ContinuousNumberingLevels or LC_NumberingLevel)
because we don't know or control the first line indent there either.
But at least for toolbar Outlines, we do change every level,
and so can set a (somewhat) appropriate spacing.
[Setting SvxAdjust without adjusting the spacing
is pointless. Don't make any changes at all if
the spacing ends up causing problems.]
The Numbering IVX/ivx styles set the firstLineIndent to -174,
so I did the same here. This is the scariest part of this change.
AFAICS SvxAdjust::Left is a non-locale aDefNumStyle default,
so hardcoding that for undefined LC_OutlineNumberingLevel
shouldn't be too scary.
Change-Id: I52deefe88aa55c55c9531b651411f64accb86f7f
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150663
Tested-by: Justin Luth
Reviewed-by: Justin Luth
diff --git a/cui/source/tabpages/numpages.cxx b/cui/source/tabpages/numpages.cxx
index c307f6ac155f..19a2b37ed82d 100644
--- a/cui/source/tabpages/numpages.cxx
+++ b/cui/source/tabpages/numpages.cxx
@@ -17,7 +17,6 @@
* the License at http://www.apache.org/licenses/LICENSE-2.0 .
*/
-#include
#include
#include
@@ -692,6 +691,11 @@ IMPL_LINK_NOARG(SvxNumPickTabPage, NumSelectHdl_Impl,
ValueSet*, void)
aFmt.SetIncludeUpperLevels(sal::static_int_cast< sal_uInt8 >(0 !=
nUpperLevelOrChar ? pActNum->GetLevelCount() : 1));
aFmt.SetCharFormatName(sNumCharFmtName);
aFmt.SetBulletRelSize(100);
+
+// Completely ignore the Left/Right value provided by the locale
outline definition,
+// because this function doesn't actually modify the indents at
all,
+// and right-adjusted numbering definitely needs a different
FirstLineIndent.
+
// #i93908#
aFmt.SetListFormat(pLevelSettings->sPrefix,
pLevelSettings->sSuffix, i);
}
diff --git a/i18npool/source/localedata/LocaleNode.cxx
b/i18npool/source/localedata/LocaleNode.cxx
index acc7dd8f927b..14232338b9f1 100644
--- a/i18npool/source/localedata/LocaleNode.cxx
+++ b/i18npool/source/localedata/LocaleNode.cxx
@@ -2236,7 +2236,7 @@ void LCOutlineNumberingLevelNode::generateCode (const
OFileWriter ) const
}
// hardcode number of attributes per level
-const int nAttributes = 11;
+const int nAttributes = 12;
const char* attr[ nAttributes ] =
{
"Prefix",
@@ -2248,6 +2248,7 @@ void LCOutlineNumberingLevelNode::generateCode (const
OFileWriter ) const
"LeftMargin",
"SymbolTextDistance",
"FirstLineOffset",
+"Adjust",
"Transliteration",
"NatNum",
};
diff --git a/i18npool/source/localedata/data/en_US.xml
b/i18npool/source/localedata/data/en_US.xml
index ffd0bf1fad59..b83c64489238 100644
--- a/i18npool/source/localedata/data/en_US.xml
+++ b/i18npool/source/localedata/data/en_US.xml
@@ -587,7 +587,7 @@
-
+
[Libreoffice-bugs] [Bug 136230] SPECIAL CHARACTER DIALOG: Results of search field are not displayed after font changing
https://bugs.documentfoundation.org/show_bug.cgi?id=136230 --- Comment #8 from shariqk...@gmail.com --- works for me. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122457] Worse text rendering in newer versions of LibreOffice (OpenGL)
https://bugs.documentfoundation.org/show_bug.cgi?id=122457 --- Comment #26 from sivisolucangubresi --- Bitkilerde, çiçeklerde, orkidede, sukulente https://www.rivasol.com.tr/blog/solucan-gubresi-bitkilere-nasil-uygulanir Solucan Gübresi Nasıl Kullanılır. çiçeklerine iyi bakmak için https://www.rivasol.com.tr/solucan-gubresisolucan gübresi satın alıp bitkilerine iyi bakabilirsiniz.https://www.rivasol.com.tr/sivi-solucan-gubresien iyi sıvı solucan gübresi, rivasol tarımdan satın alınır. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134850] TOC: On removing page number from Table of contents, the hyperlink goes away for second half length of the tab fill
https://bugs.documentfoundation.org/show_bug.cgi?id=134850 --- Comment #6 from shariqk...@gmail.com --- works for me. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122457] Worse text rendering in newer versions of LibreOffice (OpenGL)
https://bugs.documentfoundation.org/show_bug.cgi?id=122457 sivisolucangubresi changed: What|Removed |Added URL||https://www.rivasol.com.tr/ ||solucan-gubresi -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154948] New: The color gradation in objects does not function.
https://bugs.documentfoundation.org/show_bug.cgi?id=154948 Bug ID: 154948 Summary: The color gradation in objects does not function. Product: LibreOffice Version: 7.5.1.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ryo...@jetrac.com.mx Description: I chose some object in Impress and put some color gradation, chosing two colors. However, when the corresponding slide is shown on the screen in presentation mode, such object appears with only one color. And after that, when it's shown in normal mode, with the property panel, it shows "solid color". And when I change the selection to gradation, the color of the object changes and none of the colors I had chowen appears. Steps to Reproduce: 1.Chose an object 2.Select area 3.Select degration 4. Select combination of two colors and type (liner, etc.) 5. Chose Accept 6. Start presentation with the corresponding slide, but the object has only one of the colors (solid color but no gradation) 7. Return to normal view, and the setting of the gradation has lost Actual Results: As above, the color gradation setting loses. After that, I select the same object and see the side panel for the property, it shows "solid color". Expected Results: That the color gradation function works properly. Reproducible: Always User Profile Reset: No Additional Info: I didn't have this problem in earler version (I think the version 7.4). And as I have updated the version recently, I think this is a new problem for this new version. And I really need this problem to be fixed quick. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-23.05' - cui/source i18npool/source sw/qa
cui/source/tabpages/numpages.cxx |9 ++---
i18npool/source/localedata/data/en_US.xml | 12 ++--
sw/qa/extras/uiwriter/uiwriter.cxx|2 +-
3 files changed, 17 insertions(+), 6 deletions(-)
New commits:
commit f09e8642c66065bbaa57dea38ca4d68b606335d4
Author: Justin Luth
AuthorDate: Mon Jan 2 16:31:45 2023 -0500
Commit: Justin Luth
CommitDate: Fri Apr 21 01:27:34 2023 +0200
tdf#56258 en_US: increase outline levels definitions to 6
This is a squashed commit that includes
commit 894efac210a3871214d95a52c322b0bee40f00ba
tdf#56258 i18npool en-US: partial revert 5th outline level
There are 10 levels in numbering,
so it only makes sense to allow
outline definitions for all 10 levels.
Note that DOC/X formats only allow 9 levels,
There are two code paths that read these definitions.
The SVX toolbar code to allow 10 levels (SVX_MAX_NUM)
was already completed in the previous patch.
This commit allows 10 levels for the
Bullets and Numbering menu dialog.
Since all choices MUST define the same number of levels,
I only added one more. I hope that there isn't some secret
kind of requirement that ALL LOCALE's must also use
the same number of definitions - it doesn't seem to.
[Although not a direct comparison, bg_BG defines 10
single number levels, compared to en_US's 8,
and some Chinese locales also do more than 8.]
Change-Id: Ibe00d54cfa4577db83eba368b92be11055b076ec
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/144976
Tested-by: Jenkins
Reviewed-by: Justin Luth
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150661
Tested-by: Justin Luth
diff --git a/cui/source/tabpages/numpages.cxx b/cui/source/tabpages/numpages.cxx
index 916e513d9cc0..c307f6ac155f 100644
--- a/cui/source/tabpages/numpages.cxx
+++ b/cui/source/tabpages/numpages.cxx
@@ -510,11 +510,14 @@ SvxNumPickTabPage::SvxNumPickTabPage(weld::Container*
pPage, weld::DialogControl
SvxNumSettingsArr_Impl& rItemArr = aNumSettingsArrays[ nItem ];
Reference xLevel =
aOutlineAccess.getConstArray()[nItem];
-for(sal_Int32 nLevel = 0; nLevel < xLevel->getCount() && nLevel <
5; nLevel++)
+for(sal_Int32 nLevel = 0; nLevel < SVX_MAX_NUM; nLevel++)
{
-Any aValueAny = xLevel->getByIndex(nLevel);
+// use the last locale-defined level for all remaining levels.
+sal_Int32 nLocaleLevel = std::min(nLevel, xLevel->getCount() -
1);
Sequence aLevelProps;
-aValueAny >>= aLevelProps;
+if (nLocaleLevel >= 0)
+xLevel->getByIndex(nLocaleLevel) >>= aLevelProps;
+
SvxNumSettings_Impl* pNew =
lcl_CreateNumSettingsPtr(aLevelProps);
rItemArr.push_back( std::unique_ptr(pNew)
);
}
diff --git a/i18npool/source/localedata/data/en_US.xml
b/i18npool/source/localedata/data/en_US.xml
index 14c74a7e2932..ffd0bf1fad59 100644
--- a/i18npool/source/localedata/data/en_US.xml
+++ b/i18npool/source/localedata/data/en_US.xml
@@ -574,6 +574,7 @@
+
@@ -581,6 +582,7 @@
+
@@ -588,6 +590,7 @@
+
@@ -595,20 +598,23 @@
+
-
+
+
-
+
+
@@ -616,6 +622,7 @@
+
@@ -623,6 +630,7 @@
+
diff --git a/sw/qa/extras/uiwriter/uiwriter.cxx
b/sw/qa/extras/uiwriter/uiwriter.cxx
index 5cad83ed7b0f..0e45204f25db 100644
--- a/sw/qa/extras/uiwriter/uiwriter.cxx
+++ b/sw/qa/extras/uiwriter/uiwriter.cxx
@@ -1801,7 +1801,7 @@ CPPUNIT_TEST_FIXTURE(SwUiWriterTest, testTdf81995)
CPPUNIT_ASSERT_EQUAL(sal_Int32(8), aIndexAccess.getLength());
for(const auto& rIndexAccess : aIndexAccess)
{
-CPPUNIT_ASSERT_EQUAL(sal_Int32(5), rIndexAccess->getCount());
+CPPUNIT_ASSERT_EQUAL(sal_Int32(6), rIndexAccess->getCount());
for(int j=0;jgetCount();j++)
{
uno::Sequence aProps;
[Libreoffice-bugs] [Bug 154935] Enhancement: Add Points tool as default in Standard toolbar
https://bugs.documentfoundation.org/show_bug.cgi?id=154935 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||miguelangelrv@libreoffice.o ||rg Resolution|--- |WONTFIX --- Comment #1 from m.a.riosv --- You can edit the toolbar to add the buttons you like. https://help.libreoffice.org/latest/en-US/text/shared/guide/edit_symbolbar.html?DbPAR=SHARED#bm_id3159201 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124406] Dropdown list of formulaes in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=124406 Rafael Lima changed: What|Removed |Added CC||rafael.palma.l...@gmail.com --- Comment #3 from Rafael Lima --- FYI https://ask.libreoffice.org/t/how-to-view-a-list-of-available-formulas-on-calc/51707 Available functions should be shown in a dropdown list, which is easier to navigate and discover new functions. For instance, try searching form =NORM* functions (related to the normal distribution). They have weird names and are hard to remember. A dropdown list would make it much easier to search through the available formulas. The current implementation uses Ctrl+Tab to navigate the available functions. Not intuitive at all. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154947] Editing a formula should not remove range overlays; instead they should be updated
https://bugs.documentfoundation.org/show_bug.cgi?id=154947 Rafael Lima changed: What|Removed |Added Summary|Editing a formula should|Editing a formula should |not remove the range|not remove range overlays; |overlays; instead they |instead they should be |should be updated |updated -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154947] New: Editing a formula should not remove the range overlays; instead they should be updated
https://bugs.documentfoundation.org/show_bug.cgi?id=154947 Bug ID: 154947 Summary: Editing a formula should not remove the range overlays; instead they should be updated Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rafael.palma.l...@gmail.com In Calc, suppose you enter a formula in cell A2: =SUMPRODUCT(B2:B9;C2:C9) After you press enter, the formula result is displayed. Now suppose you want to edit the formula. For that you either double-click cell A2 or select cell A2 and press F2. When you do this, two overlays are shown for each of the ranges in the formula: B2:B9 => Blue overlay C2:C9 => Red overlay Now the cursor is blinking, allowing to edit the formula. The problem is that, as soon as the user types anything, both overlays are removed. This is a pain when working with formulas with multiple ranges, and you want to keep track of what is and what is not included in the formula yet. In Excel, when you start editing the formula, all overlays are maintained and updated while the formula is edited, which is super handy. In Google Sheets the same happens, with the added benefit that the range where the cursor is positioned gets a special highlight. OnlyOffice behaves exactly as Excel and WPS has a similar behavior as Google Sheets, giving special highlight to the range where the cursor is positioned. I propose we add this feature to Calc as well... it makes editing formulas much more productive. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154933] Rename "Text body" to "Body text"
https://bugs.documentfoundation.org/show_bug.cgi?id=154933 Rafael Lima changed: What|Removed |Added CC||rafael.palma.l...@gmail.com --- Comment #2 from Rafael Lima --- +1 from my side. Apparently "body text" is the right choice here. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154936] Why is it still not possible to set the title of a diagram as formula?
https://bugs.documentfoundation.org/show_bug.cgi?id=154936 Rafael Lima changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||rafael.palma.l...@gmail.com --- Comment #1 from Rafael Lima --- +1 This has been asked about in AskLibO before: https://ask.libreoffice.org/t/how-to-use-cell-content-as-a-chart-title-or-subtitle/9508 https://ask.libreoffice.org/t/how-to-have-in-graphs-title-subtitle-x-axis-and-y-axis-referred-to-cells/32200 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 154936] Why is it still not possible to set the title of a diagram as formula?
https://bugs.documentfoundation.org/show_bug.cgi?id=154936 Rafael Lima changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||rafael.palma.l...@gmail.com --- Comment #1 from Rafael Lima --- +1 This has been asked about in AskLibO before: https://ask.libreoffice.org/t/how-to-use-cell-content-as-a-chart-title-or-subtitle/9508 https://ask.libreoffice.org/t/how-to-have-in-graphs-title-subtitle-x-axis-and-y-axis-referred-to-cells/32200 -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-23.05' - svx/source
svx/source/sidebar/nbdtmg.cxx | 15 ++-
1 file changed, 10 insertions(+), 5 deletions(-)
New commits:
commit 312fd13f30e20c435370d8a11cf4123a25988f52
Author: Justin Luth
AuthorDate: Tue Jan 3 10:56:40 2023 -0500
Commit: Justin Luth
CommitDate: Fri Apr 21 00:03:15 2023 +0200
tdf#56258 svx: use last defined locale-outline for remaining levels
When applying an outline numbering choice
(one of the 8 predefined per-locale definitions)
the toolbar/sidebar would only affect the spacing
of 0 - 5 of the defined locale-levels,
and only changed the num type of the remainder.
Well, that can easily look bad if the indenting and spacing
is only partially modified.
[The Bullets and Numbering dialog outline grid
does not affect spacing at all.
That can be better or much worse, depending on the situation.]
This "Outline Format" button is normally turned off
on Writer's Formatting toolbar. You need to go to
Tools - Customize - Toolbars to turn it on.
It only seems to work for Writer - it was grayed out/disabled
in Draw even when I had it show up in the toolbar.
So almost nobody have ever seen or used this I expect.
However, I think it is important to get this working,
because I want to use this grid-choice code path
to be usable for the B dialog as well,
although that could upset people who already have
their spacing right and just want to change the digits.
In any case, this nbdtimg DOES already change some
spacing, so it should be either all or none.
Change-Id: Ib54b6ffe3497f09f0c57ff2db1ec2a946f692fc5
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150660
Tested-by: Justin Luth
Reviewed-by: Justin Luth
diff --git a/svx/source/sidebar/nbdtmg.cxx b/svx/source/sidebar/nbdtmg.cxx
index 241b91673836..a4def326c80b 100644
--- a/svx/source/sidebar/nbdtmg.cxx
+++ b/svx/source/sidebar/nbdtmg.cxx
@@ -590,11 +590,14 @@ void OutlineTypeMgr::Init()
pItemArr->sDescription = SvxResId(
TranslateId(RID_SVXSTR_OUTLINENUM_DESCRIPTION_0.mpContext, id.getStr()) );
pItemArr->pNumSettingsArr = new NumSettingsArr_Impl;
Reference xLevel =
aOutlineAccess.getConstArray()[nItem];
-for(sal_Int32 nLevel = 0; nLevel < xLevel->getCount() && nLevel <
5; nLevel++)
+for(sal_Int32 nLevel = 0; nLevel < SVX_MAX_NUM; nLevel++)
{
-Any aValueAny = xLevel->getByIndex(nLevel);
+// use the last locale-defined level for all remaining levels.
+sal_Int32 nLocaleLevel = std::min(nLevel, xLevel->getCount() -
1);
Sequence aLevelProps;
-aValueAny >>= aLevelProps;
+if (nLocaleLevel >= 0)
+xLevel->getByIndex(nLocaleLevel) >>= aLevelProps;
+
NumSettings_Impl* pNew =
lcl_CreateNumberingSettingsPtr(aLevelProps);
const SvxNumberFormat& aNumFmt( aDefNumRule.GetLevel( nLevel)
);
pNew->eLabelFollowedBy = aNumFmt.GetLabelFollowedBy();
@@ -618,7 +621,7 @@ sal_uInt16
OutlineTypeMgr::GetNBOIndexForNumRule(SvxNumRule& aNum,sal_uInt16 /*m
{
bool bNotMatch = false;
OutlineSettings_Impl* pItemArr = pOutlineSettingsArrs[iDex];
-sal_uInt16 nCount = pItemArr->pNumSettingsArr->size();
+sal_uInt16 nCount = pItemArr ? pItemArr->pNumSettingsArr->size() : 0;
for (sal_uInt16 iLevel=0;iLevel < nCount;iLevel++)
{
NumSettings_Impl* _pSet =
(*pItemArr->pNumSettingsArr)[iLevel].get();
@@ -633,7 +636,9 @@ sal_uInt16
OutlineTypeMgr::GetNBOIndexForNumRule(SvxNumRule& aNum,sal_uInt16 /*m
sal_UCS4 cChar = aFmt.GetBulletChar();
sal_UCS4 ccChar
-=
_pSet->sBulletChar.iterateCodePoints(::temporary(sal_Int32(0)));
+= _pSet->sBulletChar.isEmpty()
+ ? 0
+ :
_pSet->sBulletChar.iterateCodePoints(::temporary(sal_Int32(0)));
if ( !((cChar == ccChar) &&
_pSet->eLabelFollowedBy == aFmt.GetLabelFollowedBy() &&
[Libreoffice-bugs] [Bug 154946] New: Draw/Impress Standard toolbar missing many icons
https://bugs.documentfoundation.org/show_bug.cgi?id=154946 Bug ID: 154946 Summary: Draw/Impress Standard toolbar missing many icons Product: LibreOffice Version: 7.4.0.3 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Keywords: bibisected, bisected, regression Severity: normal Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: stephane.guil...@libreoffice.org CC: heiko.tie...@documentfoundation.org Blocks: 84909 Created attachment 186827 --> https://bugs.documentfoundation.org/attachment.cgi?id=186827=edit 7.3 and 7.4 compared Bibisected with linux-64-7.4 to first bad commit fc4c7349ed516cba4c93815326500316a8801686 which points to core commit 4cd7489f5898394730b794bdecbc29800cf23627 which is a cherrypick of: commit da284326961c2e3cfe48cd05b1ea6a51f33a0124 author Heiko TietzeFri Jun 24 11:04:31 2022 +0200 committer Heiko TietzeFri Jun 24 11:04:31 2022 +0200 Resolves tdf#143055 - Make Snap-to-grid easier to access Since this fix for bug 143055, many icons are missing for Impress and Draw's Standard toolbar. Not sure why I didn't catch it when verifying the fix back then. Heiko, maybe various missing trailing "/" in https://git.libreoffice.org/core/+/4cd7489f5898394730b794bdecbc29800cf23627%5E%21/ ? Repro on Ubuntu 20.04 with GNOME 3.36.8 + Wayland and: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 61b41646c5a93ca24f2c9f143cdb0da2c9258989 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=84909 [Bug 84909] [META] Enhancing Impress/Draw toolbars and context menu -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 84909] [META] Enhancing Impress/Draw toolbars and context menu
https://bugs.documentfoundation.org/show_bug.cgi?id=84909 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||154946 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154946 [Bug 154946] Draw/Impress Standard toolbar missing many icons -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154945] Endnotes are not coming continuous, coming on new page at the end of document even if there is space on last content page
https://bugs.documentfoundation.org/show_bug.cgi?id=154945 hemant363ku...@gmail.com changed: What|Removed |Added CC||hemant363ku...@gmail.com --- Comment #1 from hemant363ku...@gmail.com --- Created attachment 186826 --> https://bugs.documentfoundation.org/attachment.cgi?id=186826=edit File having endnotes position issue -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154945] Endnotes are not coming continuous, coming on new page at the end of document even if there is space on last content page
https://bugs.documentfoundation.org/show_bug.cgi?id=154945 hemant363ku...@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 CC||vmik...@collabora.com Status|UNCONFIRMED |NEW -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154945] New: Endnotes are not coming continuous, coming on new page at the end of document even if there is space on last content page
https://bugs.documentfoundation.org/show_bug.cgi?id=154945 Bug ID: 154945 Summary: Endnotes are not coming continuous, coming on new page at the end of document even if there is space on last content page Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: hemant363ku...@gmail.com Description: On page no 103, endnotes should start just after end of document(endnotes heading on last page of doc) on same page. Instead, they cause new page to be created and start from that page even if space is there to accomodate some endnotes on last existing page itself of doc. Seems continuous endpoints compat settings is not working as expected as mentioned in https://vmiklos.hu/blog/sw-continuous-endnotes.html Steps to Reproduce: 1.Open the file with LibreOffice Writer 2.Go to page 103 having heading "Endnotes" Actual Results: Endnotes start on new page than on existing last page of document Expected Results: Endnotes should start at the end of content of doc i.e. after "Endnotes" heading Reproducible: Always User Profile Reset: No Additional Info: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 3ec73488e447a693a14a773a7fb96938036c0324 CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-IN (en_IN); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113359] [META] Calc toolbar bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=113359 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||36943 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=36943 [Bug 36943] Clicking 'Edit Points' button in Calc doesnt show 'Edit Points' toolbar -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 36943] Clicking 'Edit Points' button in Calc doesnt show 'Edit Points' toolbar
https://bugs.documentfoundation.org/show_bug.cgi?id=36943 Stéphane Guillou (stragu) changed: What|Removed |Added Hardware|Other |All Blocks||113359 CC||stephane.guillou@libreoffic ||e.org --- Comment #57 from Stéphane Guillou (stragu) --- Still reproducible in: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 61b41646c5a93ca24f2c9f143cdb0da2c9258989 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=113359 [Bug 113359] [META] Calc toolbar bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154929] [META] Accessibility Check sidebar deck, Automatic Accessibility Checking
https://bugs.documentfoundation.org/show_bug.cgi?id=154929 Dieter changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108742] [META] Shape points (glue points) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108742 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||154934 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154934 [Bug 154934] Disappearing Edit Points toolbar set by View>Toolbars>Edit Points -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154934] Disappearing Edit Points toolbar set by View>Toolbars>Edit Points
https://bugs.documentfoundation.org/show_bug.cgi?id=154934 Stéphane Guillou (stragu) changed: What|Removed |Added Version|7.4.6.2 release |Inherited From OOo CC||stephane.guillou@libreoffic ||e.org OS|Windows (All) |All Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Blocks||108742, 84909 --- Comment #1 from Stéphane Guillou (stragu) --- Reproduced with a recent master build: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 61b41646c5a93ca24f2c9f143cdb0da2c9258989 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded If the toolbar is turned on via the menu, it remains visible until edit point mode is entered with Edit > Points (or F8), a shape is selected and then deselected. It then disappears. I'd expect the toolbar to remain visible if I decided to show it by turning it on in the menu (even if everything is greyed out). At least so the other toolbars don't jump to a different position every time edit point mode is entered. Already the case in OOo 3.3, so inherited. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=84909 [Bug 84909] [META] Enhancing Impress/Draw toolbars and context menu https://bugs.documentfoundation.org/show_bug.cgi?id=108742 [Bug 108742] [META] Shape points (glue points) bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 84909] [META] Enhancing Impress/Draw toolbars and context menu
https://bugs.documentfoundation.org/show_bug.cgi?id=84909 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||154934 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154934 [Bug 154934] Disappearing Edit Points toolbar set by View>Toolbars>Edit Points -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 86630] MENU: Easily insert page number into header/footer with extended menu Insert
https://bugs.documentfoundation.org/show_bug.cgi?id=86630 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org --- Comment #30 from Stéphane Guillou (stragu) --- Given that we now have the header/footer dropdown menu's "Insert page number" and the Insert > Page Number dialog, I think this report can be closed. There certainly is space for improvement in the dialog (including physical space: adding functionalities wouldn't make it too cluttered), but new specific enhancement requests can be opened as follow-ups. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: chart2/source
chart2/source/model/main/DataPointProperties.cxx | 42 +++---
chart2/source/model/main/DataSeriesProperties.cxx |2 -
chart2/source/tools/CharacterProperties.cxx | 11 +++--
chart2/source/tools/FillProperties.cxx| 18 +
chart2/source/tools/LinePropertiesHelper.cxx |7 ++-
chart2/source/tools/SceneProperties.cxx |6 +--
6 files changed, 46 insertions(+), 40 deletions(-)
New commits:
commit 5cd9de202765e243e41416802f3e4486b8a96f16
Author: Mike Kaganski
AuthorDate: Thu Apr 20 19:39:28 2023 +0200
Commit: Mike Kaganski
CommitDate: Thu Apr 20 22:42:57 2023 +0200
Add a bit of consistency
Change-Id: Ib201a8cec7c7a4a0a5cbd3d7e7d6156f8e8e59a1
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150717
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
diff --git a/chart2/source/model/main/DataPointProperties.cxx
b/chart2/source/model/main/DataPointProperties.cxx
index 267bf9014dca..819336edd9c4 100644
--- a/chart2/source/model/main/DataPointProperties.cxx
+++ b/chart2/source/model/main/DataPointProperties.cxx
@@ -35,6 +35,8 @@
#include
#include
+#include
+
using namespace ::com::sun::star;
using ::com::sun::star::beans::Property;
@@ -450,8 +452,8 @@ void DataPointProperties::AddPropertiesToVector(
void DataPointProperties::AddDefaultsToMap(
::chart::tPropertyValueMap & rOutMap )
{
-PropertyHelper::setPropertyValueDefault< sal_Int32 >( rOutMap,
PROP_DATAPOINT_COLOR, 0x0099ccff ); // blue 8
-PropertyHelper::setPropertyValueDefault< sal_Int16 >( rOutMap,
PROP_DATAPOINT_TRANSPARENCY, 0 );
+PropertyHelper::setPropertyValueDefault( rOutMap, PROP_DATAPOINT_COLOR,
Color(0x99, 0xcc, 0xff) ); // blue 8
+PropertyHelper::setPropertyValueDefault( rOutMap,
PROP_DATAPOINT_TRANSPARENCY, sal_Int16(0) );
//fill
PropertyHelper::setPropertyValueDefault( rOutMap,
PROP_DATAPOINT_FILL_STYLE, drawing::FillStyle_SOLID );
@@ -462,29 +464,29 @@ void DataPointProperties::AddDefaultsToMap(
PropertyHelper::setPropertyValueDefault( rOutMap,
PROP_DATAPOINT_FILL_BACKGROUND, false );
//border
-PropertyHelper::setPropertyValueDefault< sal_Int32 >( rOutMap,
PROP_DATAPOINT_BORDER_COLOR, 0x00 ); // black
+PropertyHelper::setPropertyValueDefault( rOutMap,
PROP_DATAPOINT_BORDER_COLOR, COL_BLACK );
PropertyHelper::setPropertyValueDefault( rOutMap,
PROP_DATAPOINT_BORDER_STYLE, drawing::LineStyle_SOLID ); //
drawing::LineStyle_NONE
-PropertyHelper::setPropertyValueDefault< sal_Int32 >( rOutMap,
PROP_DATAPOINT_BORDER_WIDTH, 0 );
+PropertyHelper::setPropertyValueDefault( rOutMap,
PROP_DATAPOINT_BORDER_WIDTH, sal_Int32(0) );
PropertyHelper::setEmptyPropertyValueDefault( rOutMap,
PROP_DATAPOINT_BORDER_DASH_NAME );
-PropertyHelper::setPropertyValueDefault< sal_Int16 >( rOutMap,
PROP_DATAPOINT_BORDER_TRANSPARENCY, 0 );
+PropertyHelper::setPropertyValueDefault( rOutMap,
PROP_DATAPOINT_BORDER_TRANSPARENCY, sal_Int16(0) );
//line
PropertyHelper::setPropertyValueDefault( rOutMap,
LinePropertiesHelper::PROP_LINE_STYLE, drawing::LineStyle_SOLID );
-PropertyHelper::setPropertyValueDefault< sal_Int32 >( rOutMap,
LinePropertiesHelper::PROP_LINE_WIDTH, 0 );
+PropertyHelper::setPropertyValueDefault( rOutMap,
LinePropertiesHelper::PROP_LINE_WIDTH, sal_Int32(0) );
PropertyHelper::setPropertyValueDefault( rOutMap,
LinePropertiesHelper::PROP_LINE_DASH, drawing::LineDash());
PropertyHelper::setEmptyPropertyValueDefault( rOutMap,
LinePropertiesHelper::PROP_LINE_DASH_NAME );
PropertyHelper::setPropertyValueDefault( rOutMap,
LinePropertiesHelper::PROP_LINE_CAP, drawing::LineCap_BUTT);
//fill bitmap
-PropertyHelper::setPropertyValueDefault< sal_Int16 >( rOutMap,
FillProperties::PROP_FILL_BITMAP_OFFSETX, 0 );
-PropertyHelper::setPropertyValueDefault< sal_Int16 >( rOutMap,
FillProperties::PROP_FILL_BITMAP_OFFSETY, 0 );
-PropertyHelper::setPropertyValueDefault< sal_Int16 >( rOutMap,
FillProperties::PROP_FILL_BITMAP_POSITION_OFFSETX, 0 );
-PropertyHelper::setPropertyValueDefault< sal_Int16 >( rOutMap,
FillProperties::PROP_FILL_BITMAP_POSITION_OFFSETY, 0 );
+PropertyHelper::setPropertyValueDefault( rOutMap,
FillProperties::PROP_FILL_BITMAP_OFFSETX, sal_Int16(0) );
+PropertyHelper::setPropertyValueDefault( rOutMap,
FillProperties::PROP_FILL_BITMAP_OFFSETY, sal_Int16(0) );
+PropertyHelper::setPropertyValueDefault( rOutMap,
FillProperties::PROP_FILL_BITMAP_POSITION_OFFSETX, sal_Int16(0) );
+PropertyHelper::setPropertyValueDefault( rOutMap,
FillProperties::PROP_FILL_BITMAP_POSITION_OFFSETY, sal_Int16(0) );
PropertyHelper::setPropertyValueDefault( rOutMap,
FillProperties::PROP_FILL_BITMAP_RECTANGLEPOINT,
drawing::RectanglePoint_MIDDLE_MIDDLE );
PropertyHelper::setPropertyValueDefault( rOutMap,
FillProperties::PROP_FILL_BITMAP_LOGICALSIZE, true );
-
[Libreoffice-bugs] [Bug 154944] [ feature request ] please improve the tabbed interface
https://bugs.documentfoundation.org/show_bug.cgi?id=154944 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO Summary|[ feature request ] please |[ feature request ] please |improve the interface |improve the tabbed ||interface --- Comment #4 from Stéphane Guillou (stragu) --- (In reply to yogilok from comment #0) > Created attachment 186824 [details] > no icons in ribbon > > First menus are getting too long or cluttered you can make them shorter by > grouping similar items in sub menus or using dialog boxes There are a few other UI options to choose from if you want to use menus and submenus. The tabbed interface is supposed to expose most functions directly, not hide them away in submenus. If you have suggestions for improvements to the tabbed interface, please be more specific (e.g. "functions A, B and C should be grouped together in one column"). Probably better to open a new report for these smaller improvements. > second tabbed interface does not show icons at first. They only show after I > press the arrow for an extension. This is already reported in bug 140557. > I think tabbed and groupedbar should feature all icons and the arrows should > slide or move them rather than show an extension. Maybe you'd like to make this idea the focus of this report? (Trying to stick to one issue per report.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154428] FILESAVE Shapes vanish from a Writer Frame after grouping and anchoring operation (gtk3 and kf5)
https://bugs.documentfoundation.org/show_bug.cgi?id=154428 Stéphane Guillou (stragu) changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=15 | |4914| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154827] Regression in 7.5.x: Graphics anchored in Writer as character become anchored at paragraph when reopening the document
https://bugs.documentfoundation.org/show_bug.cgi?id=154827 Stéphane Guillou (stragu) changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=15 | |4914| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152614] Database Form Creation Wizard incorrectly distributes form controls in document.
https://bugs.documentfoundation.org/show_bug.cgi?id=152614 Stéphane Guillou (stragu) changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=15 | |4914| CC||dralexander_vandenpanhuysen ||@telenet.be --- Comment #7 from Stéphane Guillou (stragu) --- *** Bug 154914 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108440] [META] Database form bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108440 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on|154914 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154914 [Bug 154914] Elements overlapped in Base form created with wizard -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154914] Elements overlapped in Base form created with wizard
https://bugs.documentfoundation.org/show_bug.cgi?id=154914 Stéphane Guillou (stragu) changed: What|Removed |Added Status|NEW |RESOLVED Blocks|108440 | Resolution|--- |DUPLICATE See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=15 | |4827, | |https://bugs.documentfounda | |tion.org/show_bug.cgi?id=15 | |4428, | |https://bugs.documentfounda | |tion.org/show_bug.cgi?id=15 | |2614| Keywords|regression | Regression By|Noel Grandin| --- Comment #5 from Stéphane Guillou (stragu) --- Good spotting, thank you. I moved the info there. *** This bug has been marked as a duplicate of bug 152614 *** Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108440 [Bug 108440] [META] Database form bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154827] Regression in 7.5.x: Graphics anchored in Writer as character become anchored at paragraph when reopening the document
https://bugs.documentfoundation.org/show_bug.cgi?id=154827 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2614 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108440] [META] Database form bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108440 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||152614 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152614 [Bug 152614] Database Form Creation Wizard incorrectly distributes form controls in document. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154428] FILESAVE Shapes vanish from a Writer Frame after grouping and anchoring operation (gtk3 and kf5)
https://bugs.documentfoundation.org/show_bug.cgi?id=154428 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2614 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152614] Database Form Creation Wizard incorrectly distributes form controls in document.
https://bugs.documentfoundation.org/show_bug.cgi?id=152614 Stéphane Guillou (stragu) changed: What|Removed |Added Version|7.5.1.2 release |7.5.0.0 alpha1+ Blocks||108440 Keywords|bibisectRequest |bibisected, bisected See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4827, ||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4428 Regression By||Noel Grandin CC||noelgran...@gmail.com, ||stephane.guillou@libreoffic ||e.org --- Comment #6 from Stéphane Guillou (stragu) --- (moving the info from duplicate bug 154914) Reproduced in 7.5.2.2 and a recent master build: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 61b41646c5a93ca24f2c9f143cdb0da2c9258989 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Bibisected the issue with the linux-64-7.5 repo to the first bad commit 6f10bfc3f53a7d88037a32deadcc7f3be94c061e which points to the core commit: commit 8611f6e259b807b4f19c8dc0eab86ca648891ce3 author Noel Grandin Thu May 27 10:27:46 2021 +0200 committer Noel Grandin Mon Aug 29 13:44:02 2022 +0200 ref-count SdrObject Reviewed-on: https://gerrit.libreoffice.org/c/core/+/138837 Steps to reproduce: 1. Open database with some fields 2. Forms > Use wizard to create form 3. Field selection: all fields 4. Arrange controls: "Columnar - labels on top" (same with "Columnar - labels left" and "In block - labels above") 5. Click Finish Results: elements overlap. gen and kf5 VCLs not affected. Attachment 186800 shows the difference before and after the commit. Noel, can you please have a look? Same commit caused bug 154827 and bug 154428. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108440 [Bug 108440] [META] Database form bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154944] [ feature request ] please improve the interface
https://bugs.documentfoundation.org/show_bug.cgi?id=154944 --- Comment #3 from yogilok --- In short the arrows should slide the icons , not show an extension. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154944] [ feature request ] please improve the interface
https://bugs.documentfoundation.org/show_bug.cgi?id=154944 --- Comment #2 from yogilok --- Created attachment 186825 --> https://bugs.documentfoundation.org/attachment.cgi?id=186825=edit extension does not disapper over dialogue box -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154944] [ feature request ] please improve the interface
https://bugs.documentfoundation.org/show_bug.cgi?id=154944 --- Comment #1 from yogilok --- third groupedbar compact has an extension that does not disappear when I start a dialogue box. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154944] New: [ feature request ] please improve the interface
https://bugs.documentfoundation.org/show_bug.cgi?id=154944 Bug ID: 154944 Summary: [ feature request ] please improve the interface Product: LibreOffice Version: 7.4.6.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: enhancement Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: halimf...@gmail.com Created attachment 186824 --> https://bugs.documentfoundation.org/attachment.cgi?id=186824=edit no icons in ribbon First menus are getting too long or cluttered you can make them shorter by grouping similar items in sub menus or using dialog boxes second tabbed interface does not show icons at first. They only show after I press the arrow for an extension. I think tabbed and groupedbar should feature all icons and the arrows should slide or move them rather than show an extension. In the meantime please fix these issues. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 131323] Libreoffice pdf conversion fails in FIPS mode
https://bugs.documentfoundation.org/show_bug.cgi?id=131323 --- Comment #19 from Caolán McNamara --- https://wiki.documentfoundation.org/QA/Bibisect might be your friend there, git repos of pre-built binaries of libreoffice that can be used to git bisect to find the source commit range of the change. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154857] when switching between application colors, formula content does not update
https://bugs.documentfoundation.org/show_bug.cgi?id=154857 Simon Mikkelsen changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154857] when switching between application colors, formula content does not update
https://bugs.documentfoundation.org/show_bug.cgi?id=154857 --- Comment #7 from Simon Mikkelsen --- sorry for late reply, for some reason it didn't send and saw it just now. libreoffice info: Version: 7.5.2.2 (X86_64) / LibreOffice Community Build ID: 50(Build:2) CPU threads: 16; OS: Linux 6.1; UI render: default; VCL: kf5 (cairo+wayland) Locale: da-DK (en_DK.UTF-8); UI: en-GB 7.5.2-1 Calc: threaded info: System: Host: zephyrusg14-ga402rkga402rk Kernel: 6.1.23-1-MANJARO arch: x86_64 bits: 64 Desktop: KDE Plasma v: 5.27.4 Distro: Manjaro Linux Machine: Type: Laptop System: ASUSTeK product: ROG Zephyrus G14 GA402RK_GA402RK Mobo: ASUSTeK model: GA402RK v: 1.0 serial: UEFI: American Megatrends LLC. v: GA402RK.318 date: 03/09/2023 CPU: Info: 8-core model: AMD Ryzen 9 6900HS with Radeon Graphics bits: 64 type: MT MCP cache: L2: 4 MiB Speed (MHz): avg: 1591 min/max: 1600/4934 cores: 1: 1600 2: 1372 3: 1368 4: 1600 5: 1304 6: 1600 7: 3300 8: 1600 9: 1600 10: 1283 11: 1600 12: 1600 13: 1306 14: 1366 15: 1600 16: 1364 Graphics: Device-1: AMD Navi 23 [Radeon RX 6650 XT / 6700S 6800S] driver: amdgpu v: kernel Device-2: AMD Rembrandt [Radeon 680M] driver: amdgpu v: kernel Device-3: Quanta USB2.0 HD UVC WebCam type: USB driver: uvcvideo Display: wayland server: X.org v: 1.21.1.8 with: Xwayland v: 23.1.1 compositor: kwin_wayland driver: X: loaded: amdgpu unloaded: modesetting,radeon dri: radeonsi gpu: amdgpu,amdgpu resolution: 1707x1067 API: OpenGL v: 4.6 Mesa 23.0.2 renderer: AMD Radeon Graphics (rembrandt LLVM 15.0.7 DRM 3.49 6.1.23-1-MANJARO) Drives: Local Storage: total: 1.86 TiB used: 154.33 GiB (8.1%) ID-1: /dev/nvme0n1 vendor: Toshiba model: N/A size: 1.86 TiB Partition: ID-1: / size: 891.53 GiB used: 77.36 GiB (8.7%) fs: ext4 dev: /dev/nvme0n1p5 ID-2: /boot/efi size: 256 MiB used: 67.8 MiB (26.5%) fs: vfat dev: /dev/nvme0n1p1 ID-3: /home size: 93.13 GiB used: 76.9 GiB (82.6%) fs: ntfs dev: /dev/nvme0n1p6 Info: Processes: 405 Uptime: 10h 5m Memory: 30.59 GiB used: 11.72 GiB (38.3%) Shell: Zsh inxi: 3.3.26 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154113] Sections: after copy-paste, layout is broken until reload
https://bugs.documentfoundation.org/show_bug.cgi?id=154113 Mike Kaganski changed: What|Removed |Added Summary|Sections merge after|Sections: after copy-paste, |copy-paste, and layout is |layout is broken until |broken until reload |reload -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107738] [META] Section bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107738 Bug 107738 depends on bug 154113, which changed state. Bug 154113 Summary: Sections merge after copy-paste, and layout is broken until reload https://bugs.documentfoundation.org/show_bug.cgi?id=154113 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154113] Sections merge after copy-paste, and layout is broken until reload
https://bugs.documentfoundation.org/show_bug.cgi?id=154113 Mike Kaganski changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #3 from Mike Kaganski --- So let me limit this to the incorrect rendering (the swapped order of last two paragraphs), which was a regression, and is fixed now. The behavior of sections (changed number and relations of sections) is different, pre-existing, and unclear what to really expect, so need a different issue. Closing fixed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154849] [macOS] Bug Fix Submission with Swift Language (swiftlang) file(s) Guidance Request
https://bugs.documentfoundation.org/show_bug.cgi?id=154849 --- Comment #11 from zb...@systemresearch.com --- (In reply to Julien Nabet from comment #9) > Some feedback from ESC … (In reply to Julien Nabet from comment #10) > Argh, I should have re-read, you indicated … Julien, Thank you for facilitating the communications. Great comments from everyone! I will circle back with additional details on what I'm proposing to contribute… after I'm past a 48 hours deadline time crunch. --Marc (bugz) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 131323] Libreoffice pdf conversion fails in FIPS mode
https://bugs.documentfoundation.org/show_bug.cgi?id=131323 --- Comment #18 from James Blaszkiewicz --- I was able to reproduce this issue in LibreOffice 7.3.3.2 with FIPS enabled, >Convert /var/tmp/PP4.docx -> /var/tmp/PP4.pdf using filter : writer_pdf_Export >Error: Please verify input parameters... (SfxBaseModel::impl_store > > failed: 0xc10(Error Area:Io Class:Write Code:16) >/home/buildslave/source/libo-core/sfx2/source/doc/sfxbasemodel.cxx:3202 >>/home/buildslave/source/libo-core/sfx2/source/doc/sfxbasemodel.cxx:1775) I also wanted to test if it was a simple permissions issue, so I tried pointing the output path at a folder without write permissions, but with an output folder that libreoffice is unable to write to, it outputs 0x507(Error Area:Io Class:Access Code:7)) while the error we're seeing is 0xc10(Error Area:Io Class:Write Code:16), so I don't believe this is a write permissions issue. Also the only conversion that fails is to pdf. With some research of similar issues, this 0xc10 is ERRCODE_IO_CANTWRITE which is somewhat generic, and can be set in several places. I suspect it might be on failure of creation of a temp file, but I can't be sure without either more log output from LibreOffice, or a debug run with gdb. When testing with LibreOffice 7.5.2 in the same FIPS enabled cluster, the command was successful and the same office document was correctly converted to PDF. Is anyone more well-versed in the code than Michael Tighe and myself able to point us in the direction of what the fix was or how to determine that? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154113] Sections merge after copy-paste, and layout is broken until reload
https://bugs.documentfoundation.org/show_bug.cgi?id=154113 --- Comment #2 from Commit Notification --- Mike Kaganski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/efb3c57851d29440ef086c68a6c1ddbb8bc8fc00 tdf#154113: do not forget to split the outermost section frame It will be available in 7.6.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. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154113] Sections merge after copy-paste, and layout is broken until reload
https://bugs.documentfoundation.org/show_bug.cgi?id=154113 Commit Notification changed: What|Removed |Added Whiteboard||target:7.6.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/qa sw/source
sw/qa/extras/layout/data/three_sections.fodt | 18 ++
sw/qa/extras/layout/layout3.cxx | 41 ++
sw/source/core/inc/sectfrm.hxx |2
sw/source/core/layout/frmtool.cxx| 63 +++--
sw/source/core/layout/layhelp.hxx|3 +
sw/source/core/layout/sectfrm.cxx| 79 ++-
6 files changed, 127 insertions(+), 79 deletions(-)
New commits:
commit efb3c57851d29440ef086c68a6c1ddbb8bc8fc00
Author: Mike Kaganski
AuthorDate: Thu Apr 20 11:18:34 2023 +0300
Commit: Mike Kaganski
CommitDate: Thu Apr 20 21:35:52 2023 +0200
tdf#154113: do not forget to split the outermost section frame
... when the inserted section node is not the first one.
The very first frame, where InsertCnt_ puts content to, may already have
some content after the insertion position. When an inner section ends,
the current section needs a new frame, and the rest of content must go
to that new frame. Previously, the new empty frame was created without
taking the content move into account.
This moves the split into the single place inside InsertCnt_, to avoid
special processing in MakeFrames.
Change-Id: I1335ebbc620af0f2b064141e8267e5bd1af0b195
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150675
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
diff --git a/sw/qa/extras/layout/data/three_sections.fodt
b/sw/qa/extras/layout/data/three_sections.fodt
new file mode 100644
index ..9233fed89085
--- /dev/null
+++ b/sw/qa/extras/layout/data/three_sections.fodt
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Select the text below, copy to clipboard, and paste from clipboard,
replacing the selection.
+
+-- Start selection here. Section1
+
+
+Section2
+
+
+Section3. End selection here --
+
+
+
+
\ No newline at end of file
diff --git a/sw/qa/extras/layout/layout3.cxx b/sw/qa/extras/layout/layout3.cxx
index 64d9862ea990..687b1c78ddd7 100644
--- a/sw/qa/extras/layout/layout3.cxx
+++ b/sw/qa/extras/layout/layout3.cxx
@@ -1602,6 +1602,47 @@ CPPUNIT_TEST_FIXTURE(SwLayoutWriter3, testTdf138124)
assertXPath(pXml,
"/root/page/ftncont/ftn/txt//SwLinePortion[@type='PortionType::FlyCnt']", 1);
}
+CPPUNIT_TEST_FIXTURE(SwLayoutWriter3, testTdf154113)
+{
+createSwDoc("three_sections.fodt");
+Scheduler::ProcessEventsToIdle();
+
+dispatchCommand(mxComponent, ".uno:GoToStartOfDoc", {});
+dispatchCommand(mxComponent, ".uno:GoToNextPara", {});
+dispatchCommand(mxComponent, ".uno:EndOfDocumentSel", {}); // to the end
of current section!
+dispatchCommand(mxComponent, ".uno:EndOfDocumentSel", {}); // to the end
of the document.
+
+auto xModel = mxComponent.queryThrow();
+auto xSelected =
xModel->getCurrentSelection().queryThrow();
+CPPUNIT_ASSERT_EQUAL(sal_Int32(1), xSelected->getCount());
+auto xRange = xSelected->getByIndex(0).queryThrow();
+CPPUNIT_ASSERT_EQUAL(OUString("<-- Start selection here. Section1"
SAL_NEWLINE_STRING
+ "Section2" SAL_NEWLINE_STRING "Section3. End
selection here -->"),
+ xRange->getString());
+
+dispatchCommand(mxComponent, ".uno:Cut", {});
+
+xSelected =
xModel->getCurrentSelection().queryThrow();
+CPPUNIT_ASSERT_EQUAL(sal_Int32(1), xSelected->getCount());
+xRange = xSelected->getByIndex(0).queryThrow();
+CPPUNIT_ASSERT_EQUAL(OUString(), xRange->getString());
+
+dispatchCommand(mxComponent, ".uno:Paste", {});
+
+xmlDocUniquePtr pXml = parseLayoutDump();
+
+// Without the fix in place, this would fail with
+// - Expected: 3
+// - Actual : 2
+assertXPath(pXml, "/root/page/body/section", 3);
+assertXPath(pXml,
"/root/page/body/section[1]/txt/SwParaPortion/SwLineLayout", "portion",
+"<-- Start selection here. Section1");
+assertXPath(pXml,
"/root/page/body/section[2]/txt/SwParaPortion/SwLineLayout", "portion",
+"Section2");
+assertXPath(pXml,
"/root/page/body/section[3]/txt/SwParaPortion/SwLineLayout", "portion",
+"Section3. End selection here -->");
+}
+
CPPUNIT_PLUGIN_IMPLEMENT();
/* vim:set shiftwidth=4 softtabstop=4 expandtab: */
diff --git a/sw/source/core/inc/sectfrm.hxx b/sw/source/core/inc/sectfrm.hxx
index 6c40c6589f31..e08a9b0a7137 100644
--- a/sw/source/core/inc/sectfrm.hxx
+++ b/sw/source/core/inc/sectfrm.hxx
@@ -109,7 +109,7 @@ public:
* Splits the SectionFrame surrounding the pFrame up in two parts:
* pFrame and the start of the 2nd part
*/
-bool SplitSect( SwFrame* pFrame, bool bAfter );
+SwSectionFrame* SplitSect( SwFrame* pFrameStartAfter, SwFrame*
pFramePutAfter );
void DelEmpty( bool bRemove ); // Like Cut(), except for that Follow
chaining is maintained
SwFootnoteContFrame* ContainsFootnoteCont( const SwFootnoteContFrame*
pCont = nullptr
[Libreoffice-commits] core.git: bridges/source
bridges/source/cpp_uno/gcc3_ios/unwind-cxx.h |2 ++ 1 file changed, 2 insertions(+) New commits: commit 153263957b22e2d5f76f951366d44c182c22c260 Author: Tor Lillqvist AuthorDate: Thu Apr 20 17:43:03 2023 +0300 Commit: Tor Lillqvist CommitDate: Thu Apr 20 21:35:01 2023 +0200 Fix compilation with latest Xcode with iOS SDK 16.4 Alternatively we could just remove lots of stuff that we apparently don't actually need from this file, including the problematic typedef and its uses. _Unwind_Exception_Class now gets typedeffed in as uint64_t which effectively is the same as the unsigned __attribute__((__mode__(__DI__))) that is used here. Change-Id: Id96d43eb481ee4ae97dd315aa2fd741e5f627916 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150702 Reviewed-by: Patrick Luby Reviewed-by: Tor Lillqvist Tested-by: Tor Lillqvist diff --git a/bridges/source/cpp_uno/gcc3_ios/unwind-cxx.h b/bridges/source/cpp_uno/gcc3_ios/unwind-cxx.h index 83ed084860fd..aa35a5bc75e6 100644 --- a/bridges/source/cpp_uno/gcc3_ios/unwind-cxx.h +++ b/bridges/source/cpp_uno/gcc3_ios/unwind-cxx.h @@ -46,7 +46,9 @@ typedef unsigned _Unwind_Word __attribute__((__mode__(__word__))); typedef signed _Unwind_Sword __attribute__((__mode__(__word__))); typedef unsigned _Unwind_Word __attribute__((__mode__(__word__))); typedef unsigned _Unwind_Ptr __attribute__((__mode__(__pointer__))); +#if !defined __IPHONE_16_4 || __IPHONE_OS_VERSION_MAX_ALLOWED < __IPHONE_16_4 typedef unsigned _Unwind_Exception_Class __attribute__((__mode__(__DI__))); +#endif typedef unsigned _Unwind_Internal_Ptr __attribute__((__mode__(__pointer__))); #pragma GCC visibility push(default)
[Libreoffice-bugs] [Bug 154882] New Table Styles in Impress does not save font color in top-left cell
https://bugs.documentfoundation.org/show_bug.cgi?id=154882 --- Comment #9 from Commit Notification --- Maxim Monastirsky committed a patch related to this issue. It has been pushed to "libreoffice-7-5": https://git.libreoffice.org/core/commit/18ad97d122fbaf7f120502fa73cea773dfe38455 tdf#154882: svx: don't overwrite the first cell's style It will be available in 7.5.4. 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. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'libreoffice-7-5' - svx/source
svx/source/unodraw/unoshtxt.cxx |5 - 1 file changed, 4 insertions(+), 1 deletion(-) New commits: commit 18ad97d122fbaf7f120502fa73cea773dfe38455 Author: Maxim Monastirsky AuthorDate: Sun Mar 26 09:59:09 2023 +0300 Commit: Xisco Fauli CommitDate: Thu Apr 20 21:21:32 2023 +0200 tdf#154882: svx: don't overwrite the first cell's style i.e. new Draw document, change the char formatting in the default drawing style (e.g. font size), insert a table and fill its cells with text. Save and reload. After reload the first cell inherits the formatting of the default DS, instead of its assigned cell style. But dragging the table around shows the correct formatting in the dragging overlay, and it's also correct when copy & pasting the table. This is caused by the order of things at import, as a table is created initially with a single cell at least, and it gets its cell style assignment too early. There is also similar code to what is changed here in SdrTextObj:: BegTextEdit, and it's rightfully overridden by SdrTableObj. This appears to be a regression from 4-0, but I'm not sure which commit and what exactly changed there. Change-Id: Id096c7b5f330d6abd8f5b01c96448a9d8aac8001 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/149616 Tested-by: Jenkins Reviewed-by: Maxim Monastirsky (cherry picked from commit f0287aad967761d46cb6903fc0d985a536408176) Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150716 Tested-by: Xisco Fauli Reviewed-by: Xisco Fauli diff --git a/svx/source/unodraw/unoshtxt.cxx b/svx/source/unodraw/unoshtxt.cxx index 168212aaa159..2743ccbaf6ee 100644 --- a/svx/source/unodraw/unoshtxt.cxx +++ b/svx/source/unodraw/unoshtxt.cxx @@ -592,7 +592,10 @@ SvxTextForwarder* SvxTextEditSourceImpl::GetBackgroundTextForwarder() // its empty, so we have to force the outliner to initialise itself mpOutliner->SetText( "", mpOutliner->GetParagraph( 0 ) ); -if(mpObject->GetStyleSheet()) +auto pCell = dynamic_cast(mpText); +if (pCell && pCell->GetStyleSheet()) +mpOutliner->SetStyleSheet( 0, pCell->GetStyleSheet()); +else if (mpObject->GetStyleSheet()) mpOutliner->SetStyleSheet( 0, mpObject->GetStyleSheet()); } }
[Libreoffice-bugs] [Bug 154882] New Table Styles in Impress does not save font color in top-left cell
https://bugs.documentfoundation.org/show_bug.cgi?id=154882 Commit Notification changed: What|Removed |Added Whiteboard||target:7.5.4 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103152] [META] Writer image bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103152 BogdanB changed: What|Removed |Added Depends on||136482 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=136482 [Bug 136482] The image in the document is write-protected: can be deleted from Navigator, but not directly -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136482] The image in the document is write-protected: can be deleted from Navigator, but not directly
https://bugs.documentfoundation.org/show_bug.cgi?id=136482 BogdanB changed: What|Removed |Added Blocks||103152 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103152 [Bug 103152] [META] Writer image bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136482] The image in the document is write-protected: can be deleted from Navigator, but not directly
https://bugs.documentfoundation.org/show_bug.cgi?id=136482 BogdanB changed: What|Removed |Added Summary|new LO document is |The image in the document |write-protected |is write-protected: can be ||deleted from Navigator, but ||not directly CC||buzea.bog...@libreoffice.or ||g -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154428] FILESAVE Shapes vanish from a Writer Frame after grouping and anchoring operation (gtk3 and kf5)
https://bugs.documentfoundation.org/show_bug.cgi?id=154428 --- Comment #6 from Roland Baudin --- Good news! Will the fix be included in the next 7.5.x release? -- You are receiving this mail because: You are the assignee for the bug.
