[Libreoffice-bugs] [Bug 155734] It takes too long time to open an '.odt' document
https://bugs.documentfoundation.org/show_bug.cgi?id=155734 Julien Nabet changed: What|Removed |Added Ever confirmed|0 |1 Severity|enhancement |normal Status|UNCONFIRMED |NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155761] New: [LibreOffice Base] Table data text is black and unreadable in dark theme
https://bugs.documentfoundation.org/show_bug.cgi?id=155761 Bug ID: 155761 Summary: [LibreOffice Base] Table data text is black and unreadable in dark theme Product: LibreOffice Version: 7.5.4.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jiri.klete...@gmail.com Description: Table data text in view mode is black and unreadable in dark theme UI Steps to Reproduce: 1. Set Dark theme in settings and restart app 2. Open any database file with some table and data in it 3. Open that table and observe unreadable text Actual Results: Text is unreadable Expected Results: Text should be white/readable Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: cs-CZ (cs_CZ); UI: cs-CZ Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149270] Writer: Font of watermark is displayed incorrectly
https://bugs.documentfoundation.org/show_bug.cgi?id=149270 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g --- Comment #7 from BogdanB --- Please retest, looking good to me. Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: filter/source
filter/source/xslt/odf2xhtml/export/xhtml/body.xsl |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit a7b5fe0c813977347a8d10ac5a52862f6150fbc0 Author: Andrea Gelmini AuthorDate: Fri Jun 9 21:12:52 2023 +0200 Commit: Julien Nabet CommitDate: Sat Jun 10 07:13:39 2023 +0200 Fix typo Change-Id: Iaf94d6e4c771220167a17131b57be68290203b35 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152802 Tested-by: Jenkins Reviewed-by: Julien Nabet diff --git a/filter/source/xslt/odf2xhtml/export/xhtml/body.xsl b/filter/source/xslt/odf2xhtml/export/xhtml/body.xsl index 278b613c766c..a8a4aa0b0347 100644 --- a/filter/source/xslt/odf2xhtml/export/xhtml/body.xsl +++ b/filter/source/xslt/odf2xhtml/export/xhtml/body.xsl @@ -3000,7 +3000,7 @@ (realized style family 'section' is missing, see https://docs.oasis-open.org/office/OpenDocument/v1.3/os/schemas/OpenDocument-v1.3-schema-rng.html#12668 and wrote an issue to ODF TC: https://github.com/oasis-tcs/odf-tc/issues/49 -in addition the mapping of styleable ODF elements to their @style:family attribute is availabe in structured form (XML) in the ODF Toolkit generator project: +in addition the mapping of styleable ODF elements to their @style:family attribute is available in structured form (XML) in the ODF Toolkit generator project: https://github.com/tdf/odftoolkit/blob/master/generator/schema2template/src/test/resources/test-input/odf/generation/odfdom-java/dom/grammar-additions.xml#LL43C52-L43C52r-additions.xml#LL43C52-L43C52 -->
[Libreoffice-commits] core.git: filter/source
filter/source/xslt/odf2xhtml/export/xhtml/body.xsl |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit a7481809d7dd9072d965e7fd281b5f2020c09b97 Author: Andrea Gelmini AuthorDate: Fri Jun 9 21:13:15 2023 +0200 Commit: Julien Nabet CommitDate: Sat Jun 10 07:13:11 2023 +0200 Fix typo Change-Id: I64f539d427a61877a0647b7b4e1a217c5d913cc3 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152803 Tested-by: Jenkins Reviewed-by: Julien Nabet diff --git a/filter/source/xslt/odf2xhtml/export/xhtml/body.xsl b/filter/source/xslt/odf2xhtml/export/xhtml/body.xsl index 7b3c7e4d3b17..278b613c766c 100644 --- a/filter/source/xslt/odf2xhtml/export/xhtml/body.xsl +++ b/filter/source/xslt/odf2xhtml/export/xhtml/body.xsl @@ -2853,7 +2853,7 @@ - +
[Libreoffice-bugs] [Bug 155749] When we hide the numbering of a chapter level, it reappears when we reopen the document
https://bugs.documentfoundation.org/show_bug.cgi?id=155749 --- Comment #3 from fab@gmail.com --- Created attachment 187814 --> https://bugs.documentfoundation.org/attachment.cgi?id=187814=edit a sample file to test -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155749] When we hide the numbering of a chapter level, it reappears when we reopen the document
https://bugs.documentfoundation.org/show_bug.cgi?id=155749 --- Comment #2 from fab@gmail.com --- (In reply to m.a.riosv from comment #1) > Please can you paste the information in Menu/Help/About LibreOffice, there > is an icon to copy. > > And add a sample file to test. Version: 7.3.7.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Ubuntu package version: 1:7.3.7-0ubuntu0.22.04.3 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155417] Mailmerge edit in Libre Writer mailmerge wizard is bugged, doesn't function very well, cannot edit fields`
https://bugs.documentfoundation.org/show_bug.cgi?id=155417 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 155519] Shape Text Box Should Be Resizeable
https://bugs.documentfoundation.org/show_bug.cgi?id=155519 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 155512] pptx import doesn't import unused master slides
https://bugs.documentfoundation.org/show_bug.cgi?id=155512 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 155664] Reopening of calc sheets --off by 1-- size increase
https://bugs.documentfoundation.org/show_bug.cgi?id=155664 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 155664] Reopening of calc sheets --off by 1-- size increase
https://bugs.documentfoundation.org/show_bug.cgi?id=155664 --- Comment #5 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151967] Printing handouts on Impress requires Portrait/Landscape option
https://bugs.documentfoundation.org/show_bug.cgi?id=151967 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151967] Printing handouts on Impress requires Portrait/Landscape option
https://bugs.documentfoundation.org/show_bug.cgi?id=151967 --- Comment #3 from QA Administrators --- Dear dmchatterton, 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 151964] Can't print to 3x5 paper
https://bugs.documentfoundation.org/show_bug.cgi?id=151964 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151743] Software crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=151743 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151743] Software crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=151743 --- Comment #4 from QA Administrators --- Dear Iverson, 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 151964] Can't print to 3x5 paper
https://bugs.documentfoundation.org/show_bug.cgi?id=151964 --- Comment #5 from QA Administrators --- Dear David Zokaites, 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 97801] Writer (X)HTML export: missing page numbers in Table of Contents
https://bugs.documentfoundation.org/show_bug.cgi?id=97801 --- Comment #11 from QA Administrators --- Dear Martin Nathansen, 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 97007] ODF does not allow presentation:master-element as attribute of anim:set
https://bugs.documentfoundation.org/show_bug.cgi?id=97007 --- Comment #10 from QA Administrators --- Dear Regina Henschel, 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 91595] UI Escaping dialog Format Comments doesn't bring focus back to document
https://bugs.documentfoundation.org/show_bug.cgi?id=91595 --- Comment #9 from QA Administrators --- Dear Juanjo, 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 74574] EDITING: Crop dialogue shows rotated image un-rotated
https://bugs.documentfoundation.org/show_bug.cgi?id=74574 --- Comment #10 from QA Administrators --- Dear James Murray, 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 67320] EDITING: Paragraph ends at about 64 cm although the page width is much wider
https://bugs.documentfoundation.org/show_bug.cgi?id=67320 --- Comment #9 from QA Administrators --- Dear paris, 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 65944] punctuation after inline formula may go to the next line
https://bugs.documentfoundation.org/show_bug.cgi?id=65944 --- Comment #14 from QA Administrators --- Dear Yury, 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 59353] Running spell check with 'Check words with numbers' inserts unwanted character
https://bugs.documentfoundation.org/show_bug.cgi?id=59353 --- Comment #10 from QA Administrators --- Dear Ed, 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 42471] Undo of cell style background formatting does not work when cell is in edit mode / undo stack of cell editing is sort of separated..
https://bugs.documentfoundation.org/show_bug.cgi?id=42471 --- Comment #14 from QA Administrators --- Dear Michal Suchanek, 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 136754] FILEOPEN: CHART: incorrect background
https://bugs.documentfoundation.org/show_bug.cgi?id=136754 --- Comment #5 from QA Administrators --- Dear Xisco Faulí, 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 125704] PDF export of embedded PDF outputs PDF that looks different
https://bugs.documentfoundation.org/show_bug.cgi?id=125704 --- Comment #13 from QA Administrators --- Dear philipp.kloke, 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 139700] UI: no hoover over effect page size picker in tabbed mode
https://bugs.documentfoundation.org/show_bug.cgi?id=139700 --- Comment #2 from QA Administrators --- Dear Telesto, 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 124689] Moving the scrollbar of the slides pane after having opened a presentation makes the file dirty
https://bugs.documentfoundation.org/show_bug.cgi?id=124689 --- Comment #8 from QA Administrators --- Dear sergio.callegari, 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 121166] TRACK CHANGES: linked files changes are not shown in the master document
https://bugs.documentfoundation.org/show_bug.cgi?id=121166 --- Comment #18 from QA Administrators --- Dear Emanuele Gissi, 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 120702] PPTX import: shape text with multiple columns not the same as in MSO
https://bugs.documentfoundation.org/show_bug.cgi?id=120702 --- Comment #6 from QA Administrators --- Dear Timur, 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 117516] Linked table in Writer can't be reduced to a smaller size when reducing range
https://bugs.documentfoundation.org/show_bug.cgi?id=117516 --- Comment #4 from QA Administrators --- Dear Aron Budea, 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 118558] doesn't change format of page to 2 columns for Endnote page style
https://bugs.documentfoundation.org/show_bug.cgi?id=118558 --- Comment #6 from QA Administrators --- Dear Roman Kuznetsov, 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 113095] Dialog tab labels dont have sufficient padding on Windows
https://bugs.documentfoundation.org/show_bug.cgi?id=113095 --- Comment #11 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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-commits] core.git: sc/source
sc/source/core/data/table2.cxx |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit 97a4e4582698c74fa4fa5c2fed3cd48d4c66da8b
Author: Andrea Gelmini
AuthorDate: Fri Jun 9 21:13:56 2023 +0200
Commit: Adolfo Jayme Barrientos
CommitDate: Sat Jun 10 05:13:21 2023 +0200
Fix typo
Change-Id: I93f8dc6746a9173847e96f1ba16e5fdc4a817ced
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152804
Tested-by: Jenkins
Reviewed-by: Adolfo Jayme Barrientos
diff --git a/sc/source/core/data/table2.cxx b/sc/source/core/data/table2.cxx
index b35caa7459bb..ee65a31ab6bf 100644
--- a/sc/source/core/data/table2.cxx
+++ b/sc/source/core/data/table2.cxx
@@ -400,7 +400,7 @@ void ScTable::DeleteCol(
{
for (SCCOL nCol = nStartCol + nSize; nCol < aCol.size(); ++nCol)
aCol[nCol].SwapCol(aCol[nCol - nSize]);
-// When delete column(s), inicialize the last columns from the default
attributes
+// When delete column(s), initialize the last columns from the default
attributes
for (SCCOL nCol = aCol.size() - nSize; nCol < aCol.size(); ++nCol)
aCol[nCol].Init(nCol, aCol[nCol].GetTab(), rDocument, false);
}
[Libreoffice-bugs] [Bug 155749] When we hide the numbering of a chapter level, it reappears when we reopen the document
https://bugs.documentfoundation.org/show_bug.cgi?id=155749 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 --- Comment #1 from m.a.riosv --- Please can you paste the information in Menu/Help/About LibreOffice, 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 155758] FUNCTION: suggestion for SUM.IF()
https://bugs.documentfoundation.org/show_bug.cgi?id=155758 m.a.riosv changed: What|Removed |Added Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- I think SUM.IFS() that let's add several criteria, do what you need. https://help.libreoffice.org/latest/en-US/text/scalc/01/func_sumifs.html?DbPAR=CALC#bm_id658066580665806 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 111450] [META] SVG fileSave filter (Draw/Impress)
https://bugs.documentfoundation.org/show_bug.cgi?id=111450 Bug 111450 depends on bug 155479, which changed state. Bug 155479 Summary: MCGR: clumsy export of linear gradient to SVG https://bugs.documentfoundation.org/show_bug.cgi?id=155479 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'distro/cib/libreoffice-6-4' - sc/source
sc/source/filter/html/htmlpars.cxx | 10 ++
1 file changed, 10 insertions(+)
New commits:
commit bf50bfb5aa1f0dae37a703f1dc0ca1199693c3ce
Author: Eike Rathke
AuthorDate: Sat Feb 5 22:43:13 2022 +0100
Commit: Gabor Kelemen
CommitDate: Fri Jun 9 23:07:02 2023 +0200
Resolves: tdf#74577 tdf#92960 Create missing offsets in very outer table
... if local table is outer table.
Change-Id: I5996609264f4ad9efa8d76a8d0ab730bf1dded24
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/129540
Reviewed-by: Eike Rathke
Tested-by: Jenkins
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152805
Tested-by: Gabor Kelemen
Reviewed-by: Gabor Kelemen
diff --git a/sc/source/filter/html/htmlpars.cxx
b/sc/source/filter/html/htmlpars.cxx
index ae46949e4b21..34f481eba09c 100644
--- a/sc/source/filter/html/htmlpars.cxx
+++ b/sc/source/filter/html/htmlpars.cxx
@@ -752,6 +752,16 @@ void ScHTMLLayoutParser::SetWidths()
sal_uInt16 nMax = static_cast(pLocalColOffset->back());
if ( aPageSize.Width() < nMax )
aPageSize.setWidth( nMax );
+if (nTableLevel == 0)
+{
+// Local table is very outer table, create missing offsets.
+for (auto it = pLocalColOffset->begin(); it !=
pLocalColOffset->end(); ++it)
+{
+// Only exact offsets, do not use MakeColNoRef().
+if (maColOffset.find(*it) == maColOffset.end())
+maColOffset.insert(*it);
+}
+}
}
for ( size_t i = nFirstTableCell, nListSize = maList.size(); i <
nListSize; ++i )
{
[Libreoffice-bugs] [Bug 155760] New: Recent Documents disappears after updates
https://bugs.documentfoundation.org/show_bug.cgi?id=155760 Bug ID: 155760 Summary: Recent Documents disappears after updates Product: LibreOffice Version: 4.1 all versions Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tfrogg...@yahoo.com Description: First off, thank you very much for all of your work on this excellent software; I get a lot of good use out of it. The issue is as follows: Every time a new update is installed, the list of Recent Documents disappears. I find Recent Documents very useful, because I am working on numerous documents at any given time; because of this issue, I have refrained from installing new updates for quite a while. If this could be corrected that would be fantastic. Thank you very much. Steps to Reproduce: 1. Click on notification that new updates are available 2. Install update 3. Actual Results: When the update installs, the Recent Documents list has been cleared. Expected Results: Recent Documents should be left untouched, to make these documents easier to find. Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: no -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155742] FILESAVE: Table in fromwriterdocument.html looks totally damaged when opened in Internet Browsers (but ok in LibO)
https://bugs.documentfoundation.org/show_bug.cgi?id=155742 --- Comment #7 from Alexander Kurakin --- Rainer, thanks! (In reply to Rainer Bielefeld Retired from comment #6) > c) But I can't tell whether it is possible to code such a table in html4 >And so I don`t know whether this is a real bug. Why, exactly? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107326] [META] Writer style bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107326 Bug 107326 depends on bug 154933, which changed state. Bug 154933 Summary: Rename "Text body" to "Body text" https://bugs.documentfoundation.org/show_bug.cgi?id=154933 What|Removed |Added Status|VERIFIED|REOPENED Resolution|FIXED |--- -- 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 Olivier Hallot changed: What|Removed |Added Status|VERIFIED|REOPENED Resolution|FIXED |--- --- Comment #10 from Olivier Hallot --- More strings to fix in user interface: https://translations.documentfoundation.org/languages/pt_BR/libo_ui-master/search/?offset=1=+source%3A%22Text+Body%22+_by=-priority%2Cposition= -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: filter/source
filter/source/pdf/pdfdialog.cxx |1 +
1 file changed, 1 insertion(+)
New commits:
commit e4c611ddc731d6a2ca9c3de61a02d1d4b6eefa9b
Author: Caolán McNamara
AuthorDate: Fri Jun 9 12:51:22 2023 +0100
Commit: Caolán McNamara
CommitDate: Fri Jun 9 20:26:48 2023 +0200
pdf export dialog can crash if async mode used
dialogClosed can cause the owner of PDFDialog to drop it during the
callback
==4057599==ERROR: AddressSanitizer: heap-use-after-free on address
0x6130003cc890 at pc 0x7fecd4abe0f4 bp 0x7ffce7ef2d80 sp 0x7ffce7ef2d78
READ of size 8 at 0x6130003cc890 thread T0
#0 0x7fecd4abe0f3 in std::__shared_ptr::operator bool() const
/usr/bin/../lib/gcc/x86_64-redhat-linux/13/../../../../include/c++/13/bits/shared_ptr_base.h:1670:16
#1 0x7fecd4abe0f3 in
svt::OGenericUnoAsyncDialog::destroyAsyncDialog()
core/include/svtools/genericasyncunodialog.hxx:107:13
#2 0x7fecd4abd362 in
PDFDialog::runAsync(com::sun::star::uno::Reference
const&)::$_0::operator()(int) const core/filter/source/pdf/pdfdialog.cxx:95:9
0x6130003cc890 is located 272 bytes inside of 336-byte region
[0x6130003cc780,0x6130003cc8d0)
freed by thread T0 here:
#0 0x4b7cfa in __interceptor_free
(core/instdir/program/soffice.bin+0x4b7cfa) (BuildId:
e1b47bbe1dcc1e4ed692b09b49fe3da8d206f4b1)
#1 0x7fed09f540b2 in
com::sun::star::uno::Reference::~Reference()
core/include/com/sun/star/uno/Reference.hxx:114:22
#2 0x7fed09f540b2 in ModelData_Impl::~ModelData_Impl()
core/sfx2/source/doc/guisaveas.cxx:359:1
previously allocated by thread T0 here:
#0 0x4b7fa2 in malloc (core/instdir/program/soffice.bin+0x4b7fa2)
(BuildId: e1b47bbe1dcc1e4ed692b09b49fe3da8d206f4b1)
#1 0x7fecd4ab87cf in cppu::OWeakObject::operator new(unsigned long)
core/include/cppuhelper/weak.hxx:89:18
#2 0x7fecd4ab87cf in filter_PDFDialog_get_implementation
core/filter/source/pdf/pdfdialog.cxx:170:26
...
#9 0x7fed09f811a4 in
SfxStoringHelper::GUIStoreModel(com::sun::star::uno::Reference
const&, std::basic_string_view>,
com::sun::star::uno::Sequence&, bool,
SignatureState, bool) core/sfx2/source/doc/guisaveas.cxx:1561:29
Change-Id: I7ea28b9b4bb7c826f1c3c8ced7ea8217573f733b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152793
Tested-by: Jenkins
Reviewed-by: Caolán McNamara
diff --git a/filter/source/pdf/pdfdialog.cxx b/filter/source/pdf/pdfdialog.cxx
index c036fc747b2a..c7dd241c2049 100644
--- a/filter/source/pdf/pdfdialog.cxx
+++ b/filter/source/pdf/pdfdialog.cxx
@@ -79,6 +79,7 @@ void PDFDialog::executedDialog( sal_Int16 nExecutionResult )
void PDFDialog::runAsync(const css::uno::Reference<
css::ui::dialogs::XDialogClosedListener >& xListener)
{
SfxTabDialogController::runAsync(m_xAsyncDialog, [this,
xListener](sal_Int32 nResponse) {
+rtl::Reference xThis(this); // keep alive for scope,
dialogClosed can cause owner to drop this
executedAsyncDialog( m_xAsyncDialog, nResponse );
css::ui::dialogs::DialogClosedEvent aEvent;
aEvent.DialogResult = nResponse;
[Libreoffice-bugs] [Bug 155759] New: Blurry text in LibreOffice Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=155759 Bug ID: 155759 Summary: Blurry text in LibreOffice Writer Product: LibreOffice Version: 7.5.4.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: aaron.bus...@gmail.com Description: Same issue in the following URL: https://www.reddit.com/r/libreoffice/comments/f2wlsy/blurry_text_in_libreoffice_writer/ I am using Fedora 38 and the following version of LibreOffice: 7.5.4.2 (Flatpak) Steps to Reproduce: 1. Use Calibri font 2. Use any zoom less than 120% 3. All text is blurry/pixelated Actual Results: All text is blurry/pixelated Expected Results: Not produced blurry/pixelated text Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 12; OS: Linux 6.3; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-GB Flatpak Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120262] Fileopen DOC: floating tables piled on top of each other - probably due to in-line tables not wrapping around flies
https://bugs.documentfoundation.org/show_bug.cgi?id=120262 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||7822 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137822] LAYOUT DOCX: Text boxes with parallel wrap have inline tables slip underneath them (bad), while optimal wrap does not (workaround)
https://bugs.documentfoundation.org/show_bug.cgi?id=137822 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||0262 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120262] Fileopen DOC: floating tables piled on top of each other - probably due to in-line tables not wrapping around flies
https://bugs.documentfoundation.org/show_bug.cgi?id=120262 --- Comment #9 from Justin L --- This document looks to be designed pretty much identically to the minimal reproducer in bug 137822 comment 5. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/qa sw/source
sw/qa/extras/uiwriter/uiwriter2.cxx | 19 +++
sw/source/core/crsr/crsrsh.cxx | 10 ++
2 files changed, 29 insertions(+)
New commits:
commit ca9341cf60f3f9350662d30b61f6eadefca24667
Author: Michael Stahl
AuthorDate: Fri Jun 9 13:59:58 2023 +0200
Commit: Michael Stahl
CommitDate: Fri Jun 9 18:07:19 2023 +0200
cool#6580 sw: fix infinite loop when changing document language
If there's a footnote in the document, changing the document langauge
goes into an infinite loop in FindParentText(), because the selection
created by ExtendedSelectAll(true) is actually invalid, apparently
the intention is that only very limited functions may be called while it
is active.
Don't handle this invalid "very" extended selection like one created by
ExtendedSelectAll(false).
(regression from commit d81379db730a163c5ff75d4f3a3cddbd7b5eddda)
Change-Id: Icf1032715cf2e0a05bf485039c483440c08bb6bb
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152797
Tested-by: Jenkins
Reviewed-by: Michael Stahl
diff --git a/sw/qa/extras/uiwriter/uiwriter2.cxx
b/sw/qa/extras/uiwriter/uiwriter2.cxx
index a09d7b6fb780..6c9714367bf7 100644
--- a/sw/qa/extras/uiwriter/uiwriter2.cxx
+++ b/sw/qa/extras/uiwriter/uiwriter2.cxx
@@ -18,6 +18,10 @@
#include
#include
#include
+#include
+#include
+#include
+#include
#include
#include
#include
@@ -168,6 +172,21 @@ CPPUNIT_TEST_FIXTURE(SwUiWriterTest2, testTdf101534)
CPPUNIT_ASSERT_EQUAL(::tools::Long(0),
aSet.GetItem(RES_MARGIN_TEXTLEFT)->GetTextLeft());
}
+CPPUNIT_TEST_FIXTURE(SwUiWriterTest2, testExtendedSelectAllHang)
+{
+createSwDoc();
+SwDoc* const pDoc = getSwDoc();
+SwWrtShell* const pWrtShell = pDoc->GetDocShell()->GetWrtShell();
+
+pWrtShell->InsertFootnote("");
+pWrtShell->StartOfSection();
+SwView* pView = pDoc->GetDocShell()->GetView();
+SfxStringItem aLangString(SID_LANGUAGE_STATUS, "Default_Spanish
(Bolivia)");
+// this looped
+pView->GetViewFrame().GetDispatcher()->ExecuteList(SID_LANGUAGE_STATUS,
SfxCallMode::SYNCHRON,
+ { });
+}
+
CPPUNIT_TEST_FIXTURE(SwUiWriterTest2, testRedlineMoveInsertInDelete)
{
createSwDoc();
diff --git a/sw/source/core/crsr/crsrsh.cxx b/sw/source/core/crsr/crsrsh.cxx
index 325ff54d52cd..9fb43ff2d596 100644
--- a/sw/source/core/crsr/crsrsh.cxx
+++ b/sw/source/core/crsr/crsrsh.cxx
@@ -895,6 +895,16 @@ SwCursorShell::ExtendedSelectedAll() const
typename SwCursorShell::StartsWith SwCursorShell::StartsWith_()
{
SwShellCursor const*const pShellCursor = getShellCursor(false);
+// first, check if this is invalid; ExtendedSelectAll(true) may result in
+// a) an ordinary selection that is valid
+// b) a selection that is extended
+// c) a selection that is invalid and will cause FindParentText to loop
+SwNode const& rEndOfExtras(GetDoc()->GetNodes().GetEndOfExtras());
+if (pShellCursor->Start()->nNode.GetIndex() <= rEndOfExtras.GetIndex()
+&& rEndOfExtras.GetIndex() < pShellCursor->End()->nNode.GetIndex())
+{
+return StartsWith::None; // *very* extended, no ExtendedSelectedAll
handling!
+}
SwStartNode const*const pStartNode(FindParentText(*pShellCursor));
if (auto const ret = ::StartsWith(*pStartNode); ret != StartsWith::None)
{
[Libreoffice-commits] core.git: sw/qa
sw/qa/uitest/writer_tests/trackedChanges.py |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit 364c8676f773085031bf454b810280ecbaf12b6a
Author: Andrea Gelmini
AuthorDate: Fri Jun 9 13:23:20 2023 +0200
Commit: Julien Nabet
CommitDate: Fri Jun 9 18:00:44 2023 +0200
Fix typo in code
Change-Id: I98cd2b8c8a05f293dd85fbdd8828bc9e67aff2fd
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152786
Tested-by: Jenkins
Reviewed-by: Julien Nabet
diff --git a/sw/qa/uitest/writer_tests/trackedChanges.py
b/sw/qa/uitest/writer_tests/trackedChanges.py
index 7e780ef61730..79bcaf1d3c66 100644
--- a/sw/qa/uitest/writer_tests/trackedChanges.py
+++ b/sw/qa/uitest/writer_tests/trackedChanges.py
@@ -503,7 +503,7 @@ class trackedchanges(UITestCase):
# of the text "inserts": "Document text inserts
document"...
self.assertTrue(document.getText().getString().startswith('Document text
document text'))
-def test_tdf155342_tracked_table_colums(self):
+def test_tdf155342_tracked_table_columns(self):
with
self.ui_test.load_file(get_url_for_data_file("TC-table-del-add.docx")) as
document:
# accept all changes and insert new columns with change tracking
[Libreoffice-commits] core.git: include/LibreOfficeKit
include/LibreOfficeKit/LibreOfficeKitEnums.h |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 286e3d3fd10bdbec4954aab46eea198e9f0b9602 Author: Andrea Gelmini AuthorDate: Fri Jun 9 13:27:21 2023 +0200 Commit: Julien Nabet CommitDate: Fri Jun 9 18:00:05 2023 +0200 Fix typo Change-Id: Ica639513051c843bf8065f209427ba4054993463 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152791 Tested-by: Jenkins Reviewed-by: Julien Nabet diff --git a/include/LibreOfficeKit/LibreOfficeKitEnums.h b/include/LibreOfficeKit/LibreOfficeKitEnums.h index 13351b672d51..0325e62399a5 100644 --- a/include/LibreOfficeKit/LibreOfficeKitEnums.h +++ b/include/LibreOfficeKit/LibreOfficeKitEnums.h @@ -964,7 +964,7 @@ typedef enum /** * Informs that the document password has been successfully changed. - * The payload contains the the new password and the type. + * The payload contains the new password and the type. */ LOK_CALLBACK_DOCUMENT_PASSWORD_RESET = 66 }
[Libreoffice-commits] core.git: include/oox oox/source
include/oox/drawingml/color.hxx |3 ++
oox/source/drawingml/color.cxx | 24 +++
oox/source/drawingml/fillproperties.cxx | 16 +--
oox/source/drawingml/textcharacterproperties.cxx | 15 --
4 files changed, 30 insertions(+), 28 deletions(-)
New commits:
commit c1470e15bd0643be8d91aaf6a0d25c78867d0b3e
Author: Tomaž Vajngerl
AuthorDate: Fri Jun 9 23:34:24 2023 +0900
Commit: Tomaž Vajngerl
CommitDate: Fri Jun 9 17:59:48 2023 +0200
oox: remove code duplication and add getComplexColor to oox::Color
Change-Id: I9cfbc851d4f303a5a8c92183f01cb5b6545b7984
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152800
Tested-by: Jenkins
Reviewed-by: Tomaž Vajngerl
diff --git a/include/oox/drawingml/color.hxx b/include/oox/drawingml/color.hxx
index 75812c200c28..245e655d7c78 100644
--- a/include/oox/drawingml/color.hxx
+++ b/include/oox/drawingml/color.hxx
@@ -30,6 +30,7 @@
#include
#include
#include
+#include
namespace oox { class GraphicHelper; }
@@ -117,6 +118,8 @@ public:
/// Compares this color with rOther.
bool equals(const Color& rOther, const GraphicHelper& rGraphicHelper,
::Color nPhClr) const;
+model::ComplexColor getComplexColor() const;
+
private:
/** Internal helper for getColor(). */
voidsetResolvedRgb( ::Color nRgb ) const;
diff --git a/oox/source/drawingml/color.cxx b/oox/source/drawingml/color.cxx
index 805ca6c4faed..ad0b5ca7835e 100644
--- a/oox/source/drawingml/color.cxx
+++ b/oox/source/drawingml/color.cxx
@@ -571,6 +571,30 @@ sal_Int16 Color::getLumOff() const
return 0;
}
+model::ComplexColor Color::getComplexColor() const
+{
+model::ComplexColor aComplexColor;
+
aComplexColor.setSchemeColor(model::convertToThemeColorType(getSchemeColorIndex()));
+
+if (getTintOrShade() > 0)
+{
+aComplexColor.addTransformation({model::TransformationType::Tint,
getTintOrShade()});
+}
+else if (getTintOrShade() < 0)
+{
+sal_Int16 nShade = o3tl::narrowing(-getTintOrShade());
+aComplexColor.addTransformation({model::TransformationType::Shade,
nShade});
+}
+
+if (getLumMod() != 1)
+aComplexColor.addTransformation({model::TransformationType::LumMod,
getLumMod()});
+
+if (getLumOff() != 0)
+aComplexColor.addTransformation({model::TransformationType::LumOff,
getLumOff()});
+
+return aComplexColor;
+}
+
::Color Color::getColor( const GraphicHelper& rGraphicHelper, ::Color nPhClr )
const
{
const sal_Int32 nTempC1 = mnC1;
diff --git a/oox/source/drawingml/fillproperties.cxx
b/oox/source/drawingml/fillproperties.cxx
index 705f2dc3b55a..7e2f5185b7f6 100644
--- a/oox/source/drawingml/fillproperties.cxx
+++ b/oox/source/drawingml/fillproperties.cxx
@@ -431,24 +431,12 @@ void FillProperties::pushToPropMap(ShapePropertyMap&
rPropMap, const GraphicHelp
if (aFillColor == nPhClr)
{
aComplexColor.setSchemeColor(model::convertToThemeColorType(nPhClrTheme));
-rPropMap.setProperty(PROP_FillComplexColor,
model::color::createXComplexColor(aComplexColor));
}
else
{
-
aComplexColor.setSchemeColor(model::convertToThemeColorType(maFillColor.getSchemeColorIndex()));
-if (maFillColor.getLumMod() != 1)
-
aComplexColor.addTransformation({model::TransformationType::LumMod,
maFillColor.getLumMod()});
-if (maFillColor.getLumOff() != 0)
-
aComplexColor.addTransformation({model::TransformationType::LumOff,
maFillColor.getLumOff()});
-if (maFillColor.getTintOrShade() > 0)
-
aComplexColor.addTransformation({model::TransformationType::Tint,
maFillColor.getTintOrShade()});
-if (maFillColor.getTintOrShade() < 0)
-{
-sal_Int16 nShade =
o3tl::narrowing(-maFillColor.getTintOrShade());
-
aComplexColor.addTransformation({model::TransformationType::Shade, nShade});
-}
-rPropMap.setProperty(PROP_FillComplexColor,
model::color::createXComplexColor(aComplexColor));
+aComplexColor = maFillColor.getComplexColor();
}
+rPropMap.setProperty(PROP_FillComplexColor,
model::color::createXComplexColor(aComplexColor));
eFillStyle = FillStyle_SOLID;
}
diff --git a/oox/source/drawingml/textcharacterproperties.cxx
b/oox/source/drawingml/textcharacterproperties.cxx
index 7d3dda284680..0e1e2830a67f 100644
--- a/oox/source/drawingml/textcharacterproperties.cxx
+++ b/oox/source/drawingml/textcharacterproperties.cxx
@@ -136,20 +136,7 @@ void TextCharacterProperties::pushToPropMap( PropertyMap&
[Libreoffice-commits] core.git: include/LibreOfficeKit
include/LibreOfficeKit/LibreOfficeKitEnums.h |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit bcd076c22c5af0993641e719ea01559548acbc38 Author: Andrea Gelmini AuthorDate: Fri Jun 9 13:26:05 2023 +0200 Commit: Julien Nabet CommitDate: Fri Jun 9 17:59:31 2023 +0200 Fix typo Change-Id: I4b8e65b686942a20df2d0133ff1208737e272e42 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152790 Tested-by: Julien Nabet Reviewed-by: Julien Nabet diff --git a/include/LibreOfficeKit/LibreOfficeKitEnums.h b/include/LibreOfficeKit/LibreOfficeKitEnums.h index d2a03c8ce9b6..13351b672d51 100644 --- a/include/LibreOfficeKit/LibreOfficeKitEnums.h +++ b/include/LibreOfficeKit/LibreOfficeKitEnums.h @@ -963,7 +963,7 @@ typedef enum LOK_CALLBACK_COLOR_PALETTES = 65, /** - * Informs that the document password has been succesfully changed. + * Informs that the document password has been successfully changed. * The payload contains the the new password and the type. */ LOK_CALLBACK_DOCUMENT_PASSWORD_RESET = 66
[Libreoffice-commits] core.git: drawinglayer/source
drawinglayer/source/processor2d/vclmetafileprocessor2d.cxx |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit fd1bd06509f4544cc18bdf2319c5456b33d08e52 Author: Andrea Gelmini AuthorDate: Fri Jun 9 13:24:34 2023 +0200 Commit: Julien Nabet CommitDate: Fri Jun 9 17:58:30 2023 +0200 Fix typo Change-Id: I4f3f148956c0502a3582a232cbd3cad287c0eaa1 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152787 Tested-by: Jenkins Reviewed-by: Julien Nabet diff --git a/drawinglayer/source/processor2d/vclmetafileprocessor2d.cxx b/drawinglayer/source/processor2d/vclmetafileprocessor2d.cxx index feb30d33e1ed..1b411d16f443 100644 --- a/drawinglayer/source/processor2d/vclmetafileprocessor2d.cxx +++ b/drawinglayer/source/processor2d/vclmetafileprocessor2d.cxx @@ -2387,7 +2387,7 @@ void VclMetafileProcessor2D::processTransparencePrimitive2D( // places using it would need adaption, ...), but combined with knowing that nearly // all usages ignore or render it locally anyways makes that a non-option. -// tdf#155479 Yepp, as already mentionmed above we need to add +// tdf#155479 Yepp, as already mentioned above we need to add // some MCGR infos in case of SVG export, prepare that here if (nullptr != mpOutputDevice->GetConnectMetaFile() && mpOutputDevice->GetConnectMetaFile()->getSVG())
[Libreoffice-commits] core.git: basegfx/source
basegfx/source/tools/bgradient.cxx |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit cdc015ffd4b2460a9235db72a5411c421ab0e2d4
Author: Andrea Gelmini
AuthorDate: Fri Jun 9 13:25:36 2023 +0200
Commit: Julien Nabet
CommitDate: Fri Jun 9 17:57:39 2023 +0200
Fix typo
Change-Id: Iaebe55927771985a6b574b2cb9410b0eb75441e1
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152789
Tested-by: Jenkins
Reviewed-by: Julien Nabet
diff --git a/basegfx/source/tools/bgradient.cxx
b/basegfx/source/tools/bgradient.cxx
index 61a58b5e3cdb..d46530074787 100644
--- a/basegfx/source/tools/bgradient.cxx
+++ b/basegfx/source/tools/bgradient.cxx
@@ -749,7 +749,7 @@ void BColorStops::doApplySteps(sal_uInt16 nStepCount)
if (!basegfx::fTools::equalZero(fDelta))
{
-// create in-between steps, always two at the same positon to
+// create in-between steps, always two at the same position to
// define a 'hard' color stop. Get start/end color for the segment
const basegfx::BColor& rStartColor(aColorL->getStopColor());
const basegfx::BColor& rEndColor(aColorR->getStopColor());
[Libreoffice-commits] core.git: basegfx/source
basegfx/source/tools/bgradient.cxx |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit e1dcf9464e56c0eee9f662f82928b3f99ba78217
Author: Andrea Gelmini
AuthorDate: Fri Jun 9 13:25:06 2023 +0200
Commit: Julien Nabet
CommitDate: Fri Jun 9 17:57:06 2023 +0200
Fix typo
Change-Id: Ib02cc0e9aaf286d8c39523ea352cfeec17a6336f
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152788
Tested-by: Jenkins
Reviewed-by: Julien Nabet
diff --git a/basegfx/source/tools/bgradient.cxx
b/basegfx/source/tools/bgradient.cxx
index c96cd0b673cb..61a58b5e3cdb 100644
--- a/basegfx/source/tools/bgradient.cxx
+++ b/basegfx/source/tools/bgradient.cxx
@@ -681,7 +681,7 @@ bool BColorStops::isSymmetrical() const
void BColorStops::doApplyAxial()
{
-// preapare new ColorStops
+// prepare new ColorStops
basegfx::BColorStops aNewColorStops;
// add gradient stops in reverse order, scaled to [0.0 .. 0.5]
[Libreoffice-commits] core.git: svx/source
svx/source/tbxctrls/StylesPreviewWindow.cxx | 41
1 file changed, 36 insertions(+), 5 deletions(-)
New commits:
commit aae8841e2057d522b3cae7b5792ae75cc8d6b5b4
Author: Caolán McNamara
AuthorDate: Wed Jun 7 20:43:12 2023 +0100
Commit: Caolán McNamara
CommitDate: Fri Jun 9 17:52:23 2023 +0200
Related: cool#6511 hold json preview cache longer
due to oddities related to tdf155720 the notebookbar the cache is hooked
to can be torn down and replaced if the 1st session is interacted with
while multiple other users join. So count goes to 0 just at the wrong
time to trigger throwing away the cache and forcing regeneration.
An Idle doesn't suffice here.
https: //github.com/CollaboraOnline/online/issues/6511
Change-Id: I148c99115fc497e34bf8920b6f59adc47605b8a1
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152720
Tested-by: Caolán McNamara
Reviewed-by: Caolán McNamara
diff --git a/svx/source/tbxctrls/StylesPreviewWindow.cxx
b/svx/source/tbxctrls/StylesPreviewWindow.cxx
index 53a8f14511a9..c5215cba4a6d 100644
--- a/svx/source/tbxctrls/StylesPreviewWindow.cxx
+++ b/svx/source/tbxctrls/StylesPreviewWindow.cxx
@@ -68,35 +68,66 @@ namespace
{
class StylePreviewCache
{
+private:
+class JsonStylePreviewCacheClear final : public Timer
+{
+public:
+JsonStylePreviewCacheClear()
+: Timer("Json Style Preview Cache clear callback")
+{
+// a generous 30 secs
+SetTimeout(3);
+SetStatic();
+}
+virtual void Invoke() override {
StylePreviewCache::gJsonStylePreviewCache.clear(); }
+};
+
static std::map> gStylePreviewCache;
static std::map gJsonStylePreviewCache;
static int gStylePreviewCacheClients;
+static JsonStylePreviewCacheClear gJsonIdleClear;
public:
static std::map>& Get() { return
gStylePreviewCache; }
static std::map& GetJson() { return
gJsonStylePreviewCache; }
-static void ClearCache()
+static void ClearCache(bool bHard)
{
for (auto& aPreview : gStylePreviewCache)
aPreview.second.disposeAndClear();
gStylePreviewCache.clear();
-gJsonStylePreviewCache.clear();
+if (bHard)
+{
+StylePreviewCache::gJsonStylePreviewCache.clear();
+gJsonIdleClear.Stop();
+}
+else
+{
+// tdf#155720 don't immediately clear the json representation
+gJsonIdleClear.Start();
+}
+}
+
+static void RegisterClient()
+{
+if (!gStylePreviewCacheClients)
+gJsonIdleClear.Stop();
+gStylePreviewCacheClients++;
}
-static void RegisterClient() { gStylePreviewCacheClients++; }
static void UnregisterClient()
{
gStylePreviewCacheClients--;
if (!gStylePreviewCacheClients)
-ClearCache();
+ClearCache(false);
}
};
std::map>
StylePreviewCache::gStylePreviewCache;
std::map StylePreviewCache::gJsonStylePreviewCache;
int StylePreviewCache::gStylePreviewCacheClients;
+StylePreviewCache::JsonStylePreviewCacheClear
StylePreviewCache::gJsonIdleClear;
}
StyleStatusListener::StyleStatusListener(
@@ -143,7 +174,7 @@ StylePoolChangeListener::~StylePoolChangeListener()
void StylePoolChangeListener::Notify(SfxBroadcaster& /*rBC*/, const SfxHint&
rHint)
{
if (rHint.GetId() == SfxHintId::StyleSheetModified)
-StylePreviewCache::ClearCache();
+StylePreviewCache::ClearCache(true);
m_pPreviewControl->RequestStylesListUpdate();
}
[Libreoffice-bugs] [Bug 155757] Support Color Filter in "Standard Filter" dialog enhancement - missing background colors choice in filter field.
https://bugs.documentfoundation.org/show_bug.cgi?id=155757 ady changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #2 from ady --- In Filter by Color, I see the name of the colors, not the content; but comment 0 is not clear to me. Perhaps attaching a screenshot of what you see as incorrect would help? Additionally, attachment 187811 from comment 1 mentions the following (which is not the same as comment 0): " test dark orange 4 -cell 11 background color color not present in color selector if cell is empty background color items not always present in standard filter " Such behavior depends on how you select the autofilter area: * If you just click on cell A1 and then Autofilter, the autofilter goes as far as the first empty cell in the column. * If, instead, you first select the relevant area (A1:A18, or the entire column A:A), then all the values and all the respective colors will be included in the autofilter list. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 94774] [META] DOCX (OOXML) object fill bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=94774 Bug 94774 depends on bug 128648, which changed state. Bug 128648 Summary: FILESAVE DOCX Linear gradient direction mirrored on saving https://bugs.documentfoundation.org/show_bug.cgi?id=128648 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104442] [META] OOXML shape (DrawingML and VML) related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=104442 Bug 104442 depends on bug 128648, which changed state. Bug 128648 Summary: FILESAVE DOCX Linear gradient direction mirrored on saving https://bugs.documentfoundation.org/show_bug.cgi?id=128648 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128648] FILESAVE DOCX Linear gradient direction mirrored on saving
https://bugs.documentfoundation.org/show_bug.cgi?id=128648 Buovjaga changed: What|Removed |Added CC||ilmari.lauhakangas@libreoff ||ice.org Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #15 from Buovjaga --- Let's close per the previous comment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 95662] XHTML-Export: Export to html produces wrong decimalseparator together with bullets
https://bugs.documentfoundation.org/show_bug.cgi?id=95662 --- Comment #34 from Svante Schubert --- I would appreciate if someone could enhance the test document having multiple list levels and all possible features with different numbers for testing: https://docs.oasis-open.org/office/OpenDocument/v1.3/os/part3-schema/OpenDocument-v1.3-os-part3-schema.html#property-text_list-level-position-and-space-mode Created an external issue that might be mapped later to bugzilla: https://github.com/oasis-tcs/odf-tc/pull/50 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-23.05' - vcl/source
vcl/source/app/svdata.cxx |8 ++--
vcl/source/app/svmain.cxx |8 +---
2 files changed, 7 insertions(+), 9 deletions(-)
New commits:
commit 6fb7330f35424f3b9f04a6dfb99b1754e2dcfa0f
Author: Michael Meeks
AuthorDate: Fri Jun 9 12:17:36 2023 +0100
Commit: Caolán McNamara
CommitDate: Fri Jun 9 16:54:04 2023 +0200
trimMemory - fix crash modifying structure during clear.
Re-use existing code from shutdown, to avoid ~Bitmap mutating
maScaleCache while we're iterating it inside clear.
Change-Id: I021d9075cf5c449702af091c2c8a4de64887f2ed
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152785
Reviewed-by: Miklos Vajna
Tested-by: Michael Meeks
Tested-by: Caolán McNamara
Reviewed-by: Caolán McNamara
diff --git a/vcl/source/app/svdata.cxx b/vcl/source/app/svdata.cxx
index febed41cb98c..cb7778fcfd40 100644
--- a/vcl/source/app/svdata.cxx
+++ b/vcl/source/app/svdata.cxx
@@ -419,9 +419,13 @@ ImplSVData::ImplSVData()
void ImplSVData::dropCaches()
{
-maGDIData.maScaleCache.clear();
-maGDIData.maThemeImageCache.clear();
+// we are iterating over a map and doing erase while inside a loop which
is doing erase
+// hence we can't use clear() here
+maGDIData.maScaleCache.remove_if([](const
lru_scale_cache::key_value_pair_t&)
+{ return true; });
+
maGDIData.maThemeDrawCommandsCache.clear();
+maGDIData.maThemeImageCache.clear();
}
void ImplSVData::dumpState(rtl::OStringBuffer )
diff --git a/vcl/source/app/svmain.cxx b/vcl/source/app/svmain.cxx
index 7c5505f364cb..2838cfc3a63c 100644
--- a/vcl/source/app/svmain.cxx
+++ b/vcl/source/app/svmain.cxx
@@ -588,13 +588,7 @@ void DeInitVCL()
pSVData->maGDIData.mxScreenFontList.reset();
pSVData->maGDIData.mxScreenFontCache.reset();
-// we are iterating over a map and doing erase while inside a loop which
is doing erase
-// hence we can't use clear() here
-pSVData->maGDIData.maScaleCache.remove_if([](const
lru_scale_cache::key_value_pair_t&)
-{ return true; });
-
-pSVData->maGDIData.maThemeDrawCommandsCache.clear();
-pSVData->maGDIData.maThemeImageCache.clear();
+pSVData->dropCaches();
// Deinit Sal
if (pSVData->mpDefInst)
[Libreoffice-commits] core.git: Branch 'libreoffice-7-6' - filter/source sc/CppunitTest_sc_html_export_test.mk sc/qa sw/qa
filter/source/xslt/odf2xhtml/export/common/table/table_rows.xsl |5 filter/source/xslt/odf2xhtml/export/common/table_of_content.xsl | 25 filter/source/xslt/odf2xhtml/export/xhtml/body.xsl | 345 +- filter/source/xslt/odf2xhtml/export/xhtml/header.xsl|7 filter/source/xslt/odf2xhtml/export/xhtml/table.xsl |6 sc/CppunitTest_sc_html_export_test.mk |5 sc/qa/extras/htmlexporttest.cxx | 18 sc/qa/extras/testdocuments/default-styles.ods |binary sw/qa/extras/htmlexport/xhtmlexport.cxx | 23 9 files changed, 394 insertions(+), 40 deletions(-) New commits: commit ea5a96e10f93a285279da4ade8104f85c1a95dfc Author: Svante Schubert AuthorDate: Wed May 17 17:44:39 2023 +0200 Commit: Michael Stahl CommitDate: Fri Jun 9 16:53:46 2023 +0200 tdf#155244 filter: XHTML export: Making ODF style IDs unique for ... ... HTML/CSS by adding a prefix (the @style:family with '-' as glue character) to their style name. Disabled debug output for style:family-name in XSL add text:a to text family ... and add a unit test. Change-Id: Ie846f5ea2a872872f38036aff59d29c8f530ed32 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152749 Tested-by: Jenkins Reviewed-by: Michael Stahl (cherry picked from commit 97c07f2ceca336f9659538fc63c600c0a1d51dfe) Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152812 diff --git a/filter/source/xslt/odf2xhtml/export/common/table/table_rows.xsl b/filter/source/xslt/odf2xhtml/export/common/table/table_rows.xsl index 2d6cd7285037..60b47be753ca 100644 --- a/filter/source/xslt/odf2xhtml/export/common/table/table_rows.xsl +++ b/filter/source/xslt/odf2xhtml/export/common/table/table_rows.xsl @@ -196,7 +196,10 @@ - + + + + diff --git a/filter/source/xslt/odf2xhtml/export/common/table_of_content.xsl b/filter/source/xslt/odf2xhtml/export/common/table_of_content.xsl index 7a04bee074a8..0f36b36486de 100644 --- a/filter/source/xslt/odf2xhtml/export/common/table_of_content.xsl +++ b/filter/source/xslt/odf2xhtml/export/common/table_of_content.xsl @@ -93,7 +93,10 @@ - + + + + @@ -317,7 +320,10 @@ Scenarios unmatched: - + + + + @@ -341,7 +347,10 @@ Scenarios unmatched: - + + + + @@ -358,7 +367,10 @@ Scenarios unmatched: - + + + + @@ -382,7 +394,10 @@ Scenarios unmatched: - + + + + diff --git a/filter/source/xslt/odf2xhtml/export/xhtml/body.xsl b/filter/source/xslt/odf2xhtml/export/xhtml/body.xsl index 9706c1df0615..7b3c7e4d3b17 100644 --- a/filter/source/xslt/odf2xhtml/export/xhtml/body.xsl +++ b/filter/source/xslt/odf2xhtml/export/xhtml/body.xsl @@ -19,7 +19,7 @@ -http://www.w3.org/1999/XSL/Transform; xmlns:chart="urn:oasis:names:tc:opendocument:xmlns:chart:1.0"
[Libreoffice-bugs] [Bug 108152] Diacritic positioning at beginning of paragraph not working with Graphite font
https://bugs.documentfoundation.org/show_bug.cgi?id=108152 --- Comment #16 from Buovjaga --- (In reply to Sophie Sipasseuth from comment #15) > Hi Ilmari, > > Thanks for your comment, I checked the installation of the GodaGr font on my > computer and the screenshot "no repro bug graphite font". > I don't understand where is my mistake. > Could you explain to me where is it, please? > And I could better manage the installation of a font in the future. In your screenshot, the font name is shown in italics. This means the font is not available and has been substituted. If the installation was ok, the only reason I can think of is that you had LibreOffice running and did not close and reopen it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155452] When pasting image from Firefox in Calc, pasted image is not visible (only paste frame)
https://bugs.documentfoundation.org/show_bug.cgi?id=155452 --- Comment #11 from Regis Perdreau --- tested in Version: 7.6.0.0.beta1+ (X86_64) / LibreOffice Community Build ID: a0ce0d4418ad92dd0e3a70cf698c549b544d6084 CPU threads: 6; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: fr-FR (fr_FR); UI: fr-FR Calc: CL threaded the paste action in paste special with bmp format is working now.( we have not the empty paste frame described previously) But not the direct ctrl-v paste action. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: vcl/source
vcl/source/app/svdata.cxx |8 ++--
vcl/source/app/svmain.cxx |8 +---
2 files changed, 7 insertions(+), 9 deletions(-)
New commits:
commit 6fc48879f8347a53a5ef1bf801fab831be3310f2
Author: Michael Meeks
AuthorDate: Fri Jun 9 12:17:36 2023 +0100
Commit: Michael Meeks
CommitDate: Fri Jun 9 16:33:40 2023 +0200
trimMemory - fix crash modifying structure during clear.
Re-use existing code from shutdown, to avoid ~Bitmap mutating
maScaleCache while we're iterating it inside clear.
Change-Id: I021d9075cf5c449702af091c2c8a4de64887f2ed
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152769
Tested-by: Jenkins
Reviewed-by: Michael Meeks
diff --git a/vcl/source/app/svdata.cxx b/vcl/source/app/svdata.cxx
index ac1fd6b2c623..9840eec37fc6 100644
--- a/vcl/source/app/svdata.cxx
+++ b/vcl/source/app/svdata.cxx
@@ -420,9 +420,13 @@ ImplSVData::ImplSVData()
void ImplSVData::dropCaches()
{
-maGDIData.maScaleCache.clear();
-maGDIData.maThemeImageCache.clear();
+// we are iterating over a map and doing erase while inside a loop which
is doing erase
+// hence we can't use clear() here
+maGDIData.maScaleCache.remove_if([](const
lru_scale_cache::key_value_pair_t&)
+{ return true; });
+
maGDIData.maThemeDrawCommandsCache.clear();
+maGDIData.maThemeImageCache.clear();
}
void ImplSVData::dumpState(rtl::OStringBuffer )
diff --git a/vcl/source/app/svmain.cxx b/vcl/source/app/svmain.cxx
index 5bccf3e3a0c4..b574873744ee 100644
--- a/vcl/source/app/svmain.cxx
+++ b/vcl/source/app/svmain.cxx
@@ -589,13 +589,7 @@ void DeInitVCL()
pSVData->maGDIData.mxScreenFontList.reset();
pSVData->maGDIData.mxScreenFontCache.reset();
-// we are iterating over a map and doing erase while inside a loop which
is doing erase
-// hence we can't use clear() here
-pSVData->maGDIData.maScaleCache.remove_if([](const
lru_scale_cache::key_value_pair_t&)
-{ return true; });
-
-pSVData->maGDIData.maThemeDrawCommandsCache.clear();
-pSVData->maGDIData.maThemeImageCache.clear();
+pSVData->dropCaches();
comphelper::AccessibleEventNotifier::shutdown();
[Libreoffice-bugs] [Bug 155736] Fileopen DOCX:Page numbers (from field of course, but inside a nested block SDT) are missing in the footer for a particular file
https://bugs.documentfoundation.org/show_bug.cgi?id=155736 --- Comment #9 from Justin L --- (In reply to Justin L from comment #8) > IIUC, this is a lot of hacky stuff, so it all could be dreadfully wrong. I > believe there was a lot of code changes/research into this area recently See bug 154478 which replaces a similar fix made for bug 154481. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155755] FUNCTION: suggestion for MULTIPLY.IF()
https://bugs.documentfoundation.org/show_bug.cgi?id=155755 --- Comment #3 from Michel COLLET --- @ Eike Rathke waouh, so great! I don't have this description in my french documentation. Thanks a lot Eike -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155755] FUNCTION: suggestion for MULTIPLY.IF()
https://bugs.documentfoundation.org/show_bug.cgi?id=155755 --- Comment #2 from Eike Rathke --- That wouldn't deliver a single return value though like SUMIF() (note it's not SUM.IF() that was probably because in French it's SOMME.SI()) but an array/matrix and that can already be accomplished by entering =range1*range2*condition as array formula, i.e. closing it with Shift+Ctrl+Enter instead of Enter. Example: =A1:A5*B1:B5*(C1:C5<>23) multiplies cells of A1:B5 with cells of B1:B5 if the corresponding value in C1:C5 does not equal 23; returns an array of 5 values, 0 if condition is not met. If in comment 0 you meant to multiply all values of a range for a condition, that can be accomplished similar using =PRODUCT(IF(C1:C5<>23;A1:A5;"")) as array formula (French PRODUIT()). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155758] New: FUNCTION: suggestion for SUM.IF()
https://bugs.documentfoundation.org/show_bug.cgi?id=155758 Bug ID: 155758 Summary: FUNCTION: suggestion for SUM.IF() Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mco_documentfoundation.org_UnimailQeWEbOBj39z8Xb@dclic .fr Created attachment 187812 --> https://bugs.documentfoundation.org/attachment.cgi?id=187812=edit example for the suggestion for SUM.IF() I suggest accepting functions in the "criteria" parameter. Examples: > SUM.IF(E6:M6;AND(>0;<100);E7:M7) > SUM.IF(E6:M6;OR(AND(>0;<100);AND(>200;<300));E7:M7) A detailed example is joined. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 76022] DOC/DOCX import: Tables don't wrap around floating shapes (also wrong in old versions of MSO, but "correct" in MSO2013)
https://bugs.documentfoundation.org/show_bug.cgi?id=76022 Justin L changed: What|Removed |Added Blocks||155040 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=155040 [Bug 155040] FILEOPEN RTF Floating table is overlapped by subsequent non-floating ones -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155040] FILEOPEN RTF Floating table is overlapped by subsequent non-floating ones
https://bugs.documentfoundation.org/show_bug.cgi?id=155040 Justin L changed: What|Removed |Added Depends on||76022 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=76022 [Bug 76022] DOC/DOCX import: Tables don't wrap around floating shapes (also wrong in old versions of MSO, but "correct" in MSO2013) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155045] [META] RTF Floating table related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=155045 Justin L changed: What|Removed |Added Depends on||126449 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=126449 [Bug 126449] Tables in DOC document are overlapping (one floating multipage table-in-fr-table) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 126449] Tables in DOC document are overlapping (one floating multipage table-in-fr-table)
https://bugs.documentfoundation.org/show_bug.cgi?id=126449 Justin L changed: What|Removed |Added Summary|Tables in DOC document are |Tables in DOC document are |overlapping (one floating |overlapping (one floating |multipage table-in-table) |multipage ||table-in-fr-table) Blocks||155045 --- Comment #5 from Justin L --- repro 24.2 (very early in development) Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=155045 [Bug 155045] [META] RTF Floating table related issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155045] [META] RTF Floating table related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=155045 Justin L changed: What|Removed |Added Depends on||120262 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=120262 [Bug 120262] Fileopen DOC: floating tables piled on top of each other - probably due to in-line tables not wrapping around flies -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 76022] DOC/DOCX import: Tables don't wrap around floating shapes (also wrong in old versions of MSO, but "correct" in MSO2013)
https://bugs.documentfoundation.org/show_bug.cgi?id=76022 Justin L changed: What|Removed |Added Blocks||120262 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=120262 [Bug 120262] Fileopen DOC: floating tables piled on top of each other - probably due to in-line tables not wrapping around flies -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120262] Fileopen DOC: floating tables piled on top of each other - probably due to in-line tables not wrapping around flies
https://bugs.documentfoundation.org/show_bug.cgi?id=120262 Justin L changed: What|Removed |Added Depends on||76022 Blocks||155045 Summary|Fileopen DOC: tables|Fileopen DOC: floating |imported with reduced width |tables piled on top of each |if too close to the|other - probably due to |floating rectangle |in-line tables not wrapping ||around flies --- Comment #8 from Justin L --- I assume at this point this is just a duplicate of bug 76022 - marking it as a dependency. The problem of "first table shrunk in width to parallel wrapped around fly" was solved in 7.6. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=76022 [Bug 76022] DOC/DOCX import: Tables don't wrap around floating shapes (also wrong in old versions of MSO, but "correct" in MSO2013) https://bugs.documentfoundation.org/show_bug.cgi?id=155045 [Bug 155045] [META] RTF Floating table related issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/qa sw/source
sw/qa/extras/uiwriter/uiwriter5.cxx | 33 ++
sw/source/core/doc/DocumentRedlineManager.cxx |3 ++
2 files changed, 36 insertions(+)
New commits:
commit 9486ead7bbd5bd2460f5c75540dfeb731838e655
Author: László Németh
AuthorDate: Fri Jun 9 12:22:17 2023 +0200
Commit: László Németh
CommitDate: Fri Jun 9 15:45:56 2023 +0200
tdf#155747 sw tracked table column: fix crash at table selection
Selecting tracked columns and accepting their deletion resulted
crashing because of the outdated table cursor in IsCursorInTable()
call of UpdateTableStyleFormatting(). Remove table cursor before
calling DeleteCol().
Regression from commit d1004cdd6a445ae73673b0ca360ae034b0ec09f2
"tdf#150673 sw offapi: add change tracking of table column deletion".
Change-Id: I47f4db11bd7ce4ad851c0658eec3e12ce4fdf4a7
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152792
Tested-by: Jenkins
Reviewed-by: László Németh
diff --git a/sw/qa/extras/uiwriter/uiwriter5.cxx
b/sw/qa/extras/uiwriter/uiwriter5.cxx
index dc2506881c19..88868f8086c2 100644
--- a/sw/qa/extras/uiwriter/uiwriter5.cxx
+++ b/sw/qa/extras/uiwriter/uiwriter5.cxx
@@ -2556,6 +2556,39 @@ CPPUNIT_TEST_FIXTURE(SwUiWriterTest5,
testRedlineTableColumnDeletion)
assertXPath(pXmlDoc, "//page[1]//body/tab/row/cell", 1);
}
+CPPUNIT_TEST_FIXTURE(SwUiWriterTest5, testTdf155747)
+{
+// load a table, and delete the first column with enabled change tracking:
+// now the column is not deleted silently, but keeps the deleted cell
content,
+// and only accepting it will result the deletion of the table column.
+createSwDoc("tdf118311.fodt");
+SwDoc* pDoc = getSwDoc();
+
+// turn on red-lining and show changes
+pDoc->getIDocumentRedlineAccess().SetRedlineFlags(RedlineFlags::On |
RedlineFlags::ShowDelete
+ |
RedlineFlags::ShowInsert);
+CPPUNIT_ASSERT_MESSAGE("redlining should be on",
+ pDoc->getIDocumentRedlineAccess().IsRedlineOn());
+CPPUNIT_ASSERT_MESSAGE(
+"redlines should be visible",
+
IDocumentRedlineAccess::IsShowChanges(pDoc->getIDocumentRedlineAccess().GetRedlineFlags()));
+
+// delete table column with enabled change tracking
+// (HasTextChangesOnly property of the cell will be false)
+dispatchCommand(mxComponent, ".uno:DeleteColumns", {});
+
+// select table
+dispatchCommand(mxComponent, ".uno:SelectTable", {});
+
+// Without the fix in place, this test would have crashed here
+dispatchCommand(mxComponent, ".uno:AcceptTrackedChange", {});
+
+// check removed column
+xmlDocUniquePtr pXmlDoc = parseLayoutDump();
+assertXPath(pXmlDoc, "//page[1]//body/tab");
+assertXPath(pXmlDoc, "//page[1]//body/tab/row/cell", 1);
+}
+
CPPUNIT_TEST_FIXTURE(SwUiWriterTest5,
testTdf150673_RedlineTableColumnDeletionWithExport)
{
// load a table, and delete the first column with enabled change tracking:
diff --git a/sw/source/core/doc/DocumentRedlineManager.cxx
b/sw/source/core/doc/DocumentRedlineManager.cxx
index ac0bfe547e90..d9148ce723f3 100644
--- a/sw/source/core/doc/DocumentRedlineManager.cxx
+++ b/sw/source/core/doc/DocumentRedlineManager.cxx
@@ -22,6 +22,7 @@
#include
#include
#include
+#include
#include
#include
#include
@@ -467,6 +468,8 @@ namespace
SwCursor aCursor( *pPos, nullptr );
if ( pBox->IsEmpty() )
{
+// tdf#155747 remove table cursor
+pPos->GetDoc().GetDocShell()->GetWrtShell()->EnterStdMode();
// TODO check the other cells of the column
// before removing the column
pPos->GetDoc().DeleteCol( aCursor );
[Libreoffice-commits] core.git: sc/inc sc/source
sc/inc/column.hxx |6 ++
sc/source/core/data/table1.cxx | 12 +---
sc/source/core/data/table2.cxx |3 +++
3 files changed, 14 insertions(+), 7 deletions(-)
New commits:
commit dd8e061406fac581d399da088c7f0187278035dc
Author: Czeber László Ádám
AuthorDate: Thu Jun 8 14:55:34 2023 +0200
Commit: László Németh
CommitDate: Fri Jun 9 15:41:38 2023 +0200
tdf#153437 sc: fix broken formatting without performance regression
Follow-up to commit 7be7e1ff95af485a9cb00748800d3d084f96387c
"tdf#153437 sc: fix broken formatting at Undo of row/column insertion"
by replacing that with a better version without performance
regression. This keeps the original performance fix of
commit 2e86718626a07e1656661df3ad69a64848bf4614
"don't allocate unnecessary columns when inserting a row"
related to the support of 16k columns.
The previous fix used extra memory to fix the broken formatting
of the cells. I have now solved the error in tdf#153437 without
taking extra memory. It doesn't change the reserved cells, it just
deletes a row from the default attribute of the cells when deleting
rows, so they don't slip. When deleting a column, the last column
in the still reserved area loses its formatting. I copied the default value
back here, as the other columns have this value.
Change-Id: I35da1cb79ff4e3493e91d29766cc2b81412080eb
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152742
Tested-by: László Németh
Reviewed-by: László Németh
diff --git a/sc/inc/column.hxx b/sc/inc/column.hxx
index 5c42f02794ab..4b64537e1705 100644
--- a/sc/inc/column.hxx
+++ b/sc/inc/column.hxx
@@ -172,6 +172,7 @@ public:
boolTestInsertRow( SCSIZE nSize ) const;
voidInsertRow( SCROW nStartRow, SCSIZE nSize );
+voidDeleteRow( SCROW nStartRow, SCSIZE nSize );
};
// Use protected inheritance to prevent publishing some internal ScColumnData
@@ -1057,4 +1058,9 @@ inline void ScColumnData::InsertRow( SCROW nStartRow,
SCSIZE nSize )
pAttrArray->InsertRow( nStartRow, nSize );
}
+inline void ScColumnData::DeleteRow(SCROW nStartRow, SCSIZE nSize)
+{
+pAttrArray->DeleteRow( nStartRow, nSize );
+}
+
/* vim:set shiftwidth=4 softtabstop=4 expandtab: */
diff --git a/sc/source/core/data/table1.cxx b/sc/source/core/data/table1.cxx
index 99e0c5f39b0d..c5d4de055f8d 100644
--- a/sc/source/core/data/table1.cxx
+++ b/sc/source/core/data/table1.cxx
@@ -1849,13 +1849,11 @@ void ScTable::UpdateReference(
}
else
{
-// When deleting row(s) or column(s), allocate the last column
-// before updating the references
-if (nDx < 0 || nDy < 0)
-CreateColumnIfNotExists(rDocument.MaxCol());
-
-for (SCCOL col : GetColumnsRange(0, rDocument.MaxCol()))
-bUpdated |= CreateColumnIfNotExists(col).UpdateReference(rCxt,
pUndoDoc);
+for (SCCOL col : GetAllocatedColumnsRange(0, rDocument.MaxCol()))
+bUpdated |= aCol[col].UpdateReference(rCxt, pUndoDoc);
+// When deleting row(s), delete same row from the default attribute
+if (nDy < 0)
+aDefaultColData.DeleteRow(nRow1+nDy, -nDy);
}
if ( bIncludeDraw )
diff --git a/sc/source/core/data/table2.cxx b/sc/source/core/data/table2.cxx
index b3a5b9aee9b9..b35caa7459bb 100644
--- a/sc/source/core/data/table2.cxx
+++ b/sc/source/core/data/table2.cxx
@@ -400,6 +400,9 @@ void ScTable::DeleteCol(
{
for (SCCOL nCol = nStartCol + nSize; nCol < aCol.size(); ++nCol)
aCol[nCol].SwapCol(aCol[nCol - nSize]);
+// When delete column(s), inicialize the last columns from the default
attributes
+for (SCCOL nCol = aCol.size() - nSize; nCol < aCol.size(); ++nCol)
+aCol[nCol].Init(nCol, aCol[nCol].GetTab(), rDocument, false);
}
else
{
[Libreoffice-bugs] [Bug 104763] FILESAVE ODT->DOC: image in table anchored to para need to be marked "layout in cell" on export for MSO benefit.
https://bugs.documentfoundation.org/show_bug.cgi?id=104763 Justin L changed: What|Removed |Added Summary|FILESAVE DOC: image in |FILESAVE ODT->DOC: image in |table anchored to para need |table anchored to para need |to be marked "layout in |to be marked "layout in |cell" on export for MSO |cell" on export for MSO |benefit.|benefit. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 95623] FILEOPEN DOC Placement of images and frames wrong (multi-fly wrap ignored)
https://bugs.documentfoundation.org/show_bug.cgi?id=95623 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=80 ||206 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 80206] FILESAVE/LAYOUT ODT->DOC/X: misplaces graphs, even when opened in the same version of LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=80206 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=95 ||623 Summary|FILESAVE: Save as .doc or |FILESAVE/LAYOUT ODT->DOC/X: |.docx misplaces graphs, |misplaces graphs, even when |even when opened in the |opened in the same version |same version of LibreOffice |of LibreOffice --- Comment #16 from Justin L --- This is a poster child for layout issues. I assume one big aspect at play here is bug 95623 (dealing with multiple flies affecting layout of a single paragraph). For DOC, it doesn't seem like a FILESAVE problem. It looks pretty good in MS Word 2010 (other than the caption switched from being at the bottom, to being at the top - also happens in LO). DOCX is a total disaster from both MSO and LO perspective. There is not much point in working on this bug report specifically. Too many variables. We can keep it open and celebrate when the pieces get fixed one by one. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155757] Support Color Filter in "Standard Filter" dialog enhancement - missing background colors choice in filter field.
https://bugs.documentfoundation.org/show_bug.cgi?id=155757 --- Comment #1 from Regis Perdreau --- Created attachment 187811 --> https://bugs.documentfoundation.org/attachment.cgi?id=187811=edit test-file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155757] New: Support Color Filter in "Standard Filter" dialog enhancement - missing background colors choice in filter field.
https://bugs.documentfoundation.org/show_bug.cgi?id=155757 Bug ID: 155757 Summary: Support Color Filter in "Standard Filter" dialog enhancement - missing background colors choice in filter field. Product: LibreOffice Version: 7.6.0.0 alpha1+ Master Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: regis.perdr...@gmail.com Description: Color filter choice is missing in filter field. Steps to Reproduce: 1.load test file 2.open autofilter dialog 3.open standard filter 4. in the first line of filter dialogue "color", select in second field "background" 5. in the third field you should see a choice of different color, you'll cell content instead Actual Results: - cell contents Expected Results: - a set of background color Reproducible: Always User Profile Reset: No Additional Info: tested in Version: 7.6.0.0.beta1+ (X86_64) / LibreOffice Community Build ID: a0ce0d4418ad92dd0e3a70cf698c549b544d6084 CPU threads: 6; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: fr-FR (fr_FR); UI: fr-FR Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108799] [META] HTML and XHTML export bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108799 Bug 108799 depends on bug 155244, which changed state. Bug 155244 Summary: Blue background when exporting spreadsheet as XHTML https://bugs.documentfoundation.org/show_bug.cgi?id=155244 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142076] [META] Color filtering in Autofilter bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=142076 Bug 142076 depends on bug 143103, which changed state. Bug 143103 Summary: Support Color Filter in "Standard Filter" dialog https://bugs.documentfoundation.org/show_bug.cgi?id=143103 What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155756] New: UI Properties sidebar not displaying height over 100 and can't modify field over 100
https://bugs.documentfoundation.org/show_bug.cgi?id=155756 Bug ID: 155756 Summary: UI Properties sidebar not displaying height over 100 and can't modify field over 100 Product: LibreOffice Version: 7.5.3.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ralph...@gmail.com Created attachment 187810 --> https://bugs.documentfoundation.org/attachment.cgi?id=187810=edit Object height discrepancy between dialog and sidebar Properties sidebar seems to max out the height at 100.00. Scale is set to 1:16. I've tried 1:20 scale and it is the same issue. Dialog does display properly and does allow modification over 100. This is a good workaround. Steps to reproduce: 1) Open Draw using US Letter size page, inches units. 2) Draw a tall rectangle most of the height of the page. 3) Set scale to 1:16. Note "Height" of 100.00" in Properties tray. 5) Try to enter 105.00" and enter. It will ignore that and go back to 100.00". 4) Open "Position and Size" dialog and note the true height of the rectangle object. It allows modification to 105.00" here. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155755] FUNCTION: suggestion for MULTIPLY.IF()
https://bugs.documentfoundation.org/show_bug.cgi?id=155755 --- Comment #1 from Michel COLLET --- an improvement could be in the specification of a multiplier area and a multiplicand area. The multiplier area and the multiplicand area must have: the same size, either be in column or in line, or one could be in column and the other in line and vice versa. Each cell in the multiplier area have to be multiplied by the corresponding cell in the multiplicand area. Corresponding cells are: first cell of the multiplier area with the first cell of the multiplicand area, second one with the second one, etc -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: filter/source sc/CppunitTest_sc_html_export_test.mk sc/qa sw/qa
filter/source/xslt/odf2xhtml/export/common/table/table_rows.xsl |5 filter/source/xslt/odf2xhtml/export/common/table_of_content.xsl | 25 filter/source/xslt/odf2xhtml/export/xhtml/body.xsl | 345 +- filter/source/xslt/odf2xhtml/export/xhtml/header.xsl|7 filter/source/xslt/odf2xhtml/export/xhtml/table.xsl |6 sc/CppunitTest_sc_html_export_test.mk |5 sc/qa/extras/htmlexporttest.cxx | 18 sc/qa/extras/testdocuments/default-styles.ods |binary sw/qa/extras/htmlexport/xhtmlexport.cxx | 23 9 files changed, 394 insertions(+), 40 deletions(-) New commits: commit 2d9f739ccfead38cdaa13780f7bb5172553dbd77 Author: Svante Schubert AuthorDate: Wed May 17 17:44:39 2023 +0200 Commit: Michael Stahl CommitDate: Fri Jun 9 15:12:40 2023 +0200 tdf#155244 filter: XHTML export: Making ODF style IDs unique for ... ... HTML/CSS by adding a prefix (the @style:family with '-' as glue character) to their style name. Disabled debug output for style:family-name in XSL add text:a to text family ... and add a unit test. Change-Id: Ie846f5ea2a872872f38036aff59d29c8f530ed32 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152749 Tested-by: Jenkins Reviewed-by: Michael Stahl diff --git a/filter/source/xslt/odf2xhtml/export/common/table/table_rows.xsl b/filter/source/xslt/odf2xhtml/export/common/table/table_rows.xsl index 2d6cd7285037..60b47be753ca 100644 --- a/filter/source/xslt/odf2xhtml/export/common/table/table_rows.xsl +++ b/filter/source/xslt/odf2xhtml/export/common/table/table_rows.xsl @@ -196,7 +196,10 @@ - + + + + diff --git a/filter/source/xslt/odf2xhtml/export/common/table_of_content.xsl b/filter/source/xslt/odf2xhtml/export/common/table_of_content.xsl index 7a04bee074a8..0f36b36486de 100644 --- a/filter/source/xslt/odf2xhtml/export/common/table_of_content.xsl +++ b/filter/source/xslt/odf2xhtml/export/common/table_of_content.xsl @@ -93,7 +93,10 @@ - + + + + @@ -317,7 +320,10 @@ Scenarios unmatched: - + + + + @@ -341,7 +347,10 @@ Scenarios unmatched: - + + + + @@ -358,7 +367,10 @@ Scenarios unmatched: - + + + + @@ -382,7 +394,10 @@ Scenarios unmatched: - + + + + diff --git a/filter/source/xslt/odf2xhtml/export/xhtml/body.xsl b/filter/source/xslt/odf2xhtml/export/xhtml/body.xsl index 9706c1df0615..7b3c7e4d3b17 100644 --- a/filter/source/xslt/odf2xhtml/export/xhtml/body.xsl +++ b/filter/source/xslt/odf2xhtml/export/xhtml/body.xsl @@ -19,7 +19,7 @@ -http://www.w3.org/1999/XSL/Transform; xmlns:chart="urn:oasis:names:tc:opendocument:xmlns:chart:1.0" xmlns:config="urn:oasis:names:tc:opendocument:xmlns:config:1.0" xmlns:dc="http://purl.org/dc/elements/1.1/; xmlns:dom="http://www.w3.org/2001/xml-events;
[Libreoffice-bugs] [Bug 142076] [META] Color filtering in Autofilter bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=142076 Bug 142076 depends on bug 143103, which changed state. Bug 143103 Summary: Support Color Filter in "Standard Filter" dialog https://bugs.documentfoundation.org/show_bug.cgi?id=143103 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125876] More centralized endnote/footnote settings
https://bugs.documentfoundation.org/show_bug.cgi?id=125876 Commit Notification changed: What|Removed |Added Whiteboard||target:24.2.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 125876] More centralized endnote/footnote settings
https://bugs.documentfoundation.org/show_bug.cgi?id=125876 Commit Notification changed: What|Removed |Added Whiteboard||target:24.2.0 -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-commits] core.git: cui/inc officecfg/registry
cui/inc/tipoftheday.hrc |4 ++--
officecfg/registry/data/org/openoffice/Office/UI/WriterCommands.xcu |2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
New commits:
commit 0b1a8cc4a59fadd83bdcf13ba88bb8f68d02e106
Author: Seth Chaiklin
AuthorDate: Tue Jun 6 11:09:59 2023 +0200
Commit: Seth Chaiklin
CommitDate: Fri Jun 9 15:00:10 2023 +0200
tdf#125876 "Footnotes and Endnotes" -> "Footnote/Endnote Settings"
also update command name in "tip of day" and add links to the
dialog for the relevant tips.
Change-Id: I6dbebf3cbe405f5bd1d6d01d992cb096a5e61348
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152651
Tested-by: Jenkins
Reviewed-by: Seth Chaiklin
diff --git a/cui/inc/tipoftheday.hrc b/cui/inc/tipoftheday.hrc
index 5816a7de3676..462be2acd570 100644
--- a/cui/inc/tipoftheday.hrc
+++ b/cui/inc/tipoftheday.hrc
@@ -119,7 +119,7 @@ const std::tuple TIPOFTHEDAY_STRINGA
{ NC_("RID_CUI_TIPOFTHEDAY", "Open a CSV file as a new sheet in the
current spreadsheet via Sheet ▸ Sheet from file."), "", "", scalc},
{ NC_("RID_CUI_TIPOFTHEDAY", "You can continue writing with the default
formatting attributes after manually applying bold, italic or underline by
pressing %MOD1+Shift+X."), "", "", swriter},
{ NC_("RID_CUI_TIPOFTHEDAY", "Use %MOD1+%MOD2+Shift+V to paste the
contents of the clipboard as unformatted text."), "", "", swriter},
- { NC_("RID_CUI_TIPOFTHEDAY", "Customize footnote appearance with Tools ▸
Footnotes and Endnotes…"), "", "", swriter},
+ { NC_("RID_CUI_TIPOFTHEDAY", "Customize footnote appearance with Tools ▸
Footnote/Endnote Settings…"), ".uno:FootnoteDialog", "", swriter},
{ NC_("RID_CUI_TIPOFTHEDAY", "With Slide Show ▸ Custom Slide Show,
reorder and pick slides to fit a slideshow to the needs of your viewers."), "",
"", simpress},
{ NC_("RID_CUI_TIPOFTHEDAY", "Want to change spell checking for some part
of the text? Click in the language zone of the status bar or better, apply a
style."), "", "", swriter},
{ NC_("RID_CUI_TIPOFTHEDAY", "Writer can insert a blank page between two
odd (even) pages that follow. Check “Print automatically inserted blank pages”
in the print dialog’s %PRODUCTNAME Writer tab."), "", "", swriter},
@@ -156,7 +156,7 @@ const std::tuple TIPOFTHEDAY_STRINGA
{ NC_("RID_CUI_TIPOFTHEDAY", "Want to get a math object into Writer
quickly? Type your formula, select it, and use Insert ▸ OLE Object ▸ Formula to
convert the text."), "", "", swriter},
{ NC_("RID_CUI_TIPOFTHEDAY", "With %PRODUCTNAME it is very easy to
install a new dictionary: they are supplied as extensions."),
"https://extensions.libreoffice.org/?q=[]=50;, "", soffice},
{ NC_("RID_CUI_TIPOFTHEDAY", "%PRODUCTNAME has a portable version which
gives you mobility. Even without administrator rights on your computer you can
install %PRODUCTNAME Portable to your hard drive too."),
"https://www.libreoffice.org/download/portable-versions/;, "", soffice},
- { NC_("RID_CUI_TIPOFTHEDAY", "Writer lets you number your footnotes per
page, chapter, document: Tools ▸ Footnotes and Endnotes ▸ Footnotes tab ▸
Counting."), "", "", swriter},
+ { NC_("RID_CUI_TIPOFTHEDAY", "Writer lets you number your footnotes per
page, chapter, document: Tools ▸ Footnote/Endnote Settings ▸ Footnotes tab ▸
Counting."), ".uno:FootnoteDialog", "", swriter},
{ NC_("RID_CUI_TIPOFTHEDAY", "Your Writer document does not reopen with
the text cursor at the same editing position it was when you saved it? Add
First or Last name in Tools ▸ Options ▸ %PRODUCTNAME ▸ User Data ▸ First/last
name."), "", "", swriter},
{ NC_("RID_CUI_TIPOFTHEDAY", "Need to do citation? You can use
third-party citation managers such as Zotero."),
"https://wiki.documentfoundation.org/Referencing_Systems_in_LibreOffice;, "",
swriter},
{ NC_("RID_CUI_TIPOFTHEDAY", "Want to insert a value in the same place on
several sheets? Select the sheets: hold down %MOD1 key and click their tabs
before entering."), "", "", scalc},
diff --git
a/officecfg/registry/data/org/openoffice/Office/UI/WriterCommands.xcu
b/officecfg/registry/data/org/openoffice/Office/UI/WriterCommands.xcu
index b5f215d7d9e5..7458ed89d8e2 100644
--- a/officecfg/registry/data/org/openoffice/Office/UI/WriterCommands.xcu
+++ b/officecfg/registry/data/org/openoffice/Office/UI/WriterCommands.xcu
@@ -1489,7 +1489,7 @@
- ~Footnotes and Endnotes...
+ ~Footnote/Endnote Settings...
1
[Libreoffice-commits] core.git: helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 6c2829c48780820692f1a9ec4e8ad5e423933e09 Author: Olivier Hallot AuthorDate: Fri Jun 9 09:54:11 2023 -0300 Commit: Gerrit Code Review CommitDate: Fri Jun 9 14:54:11 2023 +0200 Update git submodules * Update helpcontent2 from branch 'master' to 9ff981baf27f13da4245b41e3bed652925657f4d - Improve wording in accessing commands Change-Id: I5e3220f33a00fd30a42de465b495802abc6e0462 Reviewed-on: https://gerrit.libreoffice.org/c/help/+/152796 Tested-by: Jenkins Reviewed-by: Olivier Hallot diff --git a/helpcontent2 b/helpcontent2 index 430c011fc246..9ff981baf27f 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit 430c011fc24671011cbdd5f6310e7681ecdaf17d +Subproject commit 9ff981baf27f13da4245b41e3bed652925657f4d
[Libreoffice-commits] help.git: source/text
source/text/shared/00/0004.xhp |6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) New commits: commit 9ff981baf27f13da4245b41e3bed652925657f4d Author: Olivier Hallot AuthorDate: Fri Jun 9 09:37:07 2023 -0300 Commit: Olivier Hallot CommitDate: Fri Jun 9 14:54:11 2023 +0200 Improve wording in accessing commands Change-Id: I5e3220f33a00fd30a42de465b495802abc6e0462 Reviewed-on: https://gerrit.libreoffice.org/c/help/+/152796 Tested-by: Jenkins Reviewed-by: Olivier Hallot diff --git a/source/text/shared/00/0004.xhp b/source/text/shared/00/0004.xhp index c51f3a63f3..382856c784 100644 --- a/source/text/shared/00/0004.xhp +++ b/source/text/shared/00/0004.xhp @@ -33,9 +33,9 @@ From the Context menu: From the Sheet Navigation bar: From the Tabbed interface: -From toolbars: -From the keyboard, press -From the Start Center, click +From Toolbars: +From the keyboard: +From the Start Center: From the Status bar:
[Libreoffice-bugs] [Bug 155755] New: FUNCTION: suggestion for MULTIPLY.IF()
https://bugs.documentfoundation.org/show_bug.cgi?id=155755 Bug ID: 155755 Summary: FUNCTION: suggestion for MULTIPLY.IF() Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mco_documentfoundation.org_UnimailQeWEbOBj39z8Xb@dclic .fr I suggest the new function MUTIPLY.IF() identical to SUM.IF() with a multiplication instead of an addition, and with the same parameters -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 95662] XHTML-Export: Export to html produces wrong decimalseparator together with bullets
https://bugs.documentfoundation.org/show_bug.cgi?id=95662 --- Comment #33 from Svante Schubert --- In Robert's ODT all XML uses correctly a dot '.' and not ',' therefore the ',' are added later and there are some possibilites of the culpit: I would like to provide some guidance to narraow down the possibilites! 1. I have checked the latest XSLT filter and could not view any ',' being added. By using his input document locally without LibreOffice (LO) the XSLT spreadsheet could be sorted out (for the latest sources). We (Michael Stahl and I) have a little test enviornment for the OASIS ODF TC that runs on Linux for the ODF2HTML XSLT, see https://github.com/oasis-tcs/odf-tc - especially the readme at: https://github.com/oasis-tcs/odf-tc/#odf2html-transformation-not-yet-automated-regression-tests 2. Be aware that not the ODT but a single XML is being provided to the ODT XSLT stylesheets by LibreOffice. To check the final flat file format, add an XSLT filter using the IDENT (identicall) transformation: https://github.com/oasis-tcs/odf-tc/blob/master/src/test/resources/odf1.4/tools/ident.xsl for instance using the fodt suffix as import/export filter, by this simply save to fodt format :-) NOTE: We added some QA guidance on how to add a stand-lone LO office, Configuration and pretty printing for ODF file XML in the ODF TC docu: https://github.com/oasis-tcs/odf-tc/#odf-editing-tool (just use the office you like) 3. Most likely the XSLT processor adds some localizied decimal-separator. Those who have the problem might want to install the XSLT 2.0 extension (see above docu as well that uses Saxon processor instead - but do not forget to fill thbe check-box using XSLT 2.0 at the XSLT filter configuration). Last but not least, I had been started writing this XSLT filter in my junior days early 2000 where HTML 4.0 was not fully implemented by browsers. When I look at the ODF of the test document using https://docs.oasis-open.org/office/OpenDocument/v1.3/os/part3-schema/OpenDocument-v1.3-os-part3-schema.html#property-text_list-level-position-and-space-mode I realized that nowadays CSS text-indent might be used: https://caniuse.com/?search=text-indent Helpful and efficient is to get into inspect mode (mouse context on selected HTML or press F12 on keyboard) and alter the HTML/CSS to watch if this might work. I consider doing some hack-fest on HTML XSLT at our next LibreOffice Conference in Bucharest, fixing the given test document.. :-) Sorry, close to no spare pro-bono time ahead (already quite booked).. ;-) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155754] New: Underlining at start of new paragraph if the previous paragraph started with an underline
https://bugs.documentfoundation.org/show_bug.cgi?id=155754 Bug ID: 155754 Summary: Underlining at start of new paragraph if the previous paragraph started with an underline Product: LibreOffice Version: 7.5.3.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: peterphilipp...@gmail.com Description: If I am writing a LibreOffice Writer document and the previous paragraph starts with an underline, the next paragraph starts with underline set. Steps to Reproduce: 1.Start a paragraph with underlined words then turn off underline 2.Insert a to start a new paragraph Actual Results: Underline is on Expected Results: Underline not on. Reproducible: Always User Profile Reset: No Additional Info: Kept the underline status to what was last used. -- You are receiving this mail because: You are the assignee for the bug.
