[Libreoffice-bugs] [Bug 134684] Conditional Colour Formatting in CALC becomes inconsistent as table columns are deleted
https://bugs.documentfoundation.org/show_bug.cgi?id=134684 --- Comment #18 from Colin --- Version: 7.4.7.2 (x64) / LibreOffice Community Build ID: 723314e595e8007d3cf785c16538505a1c878ca5 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: sv-SE (en_GB); UI: en-GB Calc: threaded Still present. Examining the MENU>Format>Conditional>Manage register identifies how additional CF lines are added by the "undo last action" rotor after all the instructions in the initial report are completed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/source
sw/source/uibase/shells/basesh.cxx |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit 88617f24d5a724c86a89058682ac04d7af9c8ea3
Author: Adolfo Jayme Barrientos
AuthorDate: Tue Aug 15 03:30:16 2023 +0200
Commit: Adolfo Jayme Barrientos
CommitDate: Tue Aug 15 06:55:54 2023 +0200
Revert "Fix typo"
This reverts commit 9d322bfa580839f48d2f4ce6cdd6b18c8253af85.
Reason for revert: British spellings are not "typos"
Change-Id: I0d9861435931b839747da9c9abad4cf61b1a4d83
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155693
Tested-by: Jenkins
Reviewed-by: Adolfo Jayme Barrientos
diff --git a/sw/source/uibase/shells/basesh.cxx
b/sw/source/uibase/shells/basesh.cxx
index 48aaf74779fb..a2ea7501e1e9 100644
--- a/sw/source/uibase/shells/basesh.cxx
+++ b/sw/source/uibase/shells/basesh.cxx
@@ -2786,7 +2786,7 @@ void SwBaseShell::ExecDlg(SfxRequest )
{
SwWrtShell = GetShell();
weld::Window* pMDI = GetView().GetFrameWeld();
-// So that from the basic no dialogs for the background views are called:
+// So that from the basic no dialogues for the background views are called:
bool bBackground = (() != GetActiveView());
const SfxPoolItem* pItem = nullptr;
const SfxItemSet* pArgs = rReq.GetArgs();
[Libreoffice-bugs] [Bug 156536] Support ranges / multi-selection for cross-referencing
https://bugs.documentfoundation.org/show_bug.cgi?id=156536 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 156549] New CAD features for cable design
https://bugs.documentfoundation.org/show_bug.cgi?id=156549 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 156536] Support ranges / multi-selection for cross-referencing
https://bugs.documentfoundation.org/show_bug.cgi?id=156536 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 156757] font issues
https://bugs.documentfoundation.org/show_bug.cgi?id=156757 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 156757] font issues
https://bugs.documentfoundation.org/show_bug.cgi?id=156757 --- Comment #7 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152523] MailMerge prints every other record
https://bugs.documentfoundation.org/show_bug.cgi?id=152523 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102998] [META] Mail merge bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102998 Bug 102998 depends on bug 152523, which changed state. Bug 152523 Summary: MailMerge prints every other record https://bugs.documentfoundation.org/show_bug.cgi?id=152523 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152523] MailMerge prints every other record
https://bugs.documentfoundation.org/show_bug.cgi?id=152523 --- Comment #3 from QA Administrators --- Dear Rev. LeRoy Cressy, 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 152331] LibreOffice Base - Autovalues not showing in report
https://bugs.documentfoundation.org/show_bug.cgi?id=152331 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152331] LibreOffice Base - Autovalues not showing in report
https://bugs.documentfoundation.org/show_bug.cgi?id=152331 --- Comment #7 from QA Administrators --- Dear romtl, 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 45077] External items in gallery extension have bad path
https://bugs.documentfoundation.org/show_bug.cgi?id=45077 --- Comment #9 from QA Administrators --- Dear Kami, 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 150991] Ordinals in date field format do not save in writer
https://bugs.documentfoundation.org/show_bug.cgi?id=150991 --- Comment #3 from QA Administrators --- Dear Ian, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138751] Not localized items in notebookbar customization
https://bugs.documentfoundation.org/show_bug.cgi?id=138751 --- Comment #9 from QA Administrators --- Dear Stanislav Horacek, 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 136449] Sections in the sidebar not a nice list after RTF paste
https://bugs.documentfoundation.org/show_bug.cgi?id=136449 --- Comment #4 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 134497] PNG not exported with the same dimensions
https://bugs.documentfoundation.org/show_bug.cgi?id=134497 --- Comment #11 from QA Administrators --- Dear taro, 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 135823] unable to unset chart border-color
https://bugs.documentfoundation.org/show_bug.cgi?id=135823 --- Comment #6 from QA Administrators --- Dear Lyndon Brown, 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 134684] Conditional Colour Formatting in CALC becomes inconsistent as table columns are deleted
https://bugs.documentfoundation.org/show_bug.cgi?id=134684 --- Comment #17 from QA Administrators --- Dear Colin, 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 133581] FILEOPEN PPT Some links not working in powerpoint slide
https://bugs.documentfoundation.org/show_bug.cgi?id=133581 --- Comment #7 from QA Administrators --- Dear Rhys Young, 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 131652] chained MULTIPLE.OPERATIONS leaves effects of first set in the cell preceding "FormulaCell"
https://bugs.documentfoundation.org/show_bug.cgi?id=131652 --- Comment #6 from QA Administrators --- Dear xyhausen, 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 127207] Dashes, dots and spaces are too large in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=127207 --- Comment #5 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 113489] Fill color of placeholder textbox doesnt appear in slide pane preview
https://bugs.documentfoundation.org/show_bug.cgi?id=113489 --- Comment #8 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-bugs] [Bug 121829] Linked section to protected (password or gpg encrypted) document does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=121829 --- Comment #10 from QA Administrators --- Dear bugzilla, 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 120194] Weird interaction between tab pages of character dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=120194 --- Comment #5 from QA Administrators --- Dear Tamás Zolnai, 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 102599] RTF Paste doesnt retain numbered list
https://bugs.documentfoundation.org/show_bug.cgi?id=102599 --- Comment #7 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-bugs] [Bug 101238] MULTIPLE.OPERATIONS fails with Err:522 - not a duplicate of 40626
https://bugs.documentfoundation.org/show_bug.cgi?id=101238 --- Comment #9 from QA Administrators --- Dear Qaz, 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 148133] EDITING: Clear Direct Formatting doesn't work correctly for text box in Impress and Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=148133 --- Comment #4 from Dev --- In Impress, for the default shape (text frame) given in a slide template (like "Title slide", "Title, content",... etc.) it won't have this problem. Only for the text box I added (also show as "Shape (text frame)" in the Navigator) will have this problem. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156757] font issues
https://bugs.documentfoundation.org/show_bug.cgi?id=156757 --- Comment #6 from ksso --- mmm, it seems the fonts are different, one is Times New Roman and the other is Times News Roman it seems the first is the real sorry for your time I uploaded the video, just in case https://www.vidlii.com/watch?v=_GViGqr7vVF again sorry... -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156757] font issues
https://bugs.documentfoundation.org/show_bug.cgi?id=156757 --- Comment #5 from ksso --- I mean, I can upload a video later, thanks... -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156757] font issues
https://bugs.documentfoundation.org/show_bug.cgi?id=156757 --- Comment #4 from ksso --- I just tested a little bit, and when I paste some file on top of a text with Times New Roman, LO receives it as the version with italic title, but if I pull down the font menu, and select Times New Roman, the system selects the font with normal title. It seems that it is not from templates, but the system plays with both fonts at the same time. If you need, you could upload another video. Thanks -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148133] EDITING: Clear Direct Formatting doesn't work correctly for text box in Impress and Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=148133 --- Comment #3 from Dev --- Reproducible in 7.6.0.1: Version: 7.6.0.1 (X86_64) / LibreOffice Community Build ID: 776eaf34564cbf3f034a0ba1fd1d5c32ff9ccf1c CPU threads: 4; OS: Linux 6.4; UI render: default; VCL: kf5 (cairo+xcb) Locale: zh-TW (zh_TW.UTF-8); UI: zh-TW Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156757] font issues
https://bugs.documentfoundation.org/show_bug.cgi?id=156757 --- Comment #3 from ksso --- The tables are for another request (to save time I made them in one video) Regarding the fonts, it's because the font in italics and the one that isn't in italics get mixed up, I don't know if it's because I have templates (from previous version of LO) with one font and the system inserts the other font, or if it's a configuration problem, but It's a problem because in the end I don't know which of the two fonts is the real one, nor how it looks in Word or on other computers... the fonts issue come from previous versions... but I don't know if it's a mistake, but it would be good if it just there is a font with only one aspect, it is an opinion Steps to reproduce 1. install LO (in ubuntu is already installed) I used this commands (may be some are repeated) sudo apt-get install libreoffice-base libreoffice libreoffice-l10n-es libreoffice-lightproof-en libreoffice-templates libreoffice-help-es mythes-es hyphen-es libreoffice-gtk3 libreoffice-gnome unixodbc cups-bsd libsane-common libxrender1 libgl1 openclipart-libreoffice sudo add-apt-repository ppa:libreoffice/ppa sudo apt update sudo apt upgrade sudo apt install libreoffice-l10n-de hunspell-de-de-frami hyphen-de mythes-de libreoffice-help-de sudo apt install hunspell-en-us hyphen-en-us mythes-en-us libreoffice-help-en-us sudo apt install libreoffice-gtk3 sudo apt install libreoffice-style* 2. now you have to time new roman font (italic and non italic title), same size, same name, different appearance -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 88278] [META] SVG import image filter (all modules)
https://bugs.documentfoundation.org/show_bug.cgi?id=88278 Bug 88278 depends on bug 93583, which changed state. Bug 93583 Summary: EDITING formatted text on embedded SVG file displayed incorrectly https://bugs.documentfoundation.org/show_bug.cgi?id=93583 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 88278] [META] SVG import image filter (all modules)
https://bugs.documentfoundation.org/show_bug.cgi?id=88278 Bug 88278 depends on bug 86938, which changed state. Bug 86938 Summary: inserted SVG image gets mangled: vertical position of text https://bugs.documentfoundation.org/show_bug.cgi?id=86938 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: 2 commits - svgio/inc svgio/qa svgio/source
svgio/inc/svgcharacternode.hxx|4 +
svgio/inc/svgtspannode.hxx|8 +-
svgio/qa/cppunit/SvgImportTest.cxx| 52 ++
svgio/qa/cppunit/data/tdf86938.svg| 13
svgio/qa/cppunit/data/tdf93583.svg|7 ++
svgio/source/svgreader/svgcharacternode.cxx | 72 +-
svgio/source/svgreader/svgdocumenthandler.cxx | 24
svgio/source/svgreader/svgtspannode.cxx |3 -
8 files changed, 143 insertions(+), 40 deletions(-)
New commits:
commit a2b6be8af9be3237efc3ed1244302cf899680e97
Author: Xisco Fauli
AuthorDate: Mon Aug 14 17:34:00 2023 +0200
Commit: Xisco Fauli
CommitDate: Tue Aug 15 03:53:18 2023 +0200
tdf#86938: fix calculation of baseline-shift
Change-Id: I8c30c29052f2ea1fe6e49360b972af868851131b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155671
Tested-by: Jenkins
Reviewed-by: Xisco Fauli
diff --git a/svgio/qa/cppunit/SvgImportTest.cxx
b/svgio/qa/cppunit/SvgImportTest.cxx
index 53f6b23da4fd..d68e7ebf728a 100644
--- a/svgio/qa/cppunit/SvgImportTest.cxx
+++ b/svgio/qa/cppunit/SvgImportTest.cxx
@@ -746,6 +746,31 @@ CPPUNIT_TEST_FIXTURE(Test, testTdf85770)
assertXPath(pDocument, "/primitive2D/transform/textsimpleportion[3]",
"familyname", "Times New Roman");
}
+CPPUNIT_TEST_FIXTURE(Test, testTdf86938)
+{
+Primitive2DSequence aSequence =
parseSvg(u"/svgio/qa/cppunit/data/tdf86938.svg");
+CPPUNIT_ASSERT_EQUAL(1, static_cast(aSequence.getLength()));
+
+drawinglayer::Primitive2dXmlDump dumper;
+xmlDocUniquePtr pDocument =
dumper.dumpAndParse(Primitive2DContainer(aSequence));
+
+CPPUNIT_ASSERT (pDocument);
+
+assertXPath(pDocument, "/primitive2D/transform/textsimpleportion[1]",
"text", "line");
+assertXPath(pDocument, "/primitive2D/transform/textsimpleportion[1]", "x",
"290");
+assertXPath(pDocument, "/primitive2D/transform/textsimpleportion[1]", "y",
"183");
+assertXPath(pDocument, "/primitive2D/transform/textsimpleportion[2]",
"text", "above");
+assertXPath(pDocument, "/primitive2D/transform/textsimpleportion[2]", "x",
"290");
+
+// Without the fix in place, this test would have failed with
+// - Expected: 159
+// - Actual : 207
+assertXPath(pDocument, "/primitive2D/transform/textsimpleportion[2]", "y",
"159");
+assertXPath(pDocument, "/primitive2D/transform/textsimpleportion[3]",
"text", "below");
+assertXPath(pDocument, "/primitive2D/transform/textsimpleportion[3]", "x",
"290");
+assertXPath(pDocument, "/primitive2D/transform/textsimpleportion[3]", "y",
"207");
+}
+
CPPUNIT_TEST_FIXTURE(Test, testTdf93583)
{
Primitive2DSequence aSequence =
parseSvg(u"/svgio/qa/cppunit/data/tdf93583.svg");
diff --git a/svgio/qa/cppunit/data/tdf86938.svg
b/svgio/qa/cppunit/data/tdf86938.svg
new file mode 100644
index ..40287a39de88
--- /dev/null
+++ b/svgio/qa/cppunit/data/tdf86938.svg
@@ -0,0 +1,13 @@
+http://www.w3.org/2000/svg;>
+ line
+ above
+ below
+
diff --git a/svgio/source/svgreader/svgcharacternode.cxx
b/svgio/source/svgreader/svgcharacternode.cxx
index ebc317c3a445..91ec98ae9b68 100644
--- a/svgio/source/svgreader/svgcharacternode.cxx
+++ b/svgio/source/svgreader/svgcharacternode.cxx
@@ -301,7 +301,7 @@ namespace svgio::svgreader
const SvgNumber
aNumber(rSvgStyleAttributes.getBaselineShiftNumber());
const double mfBaselineShift(aNumber.solve(*this));
-aPosition.setY(aPosition.getY() + mfBaselineShift);
+aPosition.setY(aPosition.getY() - mfBaselineShift);
break;
}
default: // BaselineShift::Baseline
commit 5cfd31e505b4d1b4f9d2e21b0f9f8aac22539f47
Author: Xisco Fauli
AuthorDate: Mon Aug 14 14:52:41 2023 +0200
Commit: Xisco Fauli
CommitDate: Tue Aug 15 03:53:06 2023 +0200
tdf#93583: use getTextWidth to calculate line's width
Since every character in the line might use different styles
Change-Id: I2ce079d4308f4acde42a8366838749a7c20331b4
Change-Id: I01f51f157caa667cebc8860ae37d4458fac2d511
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155666
Tested-by: Jenkins
Reviewed-by: Xisco Fauli
diff --git a/svgio/inc/svgcharacternode.hxx b/svgio/inc/svgcharacternode.hxx
index 059aa9ece1fd..d81066af47a6 100644
--- a/svgio/inc/svgcharacternode.hxx
+++ b/svgio/inc/svgcharacternode.hxx
@@ -24,6 +24,7 @@
#include
+#include
#include "svgtextnode.hxx"
#include "svgtextposition.hxx"
@@ -58,6 +59,9 @@ namespace svgio::svgreader
OUString aText);
virtual ~SvgCharacterNode() override;
+static drawinglayer::attribute::FontAttribute getFontAttribute(
+const SvgStyleAttributes& rSvgStyleAttributes);
+
virtual const
[Libreoffice-bugs] [Bug 156771] Mail Merge create fails to include all lines with fields
https://bugs.documentfoundation.org/show_bug.cgi?id=156771 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #1 from m.a.riosv --- Please attach the needed sample files. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156759] "mouse pointer as pen" does not work when Skia off and hardware acceleration on
https://bugs.documentfoundation.org/show_bug.cgi?id=156759 --- Comment #5 from m.a.riosv --- Created attachment 188976 --> https://bugs.documentfoundation.org/attachment.cgi?id=188976=edit Video with 24.2.0.0.alpha0 518fa99dd7693d64a53e404a065090aedc0002b1 2023-08-14 17:58:41 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156759] "mouse pointer as pen" does not work when Skia off and hardware acceleration on
https://bugs.documentfoundation.org/show_bug.cgi?id=156759 --- Comment #4 from m.a.riosv --- I was some version behind, but works for me with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 218a7650a5cf03f895bed19c68d6f02daec536e9 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: default; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded and Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 518fa99dd7693d64a53e404a065090aedc0002b1 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: default; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded downloaded 2023-08-14 17:58:41 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156757] font issues
https://bugs.documentfoundation.org/show_bug.cgi?id=156757 Aaron changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO CC||aaronth...@gmail.com Ever confirmed|0 |1 --- Comment #2 from Aaron --- Thank you for reporting the bug. Unfortunately without clear steps to reproduce it, we cannot track down the origin of the problem. Please provide a clearer set of step-by-step instructions on how to reproduce the problem. I can see from attachment 188951 that indeed the two paragraphs have different aspects despite having the same font and sizes and that is a strange problem but I did not understand the issue with the table. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested information is provided. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113079] [META] Unformatted text paste special bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=113079 Bug 113079 depends on bug 137267, which changed state. Bug 137267 Summary: clipboard error on paste into a cell https://bugs.documentfoundation.org/show_bug.cgi?id=137267 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137267] clipboard error on paste into a cell
https://bugs.documentfoundation.org/show_bug.cgi?id=137267 Aaron changed: What|Removed |Added CC||aaronth...@gmail.com Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #3 from Aaron --- Thank you for reporting this. This bug is no longer reproducible in Version: 7.5.5.2 (X86_64) / LibreOffice Community Build ID: ca8fe7424262805f223b9a2334bc7181abbcbf5e CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-AU (fr_FR); UI: en-US Calc: threaded I tested pasting html text into a selected cell but I received no "Error reading from clipboard" displayed. I followed the steps to reproduce and the actual results and expected results matched i.e. "blablabla" is copied to the selected cell at the right top. Seems it's no longer reproducible. Changing status to RESOLVED WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156759] "mouse pointer as pen" does not work when Skia off and hardware acceleration on
https://bugs.documentfoundation.org/show_bug.cgi?id=156759 --- Comment #3 from m.a.riosv --- Created attachment 188975 --> https://bugs.documentfoundation.org/attachment.cgi?id=188975=edit Video with 24.2.0.0.alpha0+ I can reproduce with sample file. Version: 7.6.0.3 (X86_64) / LibreOffice Community Build ID: 69edd8b8ebc41d00b4de3915dc82f8f0fc3b6265 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: default; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded But non with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 218a7650a5cf03f895bed19c68d6f02daec536e9 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: default; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded it doesn't paint too smoothly, but it works quite well for me. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153306] Cursor leftovers keep being displayed when using Skia Vulkan/Metal
https://bugs.documentfoundation.org/show_bug.cgi?id=153306 --- Comment #14 from greg.diehl@gmail.com --- I was able to reproduce this issue, when I move the indentation on the ruler, with a iMac 21.5" Intel running macOS 13.5 with the current release of LibreOffice Version: 7.5.5.2 (X86_64) / LibreOffice Community Build ID: ca8fe7424262805f223b9a2334bc7181abbcbf5e CPU threads: 4; OS: Mac OS X 13.5; UI render: Skia/Metal; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Downloaded the current nightly build and I was unable to reproduce the problem Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1f2c7422216f568b148ddfbe75412d605335c110 CPU threads: 4; OS: Mac OS X 13.5; UI render: Skia/Metal; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156768] No page number wizard found in LibreOffice Writer 7.6
https://bugs.documentfoundation.org/show_bug.cgi?id=156768 Justin L changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Justin L --- (In reply to David García from comment #2) > Should I do the reset button every time there's a big update, like between > 7.4 and 7.5, or between 7.5 and 7.6? You should only do it when you want to lose all your custom menu settings :-) But yeah, normally there aren't many menu changes after x.y.0. Hmm - I wonder if this reset does the same "bad" thing that notebookbar did (bug 148121) - copy the default overtop of a user profile? It would be better if it simply deleted the user profile file. No, it looks good. It appears that cui/source/customize/cfg.cxx calls GetConfigManager()->removeSettings for MenuSaveInData::Reset. I confirmed that reset removed menubar.xml from instdir/user/config/soffice.cfg/modules/swriter/menubar. *** This bug has been marked as a duplicate of bug 156743 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156743] modified menu is branched from the master forever
https://bugs.documentfoundation.org/show_bug.cgi?id=156743 Justin L changed: What|Removed |Added CC||vivada...@hotmail.com --- Comment #1 from Justin L --- *** Bug 156768 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122784] Mouse pointer as pen doesn't work
https://bugs.documentfoundation.org/show_bug.cgi?id=122784 Regina Henschel changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||6759 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156759] "mouse pointer as pen" does not work when Skia off and hardware acceleration on
https://bugs.documentfoundation.org/show_bug.cgi?id=156759 Regina Henschel changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||2784 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138553] When I write formula, I can't see the selected cells
https://bugs.documentfoundation.org/show_bug.cgi?id=138553 Aaron changed: What|Removed |Added CC||aaronth...@gmail.com --- Comment #3 from Aaron --- Hi, this bug is still present in Version: 7.5.5.2 (X86_64) / LibreOffice Community Build ID: ca8fe7424262805f223b9a2334bc7181abbcbf5e CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-AU (fr_FR); UI: en-US Calc: threaded But like neuffbn said I'm not sure if it's intentional design or not. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156731] Python script provider does not reload embedded scripts updated from external file
https://bugs.documentfoundation.org/show_bug.cgi?id=156731 --- Comment #2 from Werner Tietz --- The Problem is the Combination of Embedded Code AND the »Link« from some Event, executing via →Tools→Macros works well. Sorry didnt know how to fix, but only the Workaround →save the Document and →reload the Document. have a look on the changed Code ( doesnt solve the issue ) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156731] Python script provider does not reload embedded scripts updated from external file
https://bugs.documentfoundation.org/show_bug.cgi?id=156731 --- Comment #1 from Werner Tietz --- Created attachment 188974 --> https://bugs.documentfoundation.org/attachment.cgi?id=188974=edit some improvement unrelated to the issue -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156759] "mouse pointer as pen" does not work when Skia off and hardware acceleration on
https://bugs.documentfoundation.org/show_bug.cgi?id=156759 --- Comment #2 from Regina Henschel --- Created attachment 188973 --> https://bugs.documentfoundation.org/attachment.cgi?id=188973=edit Mini presentation with gradient in background of master The problems are older. Open attached document and start slide show. From context menu check "mouse pointer as pen" and draw something. Version: 5.4.4.1 (x64) Build ID: da790616461e15a10c95a80eb8ef8ee7b726c114 CPU threads: 8; OS: Windows 6.19; UI render: default; Locale: en-US (en_US); Calc: group OpenGL On, hardware acceleration disabled => gradient OK, pen works. OpenGL off and hardware acceleration On => gradient OK, pen works. OpenGL off and hardware acceleration Off => gradient has white lines, pen works. Version: 6.2.2.2 (x64) Build ID: 2b840030fec2aae0fd2658d8d4f9548af4e3518d CPU threads: 8; OS: Windows 10.0; UI render: default; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded OpenGL On, hardware acceleration disabled => gradient OK, pen works. OpenGL off and hardware acceleration On => gradient OK, pen fails OpenGL off and hardware acceleration Off => gradient has white lines, pen works. Version: 7.2.0.4 (x64) / LibreOffice Community Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL Skia On, hardware acceleration disabled => gradient wrong, pen works. Skia Off and hardware acceleration On => gradient OK, pen fails. Skia Off and hardware acceleration Off => gradient wrong, pen works. Same for daily Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 218a7650a5cf03f895bed19c68d6f02daec536e9 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
New Defects reported by Coverity Scan for LibreOffice
Hi, Please find the latest report on new defect(s) introduced to LibreOffice found with Coverity Scan. 1 new defect(s) introduced to LibreOffice found with Coverity Scan. 3 defect(s), reported by Coverity Scan earlier, were marked fixed in the recent build analyzed by Coverity Scan. New defect(s) Reported-by: Coverity Scan Showing 1 of 1 defect(s) ** CID 1539919: Null pointer dereferences (FORWARD_NULL) *** CID 1539919: Null pointer dereferences (FORWARD_NULL) /slideshow/source/engine/slideshowimpl.cxx: 1546 in ::SlideShowImpl::registerUserPaintPolygons(const com::sun::star::uno::Reference &)() 1540 //Add the shape to the slide 1541 Shapes->add(rPolyShape); 1542 //Construct a sequence of points sequence 1543 const drawing::PointSequenceSequence aRetval 1544 = lcl_createPointSequenceSequenceFromB2DPolygon(aDrawingPoints); 1545 //Fill the properties >>> CID 1539919: Null pointer dereferences (FORWARD_NULL) >>> Passing "cppcanvas::PolyPolygonSharedPtr(pFirstPolyPoly)" to >>> "lcl_setPropertiesToShape", which dereferences null >>> "cppcanvas::PolyPolygonSharedPtr(pFirstPolyPoly)". 1546 lcl_setPropertiesToShape(aRetval, pFirstPolyPoly, rPolyShape); 1547 // make polygons special 1548 xLayerManager->attachShapeToLayer(rPolyShape, xDrawnInSlideshow); 1549 // Start next pen drawing object 1550 aDrawingPoints.clear(); 1551 aDrawingPoints.append(aPoly); To view the defects in Coverity Scan visit, https://u15810271.ct.sendgrid.net/ls/click?upn=HRESupC-2F2Czv4BOaCWWCy7my0P0qcxCbhZ31OYv50ypSs1kiFPuCn2xFdlMIFBirii0zZ9j2-2F9F2XPBcBm2BNgi9duPy3v-2FzgFDd2LJ-2BDKI-3Dsofg_OTq2XUZbbipYjyLSo6GRo-2FpVxQ9OzkDINu9UTS-2FQhSdO0F0jQniitrGlNxDIzPJiMZV5w-2BadXib3ZOTUZxa7Me6ECr3qkd1vXasZok1ijlouz-2FV1CX3Kg6d0SjeHp3Jr-2BhXkKQ072eHwaLmCtdhVt8NiFA-2BOxZWSHXRQ-2B-2FjXpD3vZHN-2FMIzBFlAuY7AMq21kyZH8WYiKCx5jaW0lsFqKksNNwjhJ0JqmVZl0d3CegIuUgtK2oohWpbcNBDNpWd0c
Week #10 report - GSoC 2023 - APNG support
Hello! This week I did work on the UI side of saving APNGs. Should be finished some time this week, and then APNG support is officially finished Thanks!
[Libreoffice-bugs] [Bug 156769] Special characters not appearing as autotext replacements
https://bugs.documentfoundation.org/show_bug.cgi?id=156769 Mike Kaganski changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #5 from Mike Kaganski --- (In reply to Anthony from comment #4) > ?-F3 Repro. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102495] [META] KDE (kf5) VCL backend bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102495 Michael Weghorn changed: What|Removed |Added Depends on||156562 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156562 [Bug 156562] Source unknown when pasting with ctrl+shift in Wayland (Linux) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156562] Source unknown when pasting with ctrl+shift in Wayland (Linux)
https://bugs.documentfoundation.org/show_bug.cgi?id=156562 Michael Weghorn changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||m.wegh...@posteo.de Ever confirmed|0 |1 Blocks||102495 --- Comment #1 from Michael Weghorn --- I can reproduce that on Debian testing in a Plasma Wayland session, e.g. as follows: 1) start LO Writer 2) select text "hello world" in Gedit, Ctrl+C 3) switch to LO Writer, Ctrl+Shift+V, select "Unformatted Text" It works when just using Ctrl+V. Also works when using the gtk3 VCL plugin (set environment variable SAL_USE_VCLPLUGIN=gtk3 before starting LO) or when forcing the use of the Qt X11 backend (QT_QPA_PLATFORM=xcb). With a debug build, these warnings can be seen in the terminal from which LO was started: warn:vcl.qt:293019:293019:vcl/qt5/QtTransferable.cxx:181: In flight clipboard change detected - broken clipboard read! warn:vcl.qt:293019:293019:vcl/qt5/QtTransferable.cxx:181: In flight clipboard change detected - broken clipboard read! warn:vcl.qt:293019:293019:vcl/qt5/QtTransferable.cxx:181: In flight clipboard change detected - broken clipboard read! Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d1d07992a89ba503f1d457a8f79926063f4d3f9c CPU threads: 12; OS: Linux 6.4; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102495 [Bug 102495] [META] KDE (kf5) VCL backend bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156769] Special characters not appearing as autotext replacements
https://bugs.documentfoundation.org/show_bug.cgi?id=156769 --- Comment #4 from Anthony --- The inverted question-mark (¿), triggered by ?-F3 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155816] FILEOPEN PPTX: style of master page placeholder objects are inadequately imported and saved to ODP
https://bugs.documentfoundation.org/show_bug.cgi?id=155816 Aron Budea changed: What|Removed |Added Version|unspecified |Inherited From OOo Hardware|x86-64 (AMD64) |All --- Comment #2 from Aron Budea --- Adjusting earliest version, since it was never OK. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103610] [META] Slide show (presentation mode) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103610 Bug 103610 depends on bug 154265, which changed state. Bug 154265 Summary: Cannot return to (first) slide when in presentation mode https://bugs.documentfoundation.org/show_bug.cgi?id=154265 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156768] No page number wizard found in LibreOffice Writer 7.6
https://bugs.documentfoundation.org/show_bug.cgi?id=156768 --- Comment #2 from David García --- Thank you! I had no idea this could happen. Eventually, I went to Tools > Customize and then I clicked on "Reset". Unfortunately, I've lost my settings, but it's not a big deal. Should I do the reset button every time there's a big update, like between 7.4 and 7.5, or between 7.5 and 7.6? I presume you don't have to do it between minor versions (like between 7.5.1 and 7.5.2, for example). Thanks again! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: slideshow/source
slideshow/source/engine/slideshowimpl.cxx |7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
New commits:
commit 850b66f969834e61f3cb1a1ccd4bfc15f23d558f
Author: Samuel Mehrbrodt
AuthorDate: Mon Aug 14 14:13:05 2023 +0200
Commit: Samuel Mehrbrodt
CommitDate: Mon Aug 14 21:40:33 2023 +0200
tdf#154265 Disable automatic slide advancement when moving backwards
When a slide has a 0 second automatic slide advance setting, and you move
back to that slide, it would immediately move forward again.
Only enable automatic slide advancement when moving forwards.
Change-Id: I3c901bed5323569f5cf52aeca5b3227c87b6e539
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155663
Tested-by: Jenkins
Reviewed-by: Samuel Mehrbrodt
diff --git a/slideshow/source/engine/slideshowimpl.cxx
b/slideshow/source/engine/slideshowimpl.cxx
index f681dc2a9559..33a9825e544a 100644
--- a/slideshow/source/engine/slideshowimpl.cxx
+++ b/slideshow/source/engine/slideshowimpl.cxx
@@ -479,6 +479,7 @@ private:
boolmbShowPaused;
boolmbSlideShowIdle;
boolmbDisableAnimationZOrder;
+boolmbMovingForward;
EffectRewinder maEffectRewinder;
FrameSynchronizationmaFrameSynchronization;
@@ -590,6 +591,7 @@ SlideShowImpl::SlideShowImpl(
mbShowPaused( false ),
mbSlideShowIdle( true ),
mbDisableAnimationZOrder( false ),
+ mbMovingForward( true ),
maEffectRewinder(maEventMultiplexer, maEventQueue, maUserEventQueue),
maFrameSynchronization(1.0 / FrameRate::PreferredFramesPerSecond)
@@ -1215,6 +1217,7 @@ void SlideShowImpl::redisplayCurrentSlide()
sal_Bool SlideShowImpl::nextEffect()
{
+mbMovingForward = true;
osl::MutexGuard const guard( m_aMutex );
if (isDisposed())
@@ -1231,6 +1234,7 @@ sal_Bool SlideShowImpl::nextEffect()
sal_Bool SlideShowImpl::previousEffect()
{
+mbMovingForward = false;
osl::MutexGuard const guard( m_aMutex );
if (isDisposed())
@@ -2310,7 +2314,8 @@ void SlideShowImpl::notifySlideAnimationsEnded()
// step slides manually.
if( !mbForceManualAdvance &&
!mpRehearseTimingsActivity &&
-bHasAutomaticNextSlide )
+bHasAutomaticNextSlide &&
+mbMovingForward )
{
aNotificationEvents = makeInterruptableDelay(
[this]() { return this->notifySlideEnded( false ); },
[Libreoffice-commits] core.git: sc/source
sc/source/filter/excel/xeescher.cxx |9 -
1 file changed, 4 insertions(+), 5 deletions(-)
New commits:
commit d827d36625e8952ef3bfadbf8de76578074d474d
Author: Caolán McNamara
AuthorDate: Mon Aug 14 11:14:14 2023 +0100
Commit: Caolán McNamara
CommitDate: Mon Aug 14 21:26:11 2023 +0200
move GetEditTextObject to after it is potentially generated
Change-Id: Iadd6a2b66e3131b8883cf3812b5f0a8153631abe
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155660
Tested-by: Jenkins
Reviewed-by: Caolán McNamara
diff --git a/sc/source/filter/excel/xeescher.cxx
b/sc/source/filter/excel/xeescher.cxx
index 04c1f1b9efbd..c7926a9b6f12 100644
--- a/sc/source/filter/excel/xeescher.cxx
+++ b/sc/source/filter/excel/xeescher.cxx
@@ -1643,12 +1643,8 @@ XclExpNote::XclExpNote(const XclExpRoot& rRoot, const
ScAddress& rScPos,
// get the main note text
OUString aNoteText;
if( pScNote )
-{
aNoteText = pScNote->GetText();
-const EditTextObject *pEditObj = pScNote->GetEditTextObject();
-if( pEditObj )
-mpNoteContents = XclExpStringHelper::CreateString( rRoot,
*pEditObj );
-}
+
// append additional text
aNoteText = ScGlobal::addToken( aNoteText, rAddText, '\n', 2 );
@@ -1689,6 +1685,9 @@ XclExpNote::XclExpNote(const XclExpRoot& rRoot, const
ScAddress& rScPos,
maAuthor = XclExpString( " " );
else
maAuthor = XclExpString( pScNote->GetAuthor(),
XclStrFlags::NONE, 54 );
+
+if (const EditTextObject *pEditObj =
pScNote->GetEditTextObject())
+mpNoteContents = XclExpStringHelper::CreateString( rRoot,
*pEditObj );
}
SetRecSize( 9 + maAuthor.GetSize() );
[Libreoffice-bugs] [Bug 156772] Create a package (folder) with original document and linked and embedded images
https://bugs.documentfoundation.org/show_bug.cgi?id=156772 Davide changed: What|Removed |Added Blocks||156767 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156767 [Bug 156767] [META] Technical Writer (EDITING) Suggested bug fixes, enhancements and features for technical writers. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156767] [META] Technical Writer (EDITING) Suggested bug fixes, enhancements and features for technical writers.
https://bugs.documentfoundation.org/show_bug.cgi?id=156767 Davide changed: What|Removed |Added Depends on||156772 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156772 [Bug 156772] Create a package (folder) with original document and linked and embedded images -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156772] New: Create a package (folder) with original document and linked and embedded images
https://bugs.documentfoundation.org/show_bug.cgi?id=156772 Bug ID: 156772 Summary: Create a package (folder) with original document and linked and embedded images Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: davide.p...@gmail.com Description: Creation of a folder containing the .odt file or master document and related files and a subfolder containing the images originally linked to the document or embedded in it. Typical use: send to a translator, archiving, send for shared job Steps to Reproduce: Typical steps could be: 1-File > Export > Create package 2- Select options: - Create pdf to be included in the package - Select destination folder - The original name of the image files is kept Actual Results: The above actions are not possible. Expected Results: Reproducible: Always User Profile Reset: No Additional Info: Actually an extension exists to export images (PicExtract 1.0.1 by Kay Struck) but the creation of such a package is not supported. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156769] Special characters not appearing as autotext replacements
https://bugs.documentfoundation.org/show_bug.cgi?id=156769 --- Comment #3 from Mike Kaganski --- (In reply to Anthony from comment #2) > 2 Good question but no, I did not forget. I do the "Autotext button -> > New?" step, close the auto text window, type the autotext char+ F3 and > nothing is inserted (to be super-clear, the character that is triggering the > autotext is erased, and no text is inserted in it's place). Which char did you use? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156745] CLI PDF export: document is 2 pages instead of 7
https://bugs.documentfoundation.org/show_bug.cgi?id=156745 --- Comment #1 from Commit Notification --- Michael Stahl committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/610c6f02b11b4b4c555a78b0feb2a1eb35159e39 tdf#156724 tdf#156722 tdf#156745 sw: layout: partially remove IsPaintLocked() It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156745] CLI PDF export: document is 2 pages instead of 7
https://bugs.documentfoundation.org/show_bug.cgi?id=156745 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-bugs] [Bug 156722] Document layout changed in PDF export: content in frames slips upwards
https://bugs.documentfoundation.org/show_bug.cgi?id=156722 --- Comment #2 from Commit Notification --- Michael Stahl committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/610c6f02b11b4b4c555a78b0feb2a1eb35159e39 tdf#156724 tdf#156722 tdf#156745 sw: layout: partially remove IsPaintLocked() It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/qa sw/source
sw/qa/extras/layout/data/fdo56797-2-min.odt |binary
sw/qa/extras/layout/layout3.cxx | 31
sw/source/core/layout/layact.cxx|6 ++---
3 files changed, 34 insertions(+), 3 deletions(-)
New commits:
commit 610c6f02b11b4b4c555a78b0feb2a1eb35159e39
Author: Michael Stahl
AuthorDate: Mon Aug 14 17:13:17 2023 +0200
Commit: Michael Stahl
CommitDate: Mon Aug 14 21:15:46 2023 +0200
tdf#156724 tdf#156722 tdf#156745 sw: layout: partially remove
IsPaintLocked()
Having the layout algorithm dependend on IsPaintLocked() is very
problematic; it is typically set when the layout is invoked from
SwViewShell code, as happens several times when loading a document in
response to window resize events etc., but not for idle formatting or
from SwXTextDocument::getRendererCount(), hence these bugs only
reproduce with soffice --convert-to pdf, not via UI.
For tdf#156724 the problem is that the table is split, during formatting
of the split row a new footnote is created on page 1, and this reduces
the space, so splitting fails and is never attempted again.
When the document is loaded from UI, when the table is split the
footnote already exists and so splitting succeeds; it was created by
a call from SwLayAction::FormatLayout() of the cell frame.
It turns out that when the condition is removed completely, testUXTSOREL
will take 5 minutes instead of 5 seconds, which seems excessive; the
problem there appears to be that a text frame in a columned section
moves forward and backward; plausibly columned section content should be
formatted by ::CalcContent() only.
(reportedly regression from commit c605283ad6785dea762feab5fdffd9d27e75c292
and commit
7e8b4756d95057f069467b34e7849f9354856578)
Change-Id: I9ed73588efeec654a769eee8aa825186bd51e059
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155672
Tested-by: Michael Stahl
Reviewed-by: Michael Stahl
diff --git a/sw/qa/extras/layout/data/fdo56797-2-min.odt
b/sw/qa/extras/layout/data/fdo56797-2-min.odt
new file mode 100644
index ..624149ec0248
Binary files /dev/null and b/sw/qa/extras/layout/data/fdo56797-2-min.odt differ
diff --git a/sw/qa/extras/layout/layout3.cxx b/sw/qa/extras/layout/layout3.cxx
index f26a6af25abf..9e47f435df94 100644
--- a/sw/qa/extras/layout/layout3.cxx
+++ b/sw/qa/extras/layout/layout3.cxx
@@ -1176,6 +1176,37 @@ CPPUNIT_TEST_FIXTURE(SwLayoutWriter3, testTdf128399)
CPPUNIT_ASSERT_EQUAL(nExpected, aPosition.GetNodeIndex());
}
+CPPUNIT_TEST_FIXTURE(SwLayoutWriter3, testTdf156724)
+{
+discardDumpedLayout();
+if (mxComponent.is())
+mxComponent->dispose();
+
+OUString const url(createFileURL(u"fdo56797-2-min.odt"));
+
+// note: must set Hidden property, so that
SfxFrameViewWindow_Impl::Resize()
+// does *not* forward initial VCL Window Resize and thereby triggers a
+// layout which does not happen on soffice --convert-to pdf.
+std::vector aFilterOptions = {
+{ beans::PropertyValue("Hidden", -1, uno::Any(true),
beans::PropertyState_DIRECT_VALUE) },
+};
+
+// inline the loading because currently properties can't be passed...
+mxComponent = loadFromDesktop(url, "com.sun.star.text.TextDocument",
+
comphelper::containerToSequence(aFilterOptions));
+save("writer_pdf_Export");
+
+xmlDocUniquePtr pXmlDoc = parseLayoutDump();
+// both pages have a tab frame and one footnote
+assertXPath(pXmlDoc, "/root/page[1]/body/tab", 1);
+assertXPath(pXmlDoc, "/root/page[1]/ftncont", 1);
+assertXPath(pXmlDoc, "/root/page[1]/ftncont/ftn", 1);
+assertXPath(pXmlDoc, "/root/page[2]/body/tab", 1);
+assertXPath(pXmlDoc, "/root/page[2]/ftncont", 1);
+assertXPath(pXmlDoc, "/root/page[2]/ftncont/ftn", 1);
+assertXPath(pXmlDoc, "/root/page", 2);
+}
+
CPPUNIT_TEST_FIXTURE(SwLayoutWriter3, testTdf145826)
{
createSwDoc("tdf145826.odt");
diff --git a/sw/source/core/layout/layact.cxx b/sw/source/core/layout/layact.cxx
index ecce180eb336..af93ab796ff6 100644
--- a/sw/source/core/layout/layact.cxx
+++ b/sw/source/core/layout/layact.cxx
@@ -1431,10 +1431,10 @@ bool SwLayAction::FormatLayout( OutputDevice
*pRenderContext, SwLayoutFrame *pLa
PopFormatLayout();
}
}
-else if ( m_pImp->GetShell()->IsPaintLocked() )
-// Shortcut to minimize the cycles. With Lock, the
-// paint is coming either way (primarily for browse)
+else if (m_pImp->GetShell()->IsPaintLocked() ||
!pLay->IsColBodyFrame())
+{ // tdf#156724 unconditionally for frames in tables, so their
footnotes exist before trying to split
pLow->OptCalc();
+}
if ( IsAgain() )
return false;
[Libreoffice-bugs] [Bug 156722] Document layout changed in PDF export: content in frames slips upwards
https://bugs.documentfoundation.org/show_bug.cgi?id=156722 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-bugs] [Bug 156724] Document layout changed in PDF export: content overlaps footnote
https://bugs.documentfoundation.org/show_bug.cgi?id=156724 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-bugs] [Bug 156764] Tools>Language>For All Text hangs if multiple languages are involved
https://bugs.documentfoundation.org/show_bug.cgi?id=156764 raal changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||r...@post.cz --- Comment #3 from raal --- Hello, as mentioned in https://bugs.documentfoundation.org/show_bug.cgi?id=156535#c2 it should be resolved in 7.5.5. Please update first. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/CppunitTest_sw_apitests.mk sw/qa
sw/CppunitTest_sw_apitests.mk |1
sw/qa/api/SwXTableCellText.cxx | 103 +
2 files changed, 104 insertions(+)
New commits:
commit b9e72b2577da2a0a61e95ff8a0a7f289f194c59b
Author: anfanite396
AuthorDate: Thu Jul 6 11:18:21 2023 +0530
Commit: Tomaž Vajngerl
CommitDate: Mon Aug 14 21:06:56 2023 +0200
Move SwXTableCellText Java tests to C++
Change-Id: Iea2113030bb82ee02bd84140f5def7040b4f4fcb
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/154087
Tested-by: Jenkins
Reviewed-by: Tomaž Vajngerl
diff --git a/sw/CppunitTest_sw_apitests.mk b/sw/CppunitTest_sw_apitests.mk
index fb500fa990c5..93bc9453113e 100644
--- a/sw/CppunitTest_sw_apitests.mk
+++ b/sw/CppunitTest_sw_apitests.mk
@@ -37,6 +37,7 @@ $(eval $(call
gb_CppunitTest_add_exception_objects,sw_apitests, \
sw/qa/api/SwXReferenceMark \
sw/qa/api/SwXStyleFamilies \
sw/qa/api/SwXReferenceMarks \
+sw/qa/api/SwXTableCellText \
sw/qa/api/SwXTextFrame \
sw/qa/api/SwXTextField \
sw/qa/api/SwXTextTable \
diff --git a/sw/qa/api/SwXTableCellText.cxx b/sw/qa/api/SwXTableCellText.cxx
new file mode 100644
index ..733ba36415fd
--- /dev/null
+++ b/sw/qa/api/SwXTableCellText.cxx
@@ -0,0 +1,103 @@
+/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */
+/*
+ * This file is part of the LibreOffice project.
+ *
+ * This Source Code Form is subject to the terms of the Mozilla Public
+ * License, v. 2.0. If a copy of the MPL was not distributed with this
+ * file, You can obtain one at http://mozilla.org/MPL/2.0/.
+ */
+
+#include
+#include
+#include
+#include
+#include
+#include
+
+#include
+
+#include
+
+#include
+#include
+#include
+#include
+#include
+
+using namespace css;
+using namespace css::uno;
+
+namespace
+{
+/**
+ * Initial tests for SwXTableCellText.
+ */
+class SwXTableCellText final : public UnoApiTest,
+ public apitest::XEnumerationAccess,
+ public apitest::XElementAccess,
+ public apitest::XSimpleText,
+ public apitest::XTextRange,
+ public apitest::XText
+{
+public:
+SwXTableCellText()
+: UnoApiTest("")
+, XElementAccess(cppu::UnoType::get())
+{
+}
+
+virtual void setUp() override
+{
+UnoApiTest::setUp();
+mxDesktop.set(frame::Desktop::create(mxComponentContext));
+mxComponent = loadFromDesktop("private:factory/swriter");
+CPPUNIT_ASSERT(mxComponent.is());
+}
+
+Reference init() override
+{
+Reference xTextDocument(mxComponent,
UNO_QUERY_THROW);
+Reference xMSF(mxComponent,
UNO_QUERY_THROW);
+
+Reference xText = xTextDocument->getText();
+Reference xCursor = xText->createTextCursor();
+
+Reference
xTable(xMSF->createInstance("com.sun.star.text.TextTable"),
+ UNO_QUERY_THROW);
+xText->insertTextContent(xCursor, xTable, false);
+
+Reference xCell = xTable->getCellByName("A1");
+Reference xCellText(xCell, UNO_QUERY_THROW);
+xCellText->setString("SwXTableCellText");
+
+mxTextContent = Reference(
+xMSF->createInstance("com.sun.star.text.TextTable"),
UNO_QUERY_THROW);
+
+return Reference(xCellText->getText(), UNO_QUERY_THROW);
+}
+
+Reference getTextContent() override { return
mxTextContent; };
+
+CPPUNIT_TEST_SUITE(SwXTableCellText);
+CPPUNIT_TEST(testCreateEnumeration);
+CPPUNIT_TEST(testGetElementType);
+CPPUNIT_TEST(testHasElements);
+CPPUNIT_TEST(testCreateTextCursor);
+CPPUNIT_TEST(testCreateTextCursorByRange);
+CPPUNIT_TEST(testInsertString);
+CPPUNIT_TEST(testInsertControlCharacter);
+CPPUNIT_TEST(testGetEnd);
+CPPUNIT_TEST(testGetSetString);
+CPPUNIT_TEST(testGetStart);
+CPPUNIT_TEST(testGetText);
+CPPUNIT_TEST(testInsertRemoveTextContent);
+CPPUNIT_TEST_SUITE_END();
+
+private:
+Reference mxTextContent;
+};
+
+CPPUNIT_TEST_SUITE_REGISTRATION(SwXTableCellText);
+}
+
+/* vim:set shiftwidth=4 softtabstop=4 expandtab: */
[Libreoffice-commits] core.git: sw/CppunitTest_sw_apitests.mk sw/qa
sw/CppunitTest_sw_apitests.mk |1
sw/qa/api/SwXReferenceMarks.cxx | 120
2 files changed, 121 insertions(+)
New commits:
commit 88fe6dc44919b0a525e06bf0ac6e628b0f6c8a28
Author: anfanite396
AuthorDate: Thu Jul 6 11:06:42 2023 +0530
Commit: Tomaž Vajngerl
CommitDate: Mon Aug 14 21:06:38 2023 +0200
Move SwXReferenceMarks Java tests to C++
Change-Id: I3d825590e60190cf95f514b5df606a83ea4193b0
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/154086
Tested-by: Tomaž Vajngerl
Reviewed-by: Tomaž Vajngerl
diff --git a/sw/CppunitTest_sw_apitests.mk b/sw/CppunitTest_sw_apitests.mk
index ef7799763231..fb500fa990c5 100644
--- a/sw/CppunitTest_sw_apitests.mk
+++ b/sw/CppunitTest_sw_apitests.mk
@@ -36,6 +36,7 @@ $(eval $(call
gb_CppunitTest_add_exception_objects,sw_apitests, \
sw/qa/api/SwXParagraphEnumeration \
sw/qa/api/SwXReferenceMark \
sw/qa/api/SwXStyleFamilies \
+sw/qa/api/SwXReferenceMarks \
sw/qa/api/SwXTextFrame \
sw/qa/api/SwXTextField \
sw/qa/api/SwXTextTable \
diff --git a/sw/qa/api/SwXReferenceMarks.cxx b/sw/qa/api/SwXReferenceMarks.cxx
new file mode 100644
index ..699647f3e5e6
--- /dev/null
+++ b/sw/qa/api/SwXReferenceMarks.cxx
@@ -0,0 +1,120 @@
+/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */
+/*
+ * This file is part of the LibreOffice project.
+ *
+ * This Source Code Form is subject to the terms of the Mozilla Public
+ * License, v. 2.0. If a copy of the MPL was not distributed with this
+ * file, You can obtain one at http://mozilla.org/MPL/2.0/.
+ */
+
+#include
+#include
+#include
+#include
+#include
+
+#include
+
+#include
+
+#include
+#include
+#include
+#include
+
+#include
+
+using namespace css;
+using namespace css::uno;
+
+namespace
+{
+/**
+ * Initial tests for SwXReferenceMark.
+ */
+class SwXReferenceMark final : public test::BootstrapFixture,
+ public unotest::MacrosTest,
+ public apitest::XElementAccess,
+ public apitest::XIndexAccess,
+ public apitest::XNameAccess
+{
+public:
+SwXReferenceMark();
+virtual void setUp() override;
+void tearDown() override;
+
+Reference init() override;
+
+CPPUNIT_TEST_SUITE(SwXReferenceMark);
+CPPUNIT_TEST(testGetElementType);
+CPPUNIT_TEST(testHasElements);
+CPPUNIT_TEST(testGetCount);
+CPPUNIT_TEST(testGetByIndex);
+CPPUNIT_TEST(testGetByName);
+CPPUNIT_TEST(testGetElementNames);
+CPPUNIT_TEST(testHasByName);
+CPPUNIT_TEST_SUITE_END();
+
+private:
+Reference mxTextDocument;
+};
+
+SwXReferenceMark::SwXReferenceMark()
+: XElementAccess(cppu::UnoType::get())
+, XIndexAccess(2)
+, XNameAccess("SwXReferenceMark2")
+{
+}
+
+void SwXReferenceMark::setUp()
+{
+test::BootstrapFixture::setUp();
+
+mxDesktop.set(frame::Desktop::create(mxComponentContext));
+mxTextDocument = Reference(
+loadFromDesktop("private:factory/swriter",
"com.sun.star.text.TextDocument"),
+uno::UNO_QUERY_THROW);
+CPPUNIT_ASSERT(mxTextDocument.is());
+}
+
+void SwXReferenceMark::tearDown()
+{
+if (mxTextDocument.is())
+mxTextDocument->dispose();
+
+test::BootstrapFixture::tearDown();
+}
+
+Reference SwXReferenceMark::init()
+{
+Reference xMSF(mxTextDocument,
UNO_QUERY_THROW);
+
+Reference xText = mxTextDocument->getText();
+Reference xCursor = xText->createTextCursor();
+
+//RefMark 1
+Reference xRefMark1 =
xMSF->createInstance("com.sun.star.text.ReferenceMark");
+Reference xNamed1(xRefMark1, UNO_QUERY_THROW);
+xNamed1->setName("SwXReferenceMark1");
+
+Reference xTextContent1(xRefMark1, UNO_QUERY_THROW);
+xText->insertTextContent(xCursor, xTextContent1, false);
+
+//RefMark 2
+Reference xRefMark2 =
xMSF->createInstance("com.sun.star.text.ReferenceMark");
+Reference xNamed2(xRefMark2, UNO_QUERY_THROW);
+xNamed2->setName("SwXReferenceMark2");
+
+Reference xTextContent2(xRefMark2, UNO_QUERY_THROW);
+xText->insertTextContent(xCursor, xTextContent2, false);
+
+// Getting ReferenceMarks from Text Document
+Reference xRefMarkSupp(mxTextDocument,
UNO_QUERY_THROW);
+
+return Reference(xRefMarkSupp->getReferenceMarks(),
UNO_QUERY_THROW);
+}
+
+CPPUNIT_TEST_SUITE_REGISTRATION(SwXReferenceMark);
+}
+
+/* vim:set shiftwidth=4 softtabstop=4 expandtab: */
[Libreoffice-bugs] [Bug 156769] Special characters not appearing as autotext replacements
https://bugs.documentfoundation.org/show_bug.cgi?id=156769 --- Comment #2 from Anthony --- 1 You are correct and I misstated what I was experiencing. It is only after re-opening the autotext window to see the contents of this particular autotext function that I see that it's body is blank in the pane. 2 Good question but no, I did not forget. I do the "Autotext button -> New?" step, close the auto text window, type the autotext char+ F3 and nothing is inserted (to be super-clear, the character that is triggering the autotext is erased, and no text is inserted in it's place). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108252] [META] Cell-related bugs and enhancements (including formatting)
https://bugs.documentfoundation.org/show_bug.cgi?id=108252 BogdanB changed: What|Removed |Added Depends on||156735 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156735 [Bug 156735] Background color of loaded XLSX not shown -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156735] Background color of loaded XLSX not shown
https://bugs.documentfoundation.org/show_bug.cgi?id=156735 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||108252 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108252 [Bug 108252] [META] Cell-related bugs and enhancements (including formatting) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156419] Section within Linked Frames Will Not Continue Beyond Page
https://bugs.documentfoundation.org/show_bug.cgi?id=156419 raal changed: What|Removed |Added CC||michael.st...@allotropia.de ||, r...@post.cz Keywords|bibisectRequest |bibisected, bisected Regression By||Michael Stahl --- Comment #3 from raal --- This seems to have begun at the below commit in bibisect repository/OS linux-64-7.5. Adding Cc: to Michael Stahl ; Could you possibly take a look at this one? Thanks d43dce3389e86d41575cb744cd8527273ebd7554 is the first bad commit commit d43dce3389e86d41575cb744cd8527273ebd7554 Author: Jenkins Build User Date: Tue Jun 27 19:26:11 2023 +0200 source sha:425a252c3cc5e5a79a533965026dd4af6b8df739 151889: tdf#155324 sw: layout: try not to MoveFwd onto a page created by page break | https://gerrit.libreoffice.org/c/core/+/151889 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156771] New: Mail Merge create fails to include all lines with fields
https://bugs.documentfoundation.org/show_bug.cgi?id=156771 Bug ID: 156771 Summary: Mail Merge create fails to include all lines with fields Product: LibreOffice Version: 24.2.0.0 alpha0+ Master Hardware: x86 (IA32) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: erikf...@gmail.com Description: With 24.2.0.0.alpha0+ (X86_64) / Build ID: 256d5fe2e7cb1bb002d5fe59527d3a3fbf6963f Mail merge to a text file fails to include some lines, usually with fields that have no data (a blank cell in the db), also fails to include last line in field area. Also different results between merge to email vs merge to file. Previous versions (don't recall which ones) worked properly. Open Office writer works properly with same files. Steps to Reproduce: 1. Create db that has cells with no data 2. create .odt with lines that have cell description (title) and then field 3. Create email or create file, observe results with some missing lines. Actual Results: (Output From Libre Office Dev) Primary lease holder for the specific hangar: Thanks for your help in this project! Expected Results: (Output from Open Office Writer. Note 2 lines of text here missing from above) Primary lease holder for the specific hangar: Master Lease Holder (direct to TAA): Remarks: Thanks for your help in this project! Reproducible: Always User Profile Reset: Yes Additional Info: I believe this was working on earlier versions of the dev build, but I do not have records of which one. The old "open office" worked as expected. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156769] Special characters not appearing as autotext replacements
https://bugs.documentfoundation.org/show_bug.cgi?id=156769 --- Comment #1 from Mike Kaganski --- 1. Preview panel only shows a preview of already existing autotext entries. It could be reasonable to add a preview for a new (edited) entry - but possibly not easy, because it uses existing autotext *documents* IIRC, and there's no document (yet) for a new entry... 2. Did you forget to *add* the new entry, using Autotext button -> New? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'libreoffice-7-6' - sw/qa sw/source
sw/qa/core/objectpositioning/data/floattable-tbl-overlap.docx |binary
sw/qa/core/objectpositioning/objectpositioning.cxx | 33
++
sw/source/core/objectpositioning/tocntntanchoredobjectposition.cxx | 22
++
3 files changed, 55 insertions(+)
New commits:
commit c129a64adcd3d3be98d4eb136bceb53e72b3aff0
Author: Miklos Vajna
AuthorDate: Thu Aug 10 09:05:18 2023 +0200
Commit: Michael Stahl
CommitDate: Mon Aug 14 19:16:42 2023 +0200
sw floattable: handle AllowOverlap==false in the layout
The bugdoc has two floating tables, and these would normally overlap,
but SwFormatWrapInfluenceOnObjPos::mbAllowOverlap requests tweaking the
position at a layout level to avoid that overlap.
This is similar to what commit d37096f59e7e0286e55008153591a60bab92b9e8
(Related: tdf#124600 sw anchored object allow overlap: add layout,
2019-09-19) did, but that was for draw shapes and this is for split
flys.
Fix the problem by extending
SwToContentAnchoredObjectPosition::CalcOverlap(): the overlap detection
can be reused, just need to look for split flys on the entire page +
need to check split flys against other split flys.
The ODT filter works out of the box.
Change-Id: Id31308a67ba502bcc830f15a1679996ec153f209
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155536
Reviewed-by: Miklos Vajna
Tested-by: Jenkins
(cherry picked from commit 905962db870e9d1cf1dcf3bd1be44c347cddafe1)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155601
Reviewed-by: Michael Stahl
diff --git a/sw/qa/core/objectpositioning/data/floattable-tbl-overlap.docx
b/sw/qa/core/objectpositioning/data/floattable-tbl-overlap.docx
new file mode 100644
index ..b5b23931a240
Binary files /dev/null and
b/sw/qa/core/objectpositioning/data/floattable-tbl-overlap.docx differ
diff --git a/sw/qa/core/objectpositioning/objectpositioning.cxx
b/sw/qa/core/objectpositioning/objectpositioning.cxx
index bb3a12793ae8..4958b8b6deb4 100644
--- a/sw/qa/core/objectpositioning/objectpositioning.cxx
+++ b/sw/qa/core/objectpositioning/objectpositioning.cxx
@@ -15,6 +15,12 @@
#include
#include
#include
+#include
+#include
+#include
+#include
+#include
+#include
/// Covers sw/source/core/objectpositioning/ fixes.
class SwCoreObjectpositioningTest : public SwModelTestBase
@@ -280,6 +286,33 @@ CPPUNIT_TEST_FIXTURE(SwCoreObjectpositioningTest,
testVMLVertAlignBottomMargin)
CPPUNIT_ASSERT_EQUAL(static_cast(1), nFifthVMLShapeOutside -
nPageBottom);
}
+CPPUNIT_TEST_FIXTURE(SwCoreObjectpositioningTest,
testFloatingTableOverlapNever)
+{
+// Given a document with two floating tables, positioned in a way that
normally these would
+// overlap, but SwFormatWrapInfluenceOnObjPos::mbAllowOverlap == false
explicitly asks to avoid
+// overlaps:
+createSwDoc("floattable-tbl-overlap.docx");
+
+// When laying out that document:
+calcLayout();
+
+// Then make sure no overlap happens:
+SwDoc* pDoc = getSwDoc();
+SwRootFrame* pLayout = pDoc->getIDocumentLayoutAccess().GetCurrentLayout();
+auto pPage1 = dynamic_cast(pLayout->Lower());
+CPPUNIT_ASSERT(pPage1);
+CPPUNIT_ASSERT(pPage1->GetSortedObjs());
+const SwSortedObjs& rPage1Objs = *pPage1->GetSortedObjs();
+CPPUNIT_ASSERT_EQUAL(static_cast(2), rPage1Objs.size());
+auto pFlyFrame1 = rPage1Objs[0]->DynCastFlyFrame();
+auto pFlyFrame2 = rPage1Objs[1]->DynCastFlyFrame();
+// Without the accompanying fix in place, this test would have failed with:
+// - Expected greater than: 2291
+// - Actual : 2175
+// i.e. the 2nd floating table overlapped with the first one.
+CPPUNIT_ASSERT_GREATER(pFlyFrame1->getFrameArea().Bottom(),
pFlyFrame2->getFrameArea().Top());
+}
+
CPPUNIT_PLUGIN_IMPLEMENT();
/* vim:set shiftwidth=4 softtabstop=4 expandtab: */
diff --git a/sw/source/core/objectpositioning/tocntntanchoredobjectposition.cxx
b/sw/source/core/objectpositioning/tocntntanchoredobjectposition.cxx
index 9a9abc9f4dd8..33168ceba432 100644
--- a/sw/source/core/objectpositioning/tocntntanchoredobjectposition.cxx
+++ b/sw/source/core/objectpositioning/tocntntanchoredobjectposition.cxx
@@ -1194,6 +1194,21 @@ void
SwToContentAnchoredObjectPosition::CalcOverlap(const SwTextFrame* pAnchorFr
// Get the list of objects.
auto pSortedObjs = pAnchorFrameForVertPos->GetDrawObjs();
+
+bool bSplitFly = false;
+SwFlyFrame* pFlyFrame = GetAnchoredObj().DynCastFlyFrame();
+if (pFlyFrame && pFlyFrame->IsFlySplitAllowed())
+{
+// At least for split flys we need to consider objects on the same
page, but anchored in
+// different text frames.
+bSplitFly = true;
+const SwPageFrame* pPageFrame =
pAnchorFrameForVertPos->FindPageFrame();
+if (pPageFrame)
+{
+pSortedObjs = pPageFrame->GetSortedObjs();
+}
+}
+
[Libreoffice-bugs] [Bug 156768] No page number wizard found in LibreOffice Writer 7.6
https://bugs.documentfoundation.org/show_bug.cgi?id=156768 --- Comment #1 from Mike Kaganski --- My suspicion is that you have modified your menu, and that prevents it from showing changes introduced in later versions. Please test using safe mode - if it works then, then you might want to reset your user profile (and loose your customizations). This would be tdf#156743 then. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'libreoffice-7-6' - sw/qa sw/source
sw/qa/filter/ww8/ww8.cxx | 45 +++
sw/source/filter/ww8/docxtableexport.cxx |8 +
2 files changed, 53 insertions(+)
New commits:
commit 00203a05e84143b57170f75f5a9f57120bad24c6
Author: Miklos Vajna
AuthorDate: Fri Aug 11 08:27:32 2023 +0200
Commit: Michael Stahl
CommitDate: Mon Aug 14 19:14:17 2023 +0200
sw floattable: export to DOCX
Once split flys containing tables have "allow overlap" disabled, this is
not saved to DOCX when we map them to floating tables.
The working case is the allowOverlap attribute on shapes, added in
commit f8c7a2284b88c149addc8a30abb0cad8a10dad77 (Related: tdf#124600 sw
anchored object allow overlap: add DOCX filter, 2019-09-20).
Fix the problem by extending DocxAttributeOutput::TableDefinition(), to
write in case overlap is not allowed, after .
DOC and RTF filters are still missing.
Change-Id: I7d0bd4a15567014d3add8cbbcd92c62c5a33b7e4
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155573
Reviewed-by: Miklos Vajna
Tested-by: Jenkins
(cherry picked from commit 5af44a176d2a738dd7523713202aeee27c5578b6)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155603
Reviewed-by: Michael Stahl
diff --git a/sw/qa/filter/ww8/ww8.cxx b/sw/qa/filter/ww8/ww8.cxx
index 68bbc28fcfc3..2d12e980dbdb 100644
--- a/sw/qa/filter/ww8/ww8.cxx
+++ b/sw/qa/filter/ww8/ww8.cxx
@@ -27,6 +27,7 @@
#include
#include
#include
+#include
namespace
{
@@ -410,6 +411,50 @@ CPPUNIT_TEST_FIXTURE(Test, testFloattableThenFloattable)
// anchor.
CPPUNIT_ASSERT_EQUAL(nFly1Anchor + 1, nFly2Anchor);
}
+
+CPPUNIT_TEST_FIXTURE(Test, testFloattableOverlapNeverDOCXExport)
+{
+// Given a document with a floating table, overlap is not allowed:
+createSwDoc();
+SwDoc* pDoc = getSwDoc();
+SwWrtShell* pWrtShell = getSwDocShell()->GetWrtShell();
+pWrtShell->Insert2("before table");
+// Insert a table:
+SwInsertTableOptions aTableOptions(SwInsertTableFlags::DefaultBorder, 0);
+pWrtShell->InsertTable(aTableOptions, /*nRows=*/1, /*nCols=*/1);
+pWrtShell->MoveTable(GotoPrevTable, fnTableStart);
+// Select table:
+pWrtShell->SelAll();
+// Wrap the table in a text frame:
+SwFlyFrameAttrMgr aMgr(true, pWrtShell, Frmmgr_Type::TEXT, nullptr);
+pWrtShell->StartAllAction();
+aMgr.InsertFlyFrame(RndStdIds::FLY_AT_PARA, aMgr.GetPos(), aMgr.GetSize());
+pWrtShell->EndAllAction();
+// Allow the text frame to split:
+pWrtShell->StartAllAction();
+auto& rFlys = *pDoc->GetSpzFrameFormats();
+auto pFly = rFlys[0];
+SwAttrSet aSet(pFly->GetAttrSet());
+aSet.Put(SwFormatFlySplit(true));
+// Don't allow overlap:
+SwFormatWrapInfluenceOnObjPos aInfluence;
+aInfluence.SetAllowOverlap(false);
+aSet.Put(aInfluence);
+pDoc->SetAttr(aSet, *pFly);
+pWrtShell->EndAllAction();
+
+// When saving to DOCX:
+save("Office Open XML Text");
+
+// Then make sure that the overlap=never markup is written:
+xmlDocUniquePtr pXmlDoc = parseExport("word/document.xml");
+// Without the accompanying fix in place, this test would have failed with:
+// - Expected: 1
+// - Actual : 0
+// - XPath '//w:tblPr/w:tblOverlap' number of nodes is incorrect
+// i.e. was not written.
+assertXPath(pXmlDoc, "//w:tblPr/w:tblOverlap", "val", "never");
+}
}
CPPUNIT_PLUGIN_IMPLEMENT();
diff --git a/sw/source/filter/ww8/docxtableexport.cxx
b/sw/source/filter/ww8/docxtableexport.cxx
index 51fb3540c9df..b3e2d014222b 100644
--- a/sw/source/filter/ww8/docxtableexport.cxx
+++ b/sw/source/filter/ww8/docxtableexport.cxx
@@ -37,6 +37,7 @@
#include
#include
#include
+#include
#include "docxexportfilter.hxx"
#include "docxhelper.hxx"
@@ -281,6 +282,13 @@ void DocxAttributeOutput::TableDefinition(
bFloatingTableWritten = true;
// The outer table was floating, make sure potential inner tables are
not floating.
m_rExport.SetFloatingTableFrame(nullptr);
+
+const SwFrameFormat& rFloatingTableFormat =
pFloatingTableFrame->GetFrameFormat();
+if (!rFloatingTableFormat.GetWrapInfluenceOnObjPos().GetAllowOverlap())
+{
+// Allowing overlap is the default, both in OOXML and in Writer.
+m_pSerializer->singleElementNS(XML_w, XML_tblOverlap, FSNS(XML_w,
XML_val), "never");
+}
}
// Extract properties from grab bag
[Libreoffice-bugs] [Bug 145982] The Word Joiner feature mentioned in the 7.2 Writer Guide is missing
https://bugs.documentfoundation.org/show_bug.cgi?id=145982 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||6768 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156768] No page number wizard found in LibreOffice Writer 7.6
https://bugs.documentfoundation.org/show_bug.cgi?id=156768 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||5982 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156768] No page number wizard found in LibreOffice Writer 7.6
https://bugs.documentfoundation.org/show_bug.cgi?id=156768 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||6743 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156743] modified menu is branched from the master forever
https://bugs.documentfoundation.org/show_bug.cgi?id=156743 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||6768 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156770] Sidebar doesn't maintain its user fixed size for example after reload the document or the next time it opens.
https://bugs.documentfoundation.org/show_bug.cgi?id=156770 Davide changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156770] Sidebar doesn't maintain its user fixed size for example after reload the document or the next time it opens.
https://bugs.documentfoundation.org/show_bug.cgi?id=156770 Davide changed: What|Removed |Added Blocks||156767 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156767 [Bug 156767] [META] Technical Writer (EDITING) Suggested bug fixes, enhancements and features for technical writers. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156767] [META] Technical Writer (EDITING) Suggested bug fixes, enhancements and features for technical writers.
https://bugs.documentfoundation.org/show_bug.cgi?id=156767 Davide changed: What|Removed |Added Depends on||156770 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156770 [Bug 156770] Sidebar doesn't maintain its user fixed size for example after reload the document or the next time it opens. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156770] New: Sidebar doesn't maintain its user fixed size for example after reload the document or the next time it opens.
https://bugs.documentfoundation.org/show_bug.cgi?id=156770 Bug ID: 156770 Summary: Sidebar doesn't maintain its user fixed size for example after reload the document or the next time it opens. Product: LibreOffice Version: 7.4.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: davide.p...@gmail.com Description: Generally speaking, a window or toolbar should maintain its user fixed size. Regression from previous version of Writer Steps to Reproduce: 1- Choose >Navigator from side bar 2- Fix a width 3- Choose Styles in navigator bar 4- File > Reload Actual Results: Go back to Navigator: side bar is narrower than before Expected Results: The side bar width is the same fixed, even after closing and restarting LO Reproducible: Always User Profile Reset: No Additional Info: Suggestion: every application can have a different width of side bar as side bar may have different use according to the application in which it is used. Versione: 5.4.3.2 (x64) Build ID: 92a7159f7e4af62137622921e809f8546db437e5 Thread CPU: 8; SO: Windows 6.19; Resa interfaccia: predefinito; Versione locale: it-IT (it_IT); Calc: group -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113510] [META] Bugs that cause CPU to run at 100%
https://bugs.documentfoundation.org/show_bug.cgi?id=113510 Bug 113510 depends on bug 142694, which changed state. Bug 142694 Summary: Writer stops responding with busy CPU after opening this document https://bugs.documentfoundation.org/show_bug.cgi?id=142694 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142694] Writer stops responding with busy CPU after opening this document
https://bugs.documentfoundation.org/show_bug.cgi?id=142694 Michael Stahl (allotropia) changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |michael.st...@allotropia.de |desktop.org | Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Michael Stahl (allotropia) --- fixed on master -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156769] New: Special characters not appearing as autotext replacements
https://bugs.documentfoundation.org/show_bug.cgi?id=156769 Bug ID: 156769 Summary: Special characters not appearing as autotext replacements Product: LibreOffice Version: 7.5.5.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: congressman9...@gmail.com Description: Trying to create an autotext to insert "¿" in document. The character is not captured and does not appear in autotext preview pane and is not inserted when the autotext is triggered. Steps to Reproduce: 1. Insert "¿" in document 2. Highlight ¿ and press CTRL-F3 3. Autotext panel appears, but there is no character in the preview pane Actual Results: Autotext is saved but on playback no text is inserted Expected Results: I expected that the ¿ char would appear in the preview pane, be saved, and be inserted when autotext triggered Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.5.2 (X86_64) / LibreOffice Community Build ID: ca8fe7424262805f223b9a2334bc7181abbcbf5e CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156764] Tools>Language>For All Text hangs if multiple languages are involved
https://bugs.documentfoundation.org/show_bug.cgi?id=156764 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #2 from m.a.riosv --- Looks like a duplicate of https://bugs.documentfoundation.org/show_bug.cgi?id=156535 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153131] Copy causes Calc to Freeze on Windows 11
https://bugs.documentfoundation.org/show_bug.cgi?id=153131 --- Comment #34 from m.a.riosv --- BTW, there are a lot of resources about "Windows 11 Freezes Randomly", searching in the web. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156768] New: No page number wizard found in LibreOffice Writer 7.6
https://bugs.documentfoundation.org/show_bug.cgi?id=156768 Bug ID: 156768 Summary: No page number wizard found in LibreOffice Writer 7.6 Product: LibreOffice Version: 7.6.0.2 rc Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: vivada...@hotmail.com Description: According to the documentation, there should be a page number wizard in LibreOffice Writer 7.6, but it's not there. Steps to Reproduce: 1. Go to Insert > Page Number: there is no page number wizard. 2. Go to Insert > Field > Page Number: there is no page number wizard. Actual Results: A page number is simply added to the page. Expected Results: The should be a page number wizard to choose between different settings according to the documentation, in particular the release notes for LibreOffice 7.6: https://wiki.documentfoundation.org/ReleaseNotes/7.6 In LibreOffice Help, they mention a dialog, which I can't find: https://help.libreoffice.org/7.6/en-US/text/swriter/guide/pagenumbers.html Reproducible: Always User Profile Reset: No Additional Info: Version: 7.6.0.3 (X86_64) / LibreOffice Community Build ID: 69edd8b8ebc41d00b4de3915dc82f8f0fc3b6265 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: en-GB Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150980] calc cells loosing property
https://bugs.documentfoundation.org/show_bug.cgi?id=150980 Buovjaga changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
