[Libreoffice-bugs] [Bug 152458] Multi-Language support for spellchecker
https://bugs.documentfoundation.org/show_bug.cgi?id=152458 Mike Kaganski changed: What|Removed |Added See Also||https://bz.apache.org/ooo/s ||how_bug.cgi?id=69451 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 34694] [META] Improve usability of error messages
https://bugs.documentfoundation.org/show_bug.cgi?id=34694 BogdanB changed: What|Removed |Added Depends on||143771 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=143771 [Bug 143771] FILTER: FILESAVE: When xml export xsl transform file not found, error message is vague and misleading: "Error saving document" "General input/output error" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143771] FILTER: FILESAVE: When xml export xsl transform file not found, error message is vague and misleading: "Error saving document" "General input/output error"
https://bugs.documentfoundation.org/show_bug.cgi?id=143771 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||34694 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=34694 [Bug 34694] [META] Improve usability of error messages -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 42593] FILTER: ascii import does not recognize scientific numbers
https://bugs.documentfoundation.org/show_bug.cgi?id=42593 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||109239 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=109239 [Bug 109239] [META] CSV / TSV / Text Import and export / Text to Columns dialogs bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109239] [META] CSV / TSV / Text Import and export / Text to Columns dialogs bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109239 BogdanB changed: What|Removed |Added Depends on||42593 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=42593 [Bug 42593] FILTER: ascii import does not recognize scientific numbers -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102847] [META] Quick Find, Search and Replace
https://bugs.documentfoundation.org/show_bug.cgi?id=102847 BogdanB changed: What|Removed |Added Depends on||146142 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=146142 [Bug 146142] Automatic number formatting not undone after search and replace -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146142] Automatic number formatting not undone after search and replace
https://bugs.documentfoundation.org/show_bug.cgi?id=146142 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||102847, 108252 Hardware|x86-64 (AMD64) |All Component|LibreOffice |Calc Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102847 [Bug 102847] [META] Quick Find, Search and Replace 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 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||146142 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=146142 [Bug 146142] Automatic number formatting not undone after search and replace -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147110] Search in record not shown and not Cancel button
https://bugs.documentfoundation.org/show_bug.cgi?id=147110 BogdanB changed: What|Removed |Added Blocks||120062 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=120062 [Bug 120062] [META] Database related bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120062] [META] Database related bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=120062 BogdanB changed: What|Removed |Added Depends on||147110 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=147110 [Bug 147110] Search in record not shown and not Cancel button -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152388] Librecalc freezes when searching for non-existent text
https://bugs.documentfoundation.org/show_bug.cgi?id=152388 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||102847 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102847 [Bug 102847] [META] Quick Find, Search and Replace -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102847] [META] Quick Find, Search and Replace
https://bugs.documentfoundation.org/show_bug.cgi?id=102847 BogdanB changed: What|Removed |Added Depends on||152388 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152388 [Bug 152388] Librecalc freezes when searching for non-existent text -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155308] Dialog Record Search in Base forms: Wrong activated button "Help" instead of "Search"
https://bugs.documentfoundation.org/show_bug.cgi?id=155308 BogdanB changed: What|Removed |Added Blocks||120062 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=120062 [Bug 120062] [META] Database related bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120062] [META] Database related bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=120062 BogdanB changed: What|Removed |Added Depends on||155308 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=155308 [Bug 155308] Dialog Record Search in Base forms: Wrong activated button "Help" instead of "Search" -- 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 BogdanB changed: What|Removed |Added Depends on||149158 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=149158 [Bug 149158] Laserpointer of KDE connect not visible on Impress slide -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149158] Laserpointer of KDE connect not visible on Impress slide
https://bugs.documentfoundation.org/show_bug.cgi?id=149158 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||103610 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103610 [Bug 103610] [META] Slide show (presentation mode) bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147247] Grouped animated GIFs no display correctly during presentations
https://bugs.documentfoundation.org/show_bug.cgi?id=147247 BogdanB changed: What|Removed |Added Blocks||103610 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103610 [Bug 103610] [META] Slide show (presentation mode) bugs and enhancements -- 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 BogdanB changed: What|Removed |Added Depends on||147247 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=147247 [Bug 147247] Grouped animated GIFs no display correctly during presentations -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157361] Pasting hyperlink from MS Word to Impress does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=157361 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 157363] Pasting hyperlink from PowerPoint to Impress does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=157363 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 157606] Libreoffice Calc does not advertise Biff formats for paste
https://bugs.documentfoundation.org/show_bug.cgi?id=157606 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157332] EDITING: Cannot save a Page Style correctly in a template
https://bugs.documentfoundation.org/show_bug.cgi?id=157332 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 157332] EDITING: Cannot save a Page Style correctly in a template
https://bugs.documentfoundation.org/show_bug.cgi?id=157332 --- Comment #9 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154030] Data Entered into Forms does not print
https://bugs.documentfoundation.org/show_bug.cgi?id=154030 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157606] Libreoffice Calc does not advertise Biff formats for paste
https://bugs.documentfoundation.org/show_bug.cgi?id=157606 --- Comment #9 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154022] Libre office Draw my paragraph alignment sometimes works
https://bugs.documentfoundation.org/show_bug.cgi?id=154022 --- Comment #3 from QA Administrators --- Dear jake_mason, 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 154030] Data Entered into Forms does not print
https://bugs.documentfoundation.org/show_bug.cgi?id=154030 --- Comment #5 from QA Administrators --- Dear Shawn Burton, 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 154028] Difficult to change the language of everything in the document
https://bugs.documentfoundation.org/show_bug.cgi?id=154028 --- Comment #3 from QA Administrators --- Dear Eyal Rozenberg, 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 154500] we couldn't go to default text after changed text background...
https://bugs.documentfoundation.org/show_bug.cgi?id=154500 --- Comment #2 from QA Administrators --- Dear Prabakaran Rengasamy, 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 86529] Text in a Shape with added Text Box does not rotate with Shape in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=86529 --- Comment #20 from QA Administrators --- Dear ungifted, 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 84311] Impress Remote Control for iOS does not connect
https://bugs.documentfoundation.org/show_bug.cgi?id=84311 --- Comment #13 from QA Administrators --- Dear Marc Balmer, 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 83536] Exports fixed with tables to HTML even when size is relative.
https://bugs.documentfoundation.org/show_bug.cgi?id=83536 --- Comment #7 from QA Administrators --- Dear dE, 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 67272] VIEWING Paragraph border on front of image but paragraph background color is at the back
https://bugs.documentfoundation.org/show_bug.cgi?id=67272 --- Comment #13 from QA Administrators --- Dear Arnaud Versini, 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 59952] EDITING: Original (Sub-)Title text box can not be grouped with other elements
https://bugs.documentfoundation.org/show_bug.cgi?id=59952 --- Comment #10 from QA Administrators --- Dear bugquestcontri, 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 50743] FORMATTING: Highlighting scrolls automatically
https://bugs.documentfoundation.org/show_bug.cgi?id=50743 --- Comment #17 from QA Administrators --- Dear tomcb, 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 144622] FORMATTING MARKS: Non-breaking space not honored between text and non-text object
https://bugs.documentfoundation.org/show_bug.cgi?id=144622 --- Comment #2 from QA Administrators --- Dear Andre, 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 144830] EDITING No list operation on an ordered/unordered list is not recorded as tracked change
https://bugs.documentfoundation.org/show_bug.cgi?id=144830 --- Comment #4 from QA Administrators --- Dear NISZ LibreOffice Team, 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 121358] UI: Character dialog highlighting color is set to blue by default (not yellow)
https://bugs.documentfoundation.org/show_bug.cgi?id=121358 --- 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 125705] Impossible to edit any TextField (except URL) inside a spreadsheet cell by user code.
https://bugs.documentfoundation.org/show_bug.cgi?id=125705 --- Comment #9 from QA Administrators --- Dear Wolfgang Jäger, 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 120505] Table loses relative setting after moving the inner border depending on zoomfactor (100% fails)
https://bugs.documentfoundation.org/show_bug.cgi?id=120505 --- Comment #17 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 107962] Styles and Formatting deck's controls should all be disabled when inserting/selecting/editing a textbox
https://bugs.documentfoundation.org/show_bug.cgi?id=107962 --- Comment #6 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 157615] Marking parts of text with the mouse does not work any longer reliably
https://bugs.documentfoundation.org/show_bug.cgi?id=157615 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org --- Comment #3 from V Stuart Foote --- Can not confirm. A partial word, or multi-word, selection with l-mouse click-n-drag holds its mark after release. Likewise mark is held with a full word with a 'double click'. Perhaps a hardware issue with the mouse? =-testing-= Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 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 157606] Libreoffice Calc does not advertise Biff formats for paste
https://bugs.documentfoundation.org/show_bug.cgi?id=157606 --- Comment #8 from Andrew Lentvorski --- (In reply to Mike Kaganski from comment #7) > 1. There is no problem *generally* with Biff *paste* into LibreOffice - at > least on Windows, as shown in tdf#127675 - only Biff12 support is missing, > which is an easyhack there. > 2. You issue seemed to me initially a duplicate of tdf#124006 - because the > underlying issue looked the same. However, that one was for Windows, and bug > 124006 comment 1 directly told it working for Linux - but that must mean, > that there *is* a clipboard format on Linux, that different apps may use to > transfer formulas. Needs investigation. I opened two different LO instances and pasted between them. Consequently, I can confirm that "application/x-openoffice-embed-source-xml;windows_formatname="Star Embed Source (XML)" appears to transmit formulas. I did not realize that this was xml in a zip archive and so only scanned it directly. Once I unpacked the archive, I could see the formulas. I can make personal progress doing what I need to do on Linux even though it's going to be a lot more work. As such, the severity can be downgraded or the bug closed at your discretion. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: external/skia
external/skia/UnpackedTarball_skia.mk|1 - external/skia/clang11-flax-vector-conversion.patch.0 | 11 --- 2 files changed, 12 deletions(-) New commits: commit 06b7a31cbe971470b5551044efc6c977b44bc312 Author: Taichi Haradaguchi <20001...@ymail.ne.jp> AuthorDate: Mon Oct 2 20:45:31 2023 +0900 Commit: Taichi Haradaguchi <20001...@ymail.ne.jp> CommitDate: Fri Oct 6 02:44:39 2023 +0200 Drop some patches for old Clang There are no longer needed after 6ef2d358ac053ce0f6de9cf0f8f25e8bae66d441 "Adapt Clang and GCC minimum version checks" Change-Id: Id428e2d50a120fe65738e7ba019c4f2c22095f48 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/157491 Tested-by: Jenkins Reviewed-by: Taichi Haradaguchi <20001...@ymail.ne.jp> diff --git a/external/skia/UnpackedTarball_skia.mk b/external/skia/UnpackedTarball_skia.mk index b931aefd8618..ae90f26fe15b 100644 --- a/external/skia/UnpackedTarball_skia.mk +++ b/external/skia/UnpackedTarball_skia.mk @@ -18,7 +18,6 @@ skia_patches := \ no-trace-resources-on-exit.patch.1 \ fix-alpha-difference-copy.patch.1 \ share-grcontext.patch.1 \ -clang11-flax-vector-conversion.patch.0 \ clang-attributes-warning.patch.1 \ fontconfig-get-typeface.patch.0 \ windows-do-not-modify-logfont.patch.0 \ diff --git a/external/skia/clang11-flax-vector-conversion.patch.0 b/external/skia/clang11-flax-vector-conversion.patch.0 deleted file mode 100644 index aebe66c907d6.. --- a/external/skia/clang11-flax-vector-conversion.patch.0 +++ /dev/null @@ -1,11 +0,0 @@ src/opts/SkRasterPipeline_opts.h -+++ src/opts/SkRasterPipeline_opts.h -@@ -43,7 +43,7 @@ - - using NoCtx = const void*; - --#if !defined(__clang__) -+#if !defined(__clang__) || __clang_major__ >= 11 - #define JUMPER_IS_SCALAR - #elif defined(SK_ARM_HAS_NEON) - #define JUMPER_IS_NEON
[Libreoffice-bugs] [Bug 154996] Help pages about dialogs should provide instructions for the Tabbed UI
https://bugs.documentfoundation.org/show_bug.cgi?id=154996 --- Comment #23 from Commit Notification --- Olivier Hallot committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/help/commit/e09f381a645a2731e38bfff4a573ee25ccd488b7 tdf#154996 Update tools - macro UI help pages -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 240b37e04a5c797b2be79cf9f592b2d19802161a Author: Olivier Hallot AuthorDate: Thu Oct 5 21:21:22 2023 -0300 Commit: Gerrit Code Review CommitDate: Fri Oct 6 02:21:22 2023 +0200 Update git submodules * Update helpcontent2 from branch 'master' to e09f381a645a2731e38bfff4a573ee25ccd488b7 - tdf#154996 Update tools - macro UI help pages Change-Id: Ic3dd6f3b000bc7ef743c1fc2d055a4dbf5ad90cb Reviewed-on: https://gerrit.libreoffice.org/c/help/+/157609 Tested-by: Jenkins Reviewed-by: Olivier Hallot diff --git a/helpcontent2 b/helpcontent2 index 0f8471655a2b..e09f381a645a 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit 0f8471655a2bcd1616579672c3fd5a2ab26861d9 +Subproject commit e09f381a645a2731e38bfff4a573ee25ccd488b7
[Libreoffice-commits] help.git: source/text
source/text/sbasic/shared/0105.xhp | 54 --- source/text/shared/00/0406.xhp | 53 +-- source/text/shared/01/0613.xhp | 58 ++--- source/text/shared/01/06130001.xhp | 25 + source/text/shared/01/06130010.xhp | 11 ++-- source/text/shared/01/06130020.xhp | 26 - source/text/shared/01/06130030.xhp | 42 --- source/text/shared/01/06130200.xhp | 26 - source/text/shared/01/06130300.xhp | 77 ++-- source/text/shared/01/digitalsignatures.xhp |7 +- 10 files changed, 225 insertions(+), 154 deletions(-) New commits: commit e09f381a645a2731e38bfff4a573ee25ccd488b7 Author: Olivier Hallot AuthorDate: Thu Oct 5 21:19:39 2023 -0300 Commit: Olivier Hallot CommitDate: Fri Oct 6 02:21:22 2023 +0200 tdf#154996 Update tools - macro UI help pages Change-Id: Ic3dd6f3b000bc7ef743c1fc2d055a4dbf5ad90cb Reviewed-on: https://gerrit.libreoffice.org/c/help/+/157609 Tested-by: Jenkins Reviewed-by: Olivier Hallot diff --git a/source/text/sbasic/shared/0105.xhp b/source/text/sbasic/shared/0105.xhp index 1a0383531e..136c1ab2aa 100644 --- a/source/text/sbasic/shared/0105.xhp +++ b/source/text/sbasic/shared/0105.xhp @@ -1,6 +1,4 @@ - - - -$[officename] Basic IDE +$[officename] Basic IDE /text/sbasic/shared/0105.xhp @@ -30,12 +27,29 @@ + -$[officename] Basic IDE - -This section describes the structure of the Basic IDE. - -Opens the Basic IDE where you can write and edit macros. +$[officename] Basic IDE +Opens the Basic IDE where you can write and edit BASIC macros. +This section describes the structure of the Basic IDE. + + + +Choose Tools - Macro - Edit Macro. + +Choose Tools - Basic. +On the Tools menu of the Tools tab, choose Edit Macro. + + + + +Icon Edit Macro + + +Edit Macro + + + @@ -44,22 +58,22 @@ Commands From the Context menu of the Module Tabs Insert - + Module -Inserts a new module into the current library. - +Inserts a new module into the current library. + Dialog -Inserts a new dialog into the current library. - +Inserts a new dialog into the current library. + Delete -Deletes the selected module. - +Deletes the selected module. + Rename -Renames the current module in place. - +Renames the current module in place. + Hide -Hides the current module. +Hides the current module. Modules -Opens the Macro Organizer dialog. +Opens the Macro Organizer dialog. diff --git a/source/text/shared/00/0406.xhp b/source/text/shared/00/0406.xhp index 124df46484..4c428e9e97 100644 --- a/source/text/shared/00/0406.xhp +++ b/source/text/shared/00/0406.xhp @@ -124,15 +124,60 @@ Choose Tools - Media Player. Choose Tools - Macros - Organize Macros - Basic, or press OptionAlt+F11 (if not assigned by your system). -Choose Tools - Macros - Run Macro. -Choose Tools - Macros - Organize Macros - BeanShell. -Choose Tools - Macros - Organize Macros - JavaScript. -Choose Tools - Macros - Organize Macros - Python. + + + +Choose Tools - Macros - Run Macro. + +Choose Tools - Run Macro. +On the Tools menu of the Tools tab, choose Run Macro. + + + + +Icon Run Macro + + +Run Macro + + + + + + + +Choose Tools - Macros - Organize Macros - BeanShell/Javascript/Python. + +On the Tools menu of the Tools tab, choose Javascript/Beanshell/Python. + + + Choose Tools - Macros - Record Macro. + +On the Tools menu of the Tools tab, choose Record Macro. + + + + +Icon Record Macro + + +Record Macro + + + + Choose Tools - Macros - Organize Macros - Basic,click the Organizer button,click the Libraries tab,and then click the Password button. + + + Choose Tools - Macros - Organize Macros - Basic,click the Organizer button. + + + + Choose Tools - Extensions. Choose Tools - Extensions, click Check for Updates button. Choose Tools - Macros - XML Filter Settings. diff --git a/source/text/shared/01/0613.xhp b/source/text/shared/01/0613.xhp index 492e9b6061..e97174120a 100644 --- a/source/text/shared/01/0613.xhp +++ b/source/text/shared/01/0613.xhp @@ -18,57 +18,55 @@ * except in compliance with the License. You may obtain a copy of * the License at
[Libreoffice-bugs] [Bug 144553] JPG and PNG and GIF get corrupted to zero size on export if resaved under the same name
https://bugs.documentfoundation.org/show_bug.cgi?id=144553 --- Comment #8 from Daniel Baran --- Adding: I'm seeing the same behavior in the following versions as well. Export to a new filename, the file is good. Export to the same filename the file is zero bytes. Version: 7.5.7.1 (X86_64) / LibreOffice Community Build ID: 47eb0cf7efbacdee9b19ae25d6752381ede23126 CPU threads: 12; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 12; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; 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.
[Libreoffice-bugs] [Bug 157332] EDITING: Cannot save a Page Style correctly in a template
https://bugs.documentfoundation.org/show_bug.cgi?id=157332 --- Comment #8 from dlp...@gmail.com --- Created attachment 190054 --> https://bugs.documentfoundation.org/attachment.cgi?id=190054=edit TestMyLeft Page.odt file and the description Let me explain the bug again in clearer terms: Cannot save PageStyle correctly: Version test (7.6.1.2 on Windows 10) I create MyLeft Page Style in document TestMyLeft Page with these values: Left: 1.27cm Right: 1.27cm Option: Gutter on right side of page After saving TestMyLeft Page, I close the file and then open it up again. When I check MyLeft Page Page Style, the margin values for Left, Right are changed to new values, and the option I choose for Gutter on the right is switched off. After saving the Left, Right Margin become new value: Left: 0.00cm Right: 3.51cm Option: Gutter on right side of page (switched off) In other words, I can not save the Page Style with the original values: Left: 1.27cm Right: 1.27cm Option: Gutter on right side of page. Please create the problem by opening the file containing the Page Style MyLeft Page, change the values for Left, Right margins and change the Option to Gutter on the right as shown. Save the file and open it again to see the values changed as shown. Please see attached file CannotSavePageStyleCorrectly.zip -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157332] EDITING: Cannot save a Page Style correctly in a template
https://bugs.documentfoundation.org/show_bug.cgi?id=157332 --- Comment #7 from dlp...@gmail.com --- Let me explain the bug again in clearer terms: Cannot save PageStyle correctly: Version test (7.6.1.2 on Windows 10) I create MyLeft Page Style in document TestMyLeft Page with these values: Left: 1.27cm Right: 1.27cm Option: Gutter on right side of page After saving TestMyLeft Page, I close the file and then open it up again. When I check MyLeft Page Page Style, the margin values for Left, Right are changed to new values, and the option I choose for Gutter on the right is switched off. After saving the Left, Right Margin become new value: Left: 0.00cm Right: 3.51cm Option: Gutter on right side of page (switched off) In other words, I can not save the Page Style with the original values: Left: 1.27cm Right: 1.27cm Option: Gutter on right side of page. Please create the problem by opening the file containing the Page Style MyLeft Page, change the values for Left, Right margins and change the Option to Gutter on the right as shown. Save the file and open it again to see the values changed as shown. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157618] FILESAVE: Calc ignores directly formatted text color in .ods files
https://bugs.documentfoundation.org/show_bug.cgi?id=157618
--- Comment #5 from Patrick Luby ---
Note for myself: I found that the cell's ATTR_BACKGROUND gets set differently
depending on whether you are opening the .ods or the .xlsx files attached to
this bug.
Next step: find where ATTR_BACKGROUND is set during loading of the document:
diff --git a/sc/source/core/data/patattr.cxx b/sc/source/core/data/patattr.cxx
index 7638652e6857..87383ec29398 100644
--- a/sc/source/core/data/patattr.cxx
+++ b/sc/source/core/data/patattr.cxx
@@ -472,6 +472,10 @@ void ScPatternAttr::fillColor(model::ComplexColor&
rComplexColor, const SfxItemS
}
else
{
+// tdf#157618 when opening the .ods file, ATTR_BACKGROUND is set
+// to the Error style's red background color whereas opening the
+// .xlsx file, ATTR_BACKGROUND is set to the cell's directly
+// formatted transparent background color.
aBackColor = rItemSet.Get(ATTR_BACKGROUND).GetColor();
}
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157625] New: Tools - Macro - Organize Macro has no Help ID
https://bugs.documentfoundation.org/show_bug.cgi?id=157625 Bug ID: 157625 Summary: Tools - Macro - Organize Macro has no Help ID Product: LibreOffice Version: 24.2.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Documentation Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: olivier.hal...@libreoffice.org CC: olivier.hal...@libreoffice.org Blocks: 120201 Press F1 in Tools - Macro - Organize Macro and the help page indicates Help ID: .help:index The target page is text/shared/01/06130200.xhp Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=120201 [Bug 120201] [META] Update or add link to help page -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120201] [META] Update or add link to help page
https://bugs.documentfoundation.org/show_bug.cgi?id=120201 Olivier Hallot changed: What|Removed |Added Depends on||157625 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=157625 [Bug 157625] Tools - Macro - Organize Macro has no Help ID -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144553] JPG and PNG and GIF get corrupted to zero size on export if resaved under the same name
https://bugs.documentfoundation.org/show_bug.cgi?id=144553 --- Comment #7 from Daniel Baran --- Per QA Team request: Using the version below, I still see the same behavior. If I export to a new filename, the file is good. If I export to the same filename the file is zero bytes. Hope this helps. Version: 7.5.6.2 (X86_64) / LibreOffice Community Build ID: f654817fb68d6d4600d7d2f6b647e47729f55f15 CPU threads: 12; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; 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.
[Libreoffice-bugs] [Bug 157447] Calc does not preserve cell padding on other undo operations
https://bugs.documentfoundation.org/show_bug.cgi?id=157447 --- Comment #6 from Kira Tubo --- Created attachment 190053 --> https://bugs.documentfoundation.org/attachment.cgi?id=190053=edit XLSX file with cell padding 1. Open attached XLSX file 2. Note that padding is visibly set to 10pt 3. Right click > Format Cells 4. Padding is set to default 1.0pt (NOT expected) 5. Click OK 6. Padding visibly reset to default Expected: Cell padding settings should be retained in XLSX file Actual: Saved cell padding settings are not retained in XLSX file. Visibly, the cell padding looks like it is saved, but in the Format Cells menu, cell padding is at default. It would be good if others can confirm the above steps. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157447] Calc does not preserve cell padding on other undo operations
https://bugs.documentfoundation.org/show_bug.cgi?id=157447 --- Comment #5 from Kira Tubo --- Created attachment 190052 --> https://bugs.documentfoundation.org/attachment.cgi?id=190052=edit Cell padding XLSX upon opening file screenshot (In reply to Murugavel from comment #4) > The file was saved in xlsx format. Sorry, I missed mentioning it earlier. Thanks for confirming. I think the XLSX format is causing the problem. Interestingly enough, if you check on the cell format when you open the XLSX file (BEFORE typing or undoing the text), the padding is already set to default 1.0 pt for me (as shown in attachment). I checked the ODS file, and the padding is saved in the Format Cell dialog. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157624] New: tkinter Missing From LibreOffice Python Interpreter
https://bugs.documentfoundation.org/show_bug.cgi?id=157624 Bug ID: 157624 Summary: tkinter Missing From LibreOffice Python Interpreter Product: LibreOffice Version: 7.6.1.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tomekl...@gmail.com Description: tkinter works beautifully under LibreOffice. It can be used in Linux without any problem (Linux LibreOffice uses system Python interpreter if LibreOffice is installed using packaging system like deb/rpm). But on Windows, Mac and LibreOffice installed in Linux using e.g. flatpak, LibreOffice has its own Python interpreter packaged. This interpreter is missing tkinter. Other Python packages can be added using pip but not tkinter. If tkinter is not a part of a Python interpreter, there is no way to add it later. Steps to Reproduce: 1. there is no way to add tkinter to LibreOffice Python interpreter Actual Results: tkinter works nicely but can not be added Expected Results: tkinter should be the default part of the packaged Python interpreter Reproducible: Always User Profile Reset: No Additional Info: It is very sad that there are very limited possibilities regarding GUI frameworks in Python in LibreOffice. Only UNO dialogs really work. Under Linux, tkinter works without problems but it can not be used on Windows/Mac/Linux with LO installed using flatpak. Also PyQT and PySide actually work very nicely! But after closing a PyQT window, LibreOffice always crashes (new versions of LO. In older versions of LO, PyQT/PySide just worked). Many other GUI frameworks do not work under LibreOffice (I tested Dear PyGUI, Toga, PySimpleGUI, wxPython, Kivy, Pywebview). It is interesting that many of them actually work but only after closing a window, the whole LibreOffice freezes or crashes or the window can not be closed (destroy method does not work). So, there are really no options, just UNO dialog windows and forms which are unknown to almost all Pythonists. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157623] New: Log Text Marker
https://bugs.documentfoundation.org/show_bug.cgi?id=157623 Bug ID: 157623 Summary: Log Text Marker Product: LibreOffice Version: 7.5.7.1 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jon.nico...@wanadoo.fr Hello I have the same problem again when I use Text Cue, the buggy application. Pages move from top to bottom for several seconds before the feature appears. The issue also appears in Safe Mode, but does not appear in a blank document and plain text. The problem is absent when using the OpenOffice writer software. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 34391] FORMATTING: Introduce table cell styles
https://bugs.documentfoundation.org/show_bug.cgi?id=34391 --- Comment #31 from João Pedro --- With each new release I have the hope that this bug will be fixed, because it's a shame such a good software has this problem. Since I use a lot of tables in my job, this is becoming difficult. It's like having a Ferrari (because LibreOffice is like a Ferrari) and every time I use third gear the engine stops working and I have to restart everything again. I understand that LibreOffice is free software, that there is no commercial team developing the system, but in my job I use a lot of tables and I am no longer having time to reformat the tables every time I need to add or delete data. This comment of mine is an attempt to continue using LibreOffice. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157365] Options > LibreOffice Writer changes page color scheme from Dark to Light
https://bugs.documentfoundation.org/show_bug.cgi?id=157365 Kira Tubo changed: What|Removed |Added CC||parisop...@gmail.com Keywords|bibisectRequest |bibisected, bisected --- Comment #3 from Kira Tubo --- Bibisected win64-7.6. Looks like the issue started at this commit: https://git.libreoffice.org/core/+/1916d161902bdd52b8cfa5b29153c8f8c39fce52 Adding Paris Oplopoios to cc. @Paris, here are simplified steps from Comment 2: >1. Go to Tools > Options > LibreOffice > Application Colours >2. Change scheme to "Dark" (document background automatically goes dark even >without pressing "Apply") >3. Open any page within LibreOffice Writer (e.g. General, View, Formatting >Aids, etc.) >4. Click OK - commit 1916d161902bdd52b8cfa5b29153c8f8c39fce52[log] author Paris Oplopoios Wed Mar 08 17:34:02 2023 +0200 committer Miklos Vajna Thu Mar 16 08:41:38 2023 + treefdb789357ef4e58e3f26066235b5928efcf63437 parent ee8e9b993595e728f827a5fe6ab1ae5fb1f6aaae [diff] -- commit fe420d4fcd358840a2e45b4985a69f92794b9b55 Author: Norbert Thiebaud Date: Thu Mar 16 03:26:24 2023 -0700 source sha:1916d161902bdd52b8cfa5b29153c8f8c39fce52 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157622] Fichiers partagés verrouillés à la version 7.5.7.1
https://bugs.documentfoundation.org/show_bug.cgi?id=157622 valenti...@live.fr changed: What|Removed |Added Hardware|Other |x86-64 (AMD64) Version|7.6.0.1 rc |7.5.7.1 release Component|Android Editor |LibreOffice OS|other |Windows (All) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157622] New: Fichiers partagés verrouillés à la version 7.5.7.1
https://bugs.documentfoundation.org/show_bug.cgi?id=157622 Bug ID: 157622 Summary: Fichiers partagés verrouillés à la version 7.5.7.1 Product: LibreOffice Version: 7.6.0.1 rc Hardware: Other OS: other Status: UNCONFIRMED Severity: normal Priority: medium Component: Android Editor Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: valenti...@live.fr Description: Bonjour, Après être passé de la V 7.5.6 à la V 7.5.7 tous mes fichiers partagés libre office uniquement affichent systématiquement un pop-up "ce fichier a été verrouillé par un autre utilisateur". J'ai vérifié auprès de la personne en partage, son PC est correctement éteint. La réparation puis la désinstallation/réinstallation de la 7.5.7 n'ont rien réparé. J'ai du réinstaller la V 7.5.6 pour que tout rentre dans l'ordre. Je suis sur PC Win10. A noter que le partage de fichier est réalisé à partir de Google Drive. Ce bug arrive à chaque fois sur la version 7.5.7. En espérant avoir été clair. Félicitations pour tout ce que vous faites !!! Cordialement. Steps to Reproduce: 1.Effectuer sur le gestionnaire de fichier un partage des fichiers via Google Drive sous la version 7.5.6 2.installer (mettre à jour) la version 7.5.7 3.ouvrir un fichier partagés 4.Seuls les fichiers Libre Office refusent de s'ouvrir "ce fichier a été verrouillé par un autre utilisateur". Les autres fichiers partagés s'ouvrent normalement. Actual Results: pop-up "ce fichier a été verrouillé par un autre utilisateur" Expected Results: ouverture du fichier Reproducible: Always User Profile Reset: No Additional Info: Seul le retour à la version précédent 7.5.6 a permis de solutionner le problème. Le bug concerne la version 7.5.7 (cadre "Version:" non compris !!) rejet du formulaire lorsque j'indique 7.5.7.1...??? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157621] New: dialog.dtd Is Outdated or Incomplete
https://bugs.documentfoundation.org/show_bug.cgi?id=157621 Bug ID: 157621 Summary: dialog.dtd Is Outdated or Incomplete Product: LibreOffice Version: 7.6.1.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tomekl...@gmail.com Description: dialog.dtd and other dtd files (documentation: https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Library_File_Structure) are XML specifications. But for example dialog.dtd (not sure about other DTD files) is incomplete or maybe outdated. Steps to Reproduce: 1. Tools > Macros > Dialog windows 2. Create any dialog window, for example with some radio buttons or other elements. 3. Export the window to XDL (there is a button for that, see the upper toolbars). 4. Open the XDL in IDE (IDE must be set up, so it can read DTD specifications of XML files and validate XMLs against DTD) (I use VS Code, see https://github.com/redhat-developer/vscode-xml/blob/main/docs/Validation.md) 5. find dialog.dtd on your system (where in LibreOffice it is placed? See: https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Library_File_Structure) 6. place the dialog.dtd in the same folder as your XDL dialog. 7. As you see, IDE validates many XML tags against DTD just right. But some tags are missing. These are not defined in DTD. For example: dlg:radio > dlg:group-name. dlg:text-field > dlg:valign. These are tags that are missing from dialog.dtd, so we can see that dialog.dtd is incomplete or maybe outdated. Actual Results: XML tag definitions missing from DTD file. Expected Results: In DTD file all used XML tags should be defined. Reproducible: Always User Profile Reset: No Additional Info: - -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157620] New: Wrong Links in XDL Exported Dialog File
https://bugs.documentfoundation.org/show_bug.cgi?id=157620 Bug ID: 157620 Summary: Wrong Links in XDL Exported Dialog File Product: LibreOffice Version: 7.6.1.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tomekl...@gmail.com Description: When we export a dialog to XDL file, inside there are wrong old links http://openoffice.org/2000/dialog and http://openoffice.org/2000/script. Steps to Reproduce: 1. Tools > Macros > Dialog Windows 2. Create a dialog window. 3. Export the window to XDL (there is a button for this, in upper toolbars). 4. open the XDL in any editing tool, check the links Actual Results: http://openoffice.org/2000/dialog and http://openoffice.org/2000/script Expected Results: Up-to-date working links. Reproducible: Always User Profile Reset: No Additional Info: - -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129288] Main menu entries: Shape or Shapes, Sheet or Sheets, Form or Forms?
https://bugs.documentfoundation.org/show_bug.cgi?id=129288 --- Comment #9 from Adolfo Jayme Barrientos --- TBH, I don't think this is a helpful change when balancing the work needed to rework translated strings with accelerators vs. the degree of clarity that it brings (I mean, I believe the strings are clear enough already in this particular case). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157365] Options > LibreOffice Writer changes page color scheme from Dark to Light
https://bugs.documentfoundation.org/show_bug.cgi?id=157365 Kira Tubo changed: What|Removed |Added Summary|Changing default fonts |Options > LibreOffice |forces page color to|Writer changes page color |display as white, in dark |scheme from Dark to Light |mode| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107805] [META] Writer master document issues
https://bugs.documentfoundation.org/show_bug.cgi?id=107805 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||157342 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=157342 [Bug 157342] Delete menu item in Master Navigator popup menu should be disabled when no entry is selected -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157342] Delete menu item in Master Navigator popup menu should be disabled when no entry is selected
https://bugs.documentfoundation.org/show_bug.cgi?id=157342 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Priority|medium |low Blocks||107805 Status|NEEDINFO|NEW Severity|normal |minor --- Comment #5 from Stéphane Guillou (stragu) --- Reproduced in: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: f95c3994f0b6a82a3bc2ddfb68822b74479ae185 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded To have no selection in the Navigator, I use the Toggle Master View with the top-left button. Right-clicking in the blank area does show "Delete", and click it has no effect. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107805 [Bug 107805] [META] Writer master document issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142340] Interface on the LibreOffice – Application colors page incompatible with pt-br translation
https://bugs.documentfoundation.org/show_bug.cgi?id=142340 --- Comment #2 from Tulio Macedo --- (In reply to BogdanB from comment #1) > Should string "ON" to be removed because it's clear that checkboxes need to > be clicked? > Would not be better? That would be a way to deal with it. The dialog was build and tested clearly with an interface in mind, what isn't bad, but it could lead to some problems, like that in the bug. For an application that should run in so many systems it's complicated. It's possible that many other places like exist right now in LO. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107658] Display of hidden text when toggling formatting marks should be enabled by default
https://bugs.documentfoundation.org/show_bug.cgi?id=107658 --- Comment #16 from Justin L --- FYI: Display of hidden text was made the only choice for LOKit with https://gerrit.libreoffice.org/c/core/+/157562. If this default ever changes to default to enabled, that patch can be reverted. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: config_host.mk.in configure.ac extras/Module_extras.mk
config_host.mk.in |1 +
configure.ac| 33 +
extras/Module_extras.mk | 13 +
3 files changed, 43 insertions(+), 4 deletions(-)
New commits:
commit f3a0550b1dd0914e8cbc026a90e10ee3ae2dc8e3
Author: Balazs Varga
AuthorDate: Thu Oct 5 18:21:48 2023 +0200
Commit: Andras Timar
CommitDate: Thu Oct 5 21:37:09 2023 +0200
tdf#101970 Introduce config option for building with or
without the not necessary template files.
The default is building with all templates, otherwise we can use:
--with-templates=no/yes
--with-templates -->yes
--without-templates -->no
Change-Id: I13f5b411057254771ad4021aa9521c153702af16
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/157600
Tested-by: Jenkins
Reviewed-by: Andras Timar
diff --git a/config_host.mk.in b/config_host.mk.in
index f4e6841b22d6..c8990ddab3ae 100644
--- a/config_host.mk.in
+++ b/config_host.mk.in
@@ -737,6 +737,7 @@ export
WITH_EXTENSION_INTEGRATION=@WITH_EXTENSION_INTEGRATION@
export WITH_EXTRA_EXTENSIONS=@WITH_EXTRA_EXTENSIONS@
export WITH_FONTS=@WITH_FONTS@
export WITH_GALLERY_BUILD=@WITH_GALLERY_BUILD@
+export WITH_TEMPLATES=@WITH_TEMPLATES@
export WITH_GSSAPI=@WITH_GSSAPI@
export WITH_KRB5=@WITH_KRB5@
export WITH_LINKER_HASH_STYLE=@WITH_LINKER_HASH_STYLE@
diff --git a/configure.ac b/configure.ac
index e9c6ba7561b9..987a5341cb57 100644
--- a/configure.ac
+++ b/configure.ac
@@ -2134,6 +2134,13 @@ AC_ARG_WITH(galleries,
or to disable them ("no")]),
)
+AC_ARG_WITH(templates,
+AS_HELP_STRING([--with-templates],
+[Specify we build with or without template files. It is possible
either to
+ build with templates ("yes"),
+ or to disable them ("no")]),
+)
+
AC_ARG_WITH(theme,
AS_HELP_STRING([--with-theme="theme1 theme2..."],
[Choose which themes to include. By default those themes with an '*'
are included.
@@ -3088,6 +3095,7 @@ if test "$enable_wasm_strip" = "yes"; then
test_libzmf=no
test_webdav=no
with_galleries=no
+with_templates=no
with_webdav=no
with_x=no
@@ -3238,6 +3246,30 @@ else
fi
AC_SUBST(WITH_GALLERY_BUILD)
+dnl ===
+dnl Sort out various templates compilation options
+dnl ===
+WITH_TEMPLATES=TRUE
+AC_MSG_CHECKING([build with or without template files])
+if test -n "${with_templates}"; then
+if test "$with_templates" = "yes"; then
+AC_MSG_RESULT([enable all templates])
+elif test "$with_templates" = "no"; then
+WITH_TEMPLATES=
+AC_MSG_RESULT([disable non-internal templates])
+else
+AC_MSG_ERROR([unknown value --with-templates=$with_templates])
+fi
+else
+if test $_os != iOS -a $_os != Android -a $_os != Emscripten; then
+AC_MSG_RESULT([enable all templates])
+else
+WITH_TEMPLATES=
+AC_MSG_RESULT([disable non-internal templates])
+fi
+fi
+AC_SUBST(WITH_TEMPLATES)
+
dnl ===
dnl Checks if ccache is available
dnl ===
@@ -5719,6 +5751,7 @@ if test "$cross_compiling" = "yes"; then
fi
test -n "$TARFILE_LOCATION" && sub_conf_opts="$sub_conf_opts
--with-external-tar=$TARFILE_LOCATION"
test "$with_galleries" = "no" -o -z "$WITH_GALLERY_BUILD" &&
sub_conf_opts="$sub_conf_opts --with-galleries=no
--disable-database-connectivity"
+test "$with_templates" = "no" -o -z "$WITH_TEMPLATES" &&
sub_conf_opts="$sub_conf_opts --with-templates=no"
test -n "$with_help" -a "$with_help" != "no" &&
sub_conf_opts="$sub_conf_opts --with-help=$with_help"
test "$enable_extensions" = yes || sub_conf_opts="$sub_conf_opts
--disable-extensions"
test "${enable_ld+set}" = set -a "$build_cpu" = "$host_cpu" &&
sub_conf_opts="$sub_conf_opts --enable-ld=${enable_ld}"
diff --git a/extras/Module_extras.mk b/extras/Module_extras.mk
index fb4ca1d4a354..497a188cc142 100644
--- a/extras/Module_extras.mk
+++ b/extras/Module_extras.mk
@@ -34,10 +34,6 @@ $(eval $(call gb_Module_add_targets,extras,\
Package_labels \
$(if $(filter WNT,$(OS)),Package_newfiles) \
Package_palettes \
- Package_templates \
- Package_tplpresnt \
- Package_tplwizard \
- Package_tplwizbitmap \
Package_tplwizdesktop \
Package_wordbook \
))
@@ -54,6 +50,15 @@ $(eval $(call gb_Module_add_targets,extras,\
))
endif
+ifneq ($(WITH_TEMPLATES),)
+$(eval $(call gb_Module_add_targets,extras,\
+ Package_templates \
+ Package_tplpresnt \
+ Package_tplwizard \
+ Package_tplwizbitmap \
+))
+endif
+
$(eval $(call gb_Module_add_targets,extras,\
Personas \
))
[Libreoffice-bugs] [Bug 146984] Lost page break: Image in frame jump to second page on DOCX export (fine with DOC)
https://bugs.documentfoundation.org/show_bug.cgi?id=146984 Justin L changed: What|Removed |Added Whiteboard|target:7.6.0 target:24.2.0 | |target:7.6.3| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146984] Lost page break: Image in frame jump to second page on DOCX export (fine with DOC)
https://bugs.documentfoundation.org/show_bug.cgi?id=146984 Justin L changed: What|Removed |Added Assignee|jl...@mail.com |libreoffice-b...@lists.free ||desktop.org -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108771] [META] DOCX (OOXML) page-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=108771 Bug 108771 depends on bug 146984, which changed state. Bug 146984 Summary: Lost page break: Image in frame jump to second page on DOCX export (fine with DOC) https://bugs.documentfoundation.org/show_bug.cgi?id=146984 What|Removed |Added Status|VERIFIED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157342] Delete menu item in Master Navigator popup menu should be disabled when no entry is selected
https://bugs.documentfoundation.org/show_bug.cgi?id=157342 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #4 from m.a.riosv --- Please attach the sample file, used for the video. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'libreoffice-7-5' - svx/source
svx/source/sidebar/possize/PosSizePropertyPanel.cxx | 32 +++-
svx/source/sidebar/possize/PosSizePropertyPanel.hxx |7 ++--
2 files changed, 22 insertions(+), 17 deletions(-)
New commits:
commit e181518492a69ec853e15813b362bf245ac2fad6
Author: Caolán McNamara
AuthorDate: Tue Oct 3 14:53:17 2023 +0100
Commit: Xisco Fauli
CommitDate: Thu Oct 5 21:19:02 2023 +0200
tdf#155756 sidebar properties not displaying height over 100
Change-Id: I5ea2441319e0d7c34ffdcd179d8a82738da4733f
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/157530
Tested-by: Jenkins
Reviewed-by: Xisco Fauli
Signed-off-by: Xisco Fauli
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/157587
Reviewed-by: Caolán McNamara
diff --git a/svx/source/sidebar/possize/PosSizePropertyPanel.cxx
b/svx/source/sidebar/possize/PosSizePropertyPanel.cxx
index 7d829d324aab..45da8c792ed6 100644
--- a/svx/source/sidebar/possize/PosSizePropertyPanel.cxx
+++ b/svx/source/sidebar/possize/PosSizePropertyPanel.cxx
@@ -94,6 +94,7 @@ PosSizePropertyPanel::PosSizePropertyPanel(
mlRotY(0),
mePoolUnit(),
meDlgUnit(FieldUnit::INCH), // #i124409# init with fallback default
+mbFieldMetricOutDated(true),
maTransfPosXControl(SID_ATTR_TRANSFORM_POS_X, *pBindings, *this),
maTransfPosYControl(SID_ATTR_TRANSFORM_POS_Y, *pBindings, *this),
maTransfWidthControl(SID_ATTR_TRANSFORM_WIDTH, *pBindings, *this),
@@ -686,10 +687,13 @@ void PosSizePropertyPanel::NotifyItemUpdate(
break;
case SID_ATTR_METRIC:
-MetricState( eState, pState );
-UpdateUIScale();
+{
+const Fraction aUIScale(mpView->GetModel()->GetUIScale());
+MetricState(eState, pState, aUIScale);
+UpdateUIScale(aUIScale);
+mbFieldMetricOutDated = false;
break;
-
+}
default:
break;
}
@@ -855,7 +859,7 @@ void
PosSizePropertyPanel::DumpAsPropertyTree(tools::JsonWriter& rJsonWriter)
PanelLayout::DumpAsPropertyTree(rJsonWriter);
}
-void PosSizePropertyPanel::MetricState( SfxItemState eState, const
SfxPoolItem* pState )
+void PosSizePropertyPanel::MetricState(SfxItemState eState, const SfxPoolItem*
pState, const Fraction& rUIScale)
{
bool bPosXBlank = false;
bool bPosYBlank = false;
@@ -865,7 +869,8 @@ void PosSizePropertyPanel::MetricState( SfxItemState
eState, const SfxPoolItem*
// #i124409# use the given Item to get the correct UI unit and initialize
it
// and the Fields using it
FieldUnit eDlgUnit = GetCurrentUnit(eState, pState);
-if (eDlgUnit == meDlgUnit)
+mbFieldMetricOutDated |= (eDlgUnit != meDlgUnit || maUIScale != rUIScale);
+if (!mbFieldMetricOutDated)
return;
meDlgUnit = eDlgUnit;
@@ -880,7 +885,8 @@ void PosSizePropertyPanel::MetricState( SfxItemState
eState, const SfxPoolItem*
SetFieldUnit( *mxMtrPosY, meDlgUnit, true );
if(bPosYBlank)
mxMtrPosY->set_text(OUString());
-SetPosSizeMinMax();
+
+SetPosSizeMinMax(rUIScale);
if (mxMtrWidth->get_text().isEmpty())
bWidthBlank = true;
@@ -1008,7 +1014,7 @@ void PosSizePropertyPanel::DisableControls()
}
}
-void PosSizePropertyPanel::SetPosSizeMinMax()
+void PosSizePropertyPanel::SetPosSizeMinMax(const Fraction& rUIScale)
{
SdrPageView* pPV = mpView->GetSdrPageView();
if (!pPV)
@@ -1021,9 +1027,8 @@ void PosSizePropertyPanel::SetPosSizeMinMax()
pPV->LogicToPagePos(aTmpRect2);
maWorkArea = vcl::unotools::b2DRectangleFromRectangle(aTmpRect2);
-const Fraction aUIScale(mpView->GetModel()->GetUIScale());
-TransfrmHelper::ScaleRect( maWorkArea, aUIScale );
-TransfrmHelper::ScaleRect( maRect, aUIScale );
+TransfrmHelper::ScaleRect(maWorkArea, rUIScale);
+TransfrmHelper::ScaleRect(maRect, rUIScale);
const sal_uInt16 nDigits(mxMtrPosX->get_digits());
TransfrmHelper::ConvertRect( maWorkArea, nDigits, mePoolUnit, meDlgUnit );
@@ -1058,16 +1063,15 @@ void PosSizePropertyPanel::SetPosSizeMinMax()
limitWidth(*mxMtrHeight);
}
-void PosSizePropertyPanel::UpdateUIScale()
+void PosSizePropertyPanel::UpdateUIScale(const Fraction& rUIScale)
{
-const Fraction aUIScale (mpView->GetModel()->GetUIScale());
-if (maUIScale == aUIScale)
+if (maUIScale == rUIScale)
return;
// UI scale has changed.
// Remember the new UI scale.
-maUIScale = aUIScale;
+maUIScale = rUIScale;
// The content of the position and size boxes is only updated when item
changes are notified.
// Request such notifications without changing the actual item values.
diff --git a/svx/source/sidebar/possize/PosSizePropertyPanel.hxx
b/svx/source/sidebar/possize/PosSizePropertyPanel.hxx
index 42af309883b2..b57d0bcf7dde 100644
--- a/svx/source/sidebar/possize/PosSizePropertyPanel.hxx
+++ b/svx/source/sidebar/possize/PosSizePropertyPanel.hxx
@@
[Libreoffice-commits] core.git: Branch 'libreoffice-7-6' - sw/source
sw/source/core/inc/ftnfrm.hxx |1 -
sw/source/core/text/EnhancedPDFExportHelper.cxx | 23 +++
2 files changed, 15 insertions(+), 9 deletions(-)
New commits:
commit 9942f9f76ffda559eccc3e4c8e196d5fe36f2051
Author: Michael Stahl
AuthorDate: Mon Oct 2 19:46:36 2023 +0200
Commit: Caolán McNamara
CommitDate: Thu Oct 5 21:18:32 2023 +0200
sw: PDF/UA export: merge footnote frame follows
Change-Id: Icb1c585c4d321e38a6ac3d841846d505c4816db2
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/157504
Tested-by: Jenkins
Reviewed-by: Michael Stahl
(cherry picked from commit 5cdb4e495e23be77466d8f8bbe6ae643b60d3aa6)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/157535
Reviewed-by: Caolán McNamara
diff --git a/sw/source/core/inc/ftnfrm.hxx b/sw/source/core/inc/ftnfrm.hxx
index a514e4ba10d3..89d9f34f863a 100644
--- a/sw/source/core/inc/ftnfrm.hxx
+++ b/sw/source/core/inc/ftnfrm.hxx
@@ -84,7 +84,6 @@ class SwFootnoteFrame final : public SwLayoutFrame
{
// Pointer to FootnoteFrame in which the footnote will be continued:
// - 0 no following existent
-// - this for the last one
// - otherwise the following FootnoteFrame
SwFootnoteFrame *mpFollow;
SwFootnoteFrame *mpMaster; // FootnoteFrame from which I am the
following
diff --git a/sw/source/core/text/EnhancedPDFExportHelper.cxx
b/sw/source/core/text/EnhancedPDFExportHelper.cxx
index 3cd5176cb786..3103b3fe9ef8 100644
--- a/sw/source/core/text/EnhancedPDFExportHelper.cxx
+++ b/sw/source/core/text/EnhancedPDFExportHelper.cxx
@@ -67,6 +67,7 @@
#include
#include
#include
+#include
#include
#include
#include "porfld.hxx"
@@ -266,25 +267,29 @@ bool lcl_IsInNonStructEnv( const SwFrame& rFrame )
}
// Generate key from frame for reopening tags:
-void* lcl_GetKeyFromFrame( const SwFrame& rFrame )
+void const* lcl_GetKeyFromFrame( const SwFrame& rFrame )
{
-void* pKey = nullptr;
+void const* pKey = nullptr;
if ( rFrame.IsPageFrame() )
-pKey = const_cast(static_cast(&(static_cast(rFrame).GetFormat()->getIDocumentSettingAccess(;
+pKey = static_cast(&(static_cast(rFrame).GetFormat()->getIDocumentSettingAccess()));
else if ( rFrame.IsTextFrame() )
-pKey = const_cast(static_cast(static_cast(rFrame).GetTextNodeFirst()));
+pKey = static_cast(static_cast(rFrame).GetTextNodeFirst());
else if ( rFrame.IsSctFrame() )
-pKey = const_cast(static_cast(static_cast(rFrame).GetSection()));
+pKey = static_cast(static_cast(rFrame).GetSection());
else if ( rFrame.IsTabFrame() )
-pKey = const_cast(static_cast(static_cast(rFrame).GetTable()));
+pKey = static_cast(static_cast(rFrame).GetTable());
else if ( rFrame.IsRowFrame() )
-pKey = const_cast(static_cast(static_cast(rFrame).GetTabLine()));
+pKey = static_cast(static_cast(rFrame).GetTabLine());
else if ( rFrame.IsCellFrame() )
{
const SwTabFrame* pTabFrame = rFrame.FindTabFrame();
const SwTable* pTable = pTabFrame->GetTable();
-pKey = const_cast(static_cast(& static_cast(rFrame).GetTabBox()->FindStartOfRowSpan( *pTable )));
+pKey = static_cast(& static_cast(rFrame).GetTabBox()->FindStartOfRowSpan(*pTable));
+}
+else if (rFrame.IsFootnoteFrame())
+{
+pKey = static_cast(static_cast(rFrame).GetAttr());
}
return pKey;
@@ -420,6 +425,7 @@ bool SwTaggedPDFHelper::CheckReopenTag()
// - rFrame is a cell frame in a follow flow row (reopen TableData tag)
if ( ( rFrame.IsPageFrame() && static_cast(rFrame).GetPrev() ) ||
( rFrame.IsFlowFrame() &&
SwFlowFrame::CastFlowFrame()->IsFollow() ) ||
+ (rFrame.IsFootnoteFrame() && static_cast(rFrame).GetMaster()) ||
( rFrame.IsRowFrame() && rFrame.IsInFollowFlowRow() ) ||
( rFrame.IsCellFrame() &&
const_cast(rFrame).GetPrevCellLeaf() ) )
{
@@ -511,6 +517,7 @@ void SwTaggedPDFHelper::BeginTag(
vcl::PDFWriter::StructElement eType, const OUS
if ( ( rFrame.IsPageFrame() && !static_cast(rFrame).GetPrev() ) ||
( rFrame.IsFlowFrame() &&
!SwFlowFrame::CastFlowFrame()->IsFollow() &&
SwFlowFrame::CastFlowFrame()->HasFollow() ) ||
( rFrame.IsTextFrame() && rFrame.GetDrawObjs() ) ||
+ (rFrame.IsFootnoteFrame() && static_cast(rFrame).GetFollow()) ||
( rFrame.IsRowFrame() && rFrame.IsInSplitTableRow() ) ||
( rFrame.IsCellFrame() &&
const_cast(rFrame).GetNextCellLeaf() ) )
{
[Libreoffice-commits] core.git: Branch 'libreoffice-7-6' - sw/qa writerfilter/source
dev/null |binary
sw/qa/extras/ooxmlexport/ooxmlexport18.cxx| 15 ---
writerfilter/source/dmapper/DomainMapper.cxx |5 +
writerfilter/source/dmapper/DomainMapper_Impl.cxx | 13 -
writerfilter/source/dmapper/DomainMapper_Impl.hxx |3 ---
5 files changed, 1 insertion(+), 35 deletions(-)
New commits:
commit 06702d8474bdac71fa2a61723ea476e888fc91d6
Author: Justin Luth
AuthorDate: Thu Oct 5 07:24:56 2023 -0400
Commit: Xisco Fauli
CommitDate: Thu Oct 5 21:17:04 2023 +0200
tdf#157574 Revert "tdf#153613 tdf#146984 split para after anchors"
This reverts 7.6 commit 828fde37632a5bb0542b6925454690a5287d6490.
and also reverts the dependent parts of the follow-up test from
commit 828fde37632a5bb0542b6925454690a5287d6490
(although the patch itself is fine to remain in place)
and also reverts followup "cid#1522030 Uninitialized scalar field"
commit 9a123a6e63600ba3998d22bbc300ac4b65b3da2c.
The commit in general is fine. However, it fails in case
of an empty paragraph (with only anchors).
Unfortunately, there is no way of knowing ahead of time,
so either everything needs to be processed after a delay,
or else the paragraph needs to be split and then re-joined
in case it is not an empty paragraph.
Both options are extremely non-trivial - I don't know how
to do either of them.
Change-Id: I9e98d825ad0008e822172b6797116ad16e90b871
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/157593
Tested-by: Jenkins
Reviewed-by: Justin Luth
(cherry picked from commit bd18618aae500d01e665d8af07067bb99a491850)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/157615
diff --git a/sw/qa/extras/ooxmlexport/data/tdf153613_textboxAfterPgBreak3.docx
b/sw/qa/extras/ooxmlexport/data/tdf153613_textboxAfterPgBreak3.docx
deleted file mode 100644
index a282deaa0ad7..
Binary files
a/sw/qa/extras/ooxmlexport/data/tdf153613_textboxAfterPgBreak3.docx and
/dev/null differ
diff --git a/sw/qa/extras/ooxmlexport/ooxmlexport18.cxx
b/sw/qa/extras/ooxmlexport/ooxmlexport18.cxx
index 62dc42dba5af..04c5789c19c6 100644
--- a/sw/qa/extras/ooxmlexport/ooxmlexport18.cxx
+++ b/sw/qa/extras/ooxmlexport/ooxmlexport18.cxx
@@ -193,11 +193,6 @@ DECLARE_OOXMLEXPORT_TEST(testTdf146984_anchorInShape,
"tdf146984_anchorInShape.d
{
// This was only one page b/c the page break was missing.
CPPUNIT_ASSERT_EQUAL(2, getPages());
-
-const auto& pLayout = parseLayoutDump();
-// There are shapes on both pages - these should be non-zero numbers
-assertXPath(pLayout, "//page[1]//anchored", 3);
-assertXPath(pLayout, "//page[2]//anchored", 2);
}
DECLARE_OOXMLEXPORT_TEST(testTdf127622_framePr, "tdf127622_framePr.docx")
@@ -377,16 +372,6 @@
DECLARE_OOXMLEXPORT_TEST(testTdf153613_textboxAfterPgBreak2, "tdf153613_textboxA
assertXPathContent(pLayout, "//page[2]/body/txt", "There should be no
prior carriage return.");
}
-DECLARE_OOXMLEXPORT_TEST(testTdf153613_textboxAfterPgBreak3,
"tdf153613_textboxAfterPgBreak3.docx")
-{
-// All anchored TO-character shapes stay on the first page, before the
page break.
-CPPUNIT_ASSERT_EQUAL(2, getPages());
-CPPUNIT_ASSERT_EQUAL(3, getParagraphs());
-
-const auto& pLayout = parseLayoutDump();
-assertXPath(pLayout, "//page[2]//anchored", 0);
-}
-
DECLARE_OOXMLEXPORT_TEST(testTdf153613_sdtAfterPgBreak,
"tdf153613_sdtAfterPgBreak.docx")
{
CPPUNIT_ASSERT_EQUAL(2, getPages());
diff --git a/writerfilter/source/dmapper/DomainMapper.cxx
b/writerfilter/source/dmapper/DomainMapper.cxx
index e6a7e1dfde9e..148bb98eaf42 100644
--- a/writerfilter/source/dmapper/DomainMapper.cxx
+++ b/writerfilter/source/dmapper/DomainMapper.cxx
@@ -3742,7 +3742,7 @@ void
DomainMapper::lcl_startShape(uno::Reference const& xShape)
{
// If there is a deferred page break, handle it now, so that the
// started shape will be on the correct page.
-if (m_pImpl->isBreakDeferred(PAGE_BREAK) &&
!m_pImpl->IsBreakDeferredByAnchor())
+if (m_pImpl->isBreakDeferred(PAGE_BREAK))
{
// RTF doesn't properly report IsFirstRun, so in order to prevent
regressions
// always split the paragraph for RTF since that is the way it has
been done lately.
@@ -3752,9 +3752,6 @@ void
DomainMapper::lcl_startShape(uno::Reference const& xShape)
finishParagraph();
lcl_startParagraphGroup();
}
-else
-m_pImpl->SetIsBreakDeferredByAnchor();
-
}
m_pImpl->PushShapeContext( xShape );
lcl_startParagraphGroup();
diff --git a/writerfilter/source/dmapper/DomainMapper_Impl.cxx
b/writerfilter/source/dmapper/DomainMapper_Impl.cxx
index 2bf742d3bf1c..1a8f44d8562c 100644
--- a/writerfilter/source/dmapper/DomainMapper_Impl.cxx
+++
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-23.05' - sw/qa sw/source
sw/qa/filter/ww8/data/floattable-in-inlinetable.doc |binary
sw/qa/filter/ww8/ww8.cxx| 37
sw/source/filter/ww8/ww8par2.cxx| 11 +++--
3 files changed, 44 insertions(+), 4 deletions(-)
New commits:
commit 589af9366078036c2f33e3254a628e267628352c
Author: Miklos Vajna
AuthorDate: Wed Oct 4 08:29:13 2023 +0200
Commit: Caolán McNamara
CommitDate: Thu Oct 5 20:53:45 2023 +0200
tdf#126449 sw floattable: DOC import: handle inner floating table
One problem with the bugdoc is that the inner floating tables in the DOC
file stay in a single page.
Seems the usual to-para anchoring + allow-to-split logic is not used
here, because the toplevel table is handled at
SwWW8ImplReader::StartApo(), but the inner table is handled in
SwWW8ImplReader::StartTable(). Additionally, the toplevel table is
anchored to-para (which seems to be the closest to Word's "position this
table based on the next paragraph" concept), but the inner table was
anchored to-char, and such fly frames can't split.
Fix the problem by switching to to-para anchoring even for inner
floating tables. This improves consistency with toplevel floatint tables
from DOC and all floating tables from DOCX. It seems to the to-char
anchor type was added in commit 10f352d2faf6a4d72337b2c098a65377eee5138b
(INTEGRATION: CWS swqbugfixes18 (1.111.60); FILE MERGED, 2005-03-30),
but there the motivation was to make sure these are not inline; so that
use-case keeps working.
This does fix the overlapping text with the original bugdoc, but
otherwise the DOCX version is still slightly closer to the Word render
result.
(cherry picked from commit 89a75cd194371002247d0138e759835bc673f7b0)
Change-Id: I379a26194da4d3a06241aa3c6f5ae78606f8fc12
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/157598
Tested-by: Jenkins CollaboraOffice
Reviewed-by: Caolán McNamara
diff --git a/sw/qa/filter/ww8/data/floattable-in-inlinetable.doc
b/sw/qa/filter/ww8/data/floattable-in-inlinetable.doc
new file mode 100644
index ..a2f06973a53c
Binary files /dev/null and
b/sw/qa/filter/ww8/data/floattable-in-inlinetable.doc differ
diff --git a/sw/qa/filter/ww8/ww8.cxx b/sw/qa/filter/ww8/ww8.cxx
index 6914ea8677b6..2a5fd2c08416 100644
--- a/sw/qa/filter/ww8/ww8.cxx
+++ b/sw/qa/filter/ww8/ww8.cxx
@@ -28,6 +28,7 @@
#include
#include
#include
+#include
namespace
{
@@ -463,6 +464,42 @@ CPPUNIT_TEST_FIXTURE(Test, testFloattableFootnote)
// - Actual : 0
CPPUNIT_ASSERT_EQUAL(static_cast(1), rFootnotes.size());
}
+
+CPPUNIT_TEST_FIXTURE(Test, testSplitFlyInInlineTableDOC)
+{
+// Outer inline table on pages 1 -> 2 -> 3, inner floating table on pages
2 -> 3:
+// When laying out that document:
+createSwDoc("floattable-in-inlinetable.doc");
+
+SwDoc* pDoc = getSwDoc();
+SwRootFrame* pLayout = pDoc->getIDocumentLayoutAccess().GetCurrentLayout();
+auto pPage1 = pLayout->Lower()->DynCastPageFrame();
+CPPUNIT_ASSERT(pPage1);
+{
+SwFrame* pBody = pPage1->FindBodyCont();
+auto pTab = pBody->GetLower()->DynCastTabFrame();
+CPPUNIT_ASSERT(!pTab->GetPrecede());
+CPPUNIT_ASSERT(pTab->GetFollow());
+}
+auto pPage2 = pPage1->GetNext()->DynCastPageFrame();
+CPPUNIT_ASSERT(pPage2);
+{
+SwFrame* pBody = pPage2->FindBodyCont();
+auto pTab = pBody->GetLower()->DynCastTabFrame();
+CPPUNIT_ASSERT(pTab->GetPrecede());
+// Without the accompanying fix in place, this test would have failed,
the outer table was
+// missing on page 3.
+CPPUNIT_ASSERT(pTab->GetFollow());
+}
+auto pPage3 = pPage2->GetNext()->DynCastPageFrame();
+CPPUNIT_ASSERT(pPage3);
+{
+SwFrame* pBody = pPage3->FindBodyCont();
+auto pTab = pBody->GetLower()->DynCastTabFrame();
+CPPUNIT_ASSERT(pTab->GetPrecede());
+CPPUNIT_ASSERT(!pTab->GetFollow());
+}
+}
}
CPPUNIT_PLUGIN_IMPLEMENT();
diff --git a/sw/source/filter/ww8/ww8par2.cxx b/sw/source/filter/ww8/ww8par2.cxx
index 0f8ab1f8ebc6..503437c8231b 100644
--- a/sw/source/filter/ww8/ww8par2.cxx
+++ b/sw/source/filter/ww8/ww8par2.cxx
@@ -3455,8 +3455,8 @@ bool SwWW8ImplReader::StartTable(WW8_CP nStartCp)
m_aSectionManager.GetTextAreaWidth(),
m_nIniFlyDx, m_nIniFlyDy);
-// #i45301# - anchor nested table Writer fly frame at-character
-eAnchor = RndStdIds::FLY_AT_CHAR;
+// #i45301# - anchor nested table Writer fly frame
+eAnchor = RndStdIds::FLY_AT_PARA;
}
}
}
@@ -3474,7 +3474,7 @@ bool SwWW8ImplReader::StartTable(WW8_CP nStartCp)
{
int nNewInTable = m_nInTable + 1;
-if ((eAnchor == RndStdIds::FLY_AT_CHAR)
+if ((eAnchor ==
[Libreoffice-bugs] [Bug 157164] Frame > Position and Size > Vertical Position preview does not show red line for baseline anymore
https://bugs.documentfoundation.org/show_bug.cgi?id=157164 Jim Avera changed: What|Removed |Added Attachment #190051|0 |1 is obsolete|| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157164] Frame > Position and Size > Vertical Position preview does not show red line for baseline anymore
https://bugs.documentfoundation.org/show_bug.cgi?id=157164 --- Comment #14 from Jim Avera --- Ignore that. The alt2.odt test case had Vertical Position referenced to "Character" not "Baseline", so the rectangle is correct in that case. So I now also confirm the problem as reported is fixed. Thank you. P.S. What does the small grey-filled box in the middle denote? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157164] Frame > Position and Size > Vertical Position preview does not show red line for baseline anymore
https://bugs.documentfoundation.org/show_bug.cgi?id=157164 --- Comment #13 from Jim Avera --- I used different test case when dis-confirming -- which I just uploaded as noredline_alt2.odt This one initially shows a red box, not line. However switching the anchor to something else and back to "As Character" makes the line appear. Do you think this is an unrelated bug? In summary: We saw different results because of the instability noted by Stéphane in Comment 11. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157609] "This file has been locked by another user" pop-up
https://bugs.documentfoundation.org/show_bug.cgi?id=157609 Julien Nabet changed: What|Removed |Added CC||gerardo.apoli...@gmail.com --- Comment #3 from Julien Nabet --- *** Bug 157619 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: forms/source
forms/source/misc/InterfaceContainer.cxx | 19 +--
1 file changed, 5 insertions(+), 14 deletions(-)
New commits:
commit 74410e57bda7ec355e92ced5c21c956f83a0f6b7
Author: Julien Nabet
AuthorDate: Thu Oct 5 13:05:05 2023 +0200
Commit: Julien Nabet
CommitDate: Thu Oct 5 20:35:59 2023 +0200
Replace useless lcl_throwIllegalArgumentException function (forms)
Change-Id: Icad8c36ef91edd12da8cc533e3ce24ca8a28
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/157590
Tested-by: Jenkins
Reviewed-by: Julien Nabet
diff --git a/forms/source/misc/InterfaceContainer.cxx
b/forms/source/misc/InterfaceContainer.cxx
index f7278117899c..90a918f5edcd 100644
--- a/forms/source/misc/InterfaceContainer.cxx
+++ b/forms/source/misc/InterfaceContainer.cxx
@@ -71,15 +71,6 @@ using namespace ::com::sun::star::io;
using namespace ::com::sun::star::form;
using namespace ::com::sun::star::util;
-namespace
-{
-
-void lcl_throwIllegalArgumentException()
-{
-throw IllegalArgumentException();
-}
-}
-
static bool
lcl_hasVbaEvents( const Sequence< ScriptEventDescriptor >& sEvents )
{
@@ -739,17 +730,17 @@ void OInterfaceContainer::approveNewElement( const
Reference< XPropertySet >& _r
// it has to support our element type interface
Any aCorrectType = _rxObject->queryInterface( m_aElementType );
if ( !aCorrectType.hasValue() )
-lcl_throwIllegalArgumentException();
+throw IllegalArgumentException();
// it has to have a "Name" property
if ( !hasProperty( PROPERTY_NAME, _rxObject ) )
-lcl_throwIllegalArgumentException();
+throw IllegalArgumentException();
// it has to be a child, and it must not have a parent already
Reference< XChild > xChild( _rxObject, UNO_QUERY );
if ( !xChild.is() || xChild->getParent().is() )
{
-lcl_throwIllegalArgumentException();
+throw IllegalArgumentException();
}
// passed all tests. cache the information we have so far
@@ -1107,14 +1098,14 @@ void SAL_CALL OInterfaceContainer::replaceByName(const
OUString& Name, const Any
throw NoSuchElementException();
if (Element.getValueType().getTypeClass() != TypeClass_INTERFACE)
-lcl_throwIllegalArgumentException();
+throw IllegalArgumentException();
Reference xSet;
Element >>= xSet;
if (xSet.is())
{
if (!hasProperty(PROPERTY_NAME, xSet))
-lcl_throwIllegalArgumentException();
+throw IllegalArgumentException();
xSet->setPropertyValue(PROPERTY_NAME, Any(Name));
}
[Libreoffice-bugs] [Bug 157164] Frame > Position and Size > Vertical Position preview does not show red line for baseline anymore
https://bugs.documentfoundation.org/show_bug.cgi?id=157164 --- Comment #12 from Jim Avera --- Created attachment 190051 --> https://bugs.documentfoundation.org/attachment.cgi?id=190051=edit noredline_alt2.odt (a different test case which shows rectangle initially) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157561] Invalid error message opening .mdb/.accdb file
https://bugs.documentfoundation.org/show_bug.cgi?id=157561 --- Comment #4 from Robert Großkopf --- (In reply to ilya.y.komarov from comment #3)> > > 1. open LibreOffice. > 2. create a new .odb file. > 3. open any .mdb file. Step 2: Create a new odb-file, which connects to an external database. This should be the Access file. Under Windows you might get direct the connection to the *.mdb-file from the obd-file. With Linux you have to connect through JDBC by https://ucanaccess.sourceforge.net/site.html LibreOffice won't open the *.mdb-file directly. Base would connect to the tables and views, but all other content won't be shown. When reading the description with "Step 3: Open any .mdb file" it seems you don't connect through Base to the file but try to open the *.mdb-file directly. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156714] .uno:IndexMarktoIndex does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=156714 --- Comment #9 from Jim Raykowski --- Created attachment 190050 --> https://bugs.documentfoundation.org/attachment.cgi?id=190050=edit video of my guess of the intended action of this UNO Maybe? -- You are receiving this mail because: You are the assignee for the bug.
Re: new bridgetest failures in 7.6 on ppc64le
On 10/5/23 17:46, Dan Horák wrote: I will look further especially at the dynamically generated stubs, which is new to me. Apply those stubs to the C++ bridge as well? When a reference to an external object (e.g., a Java one, or one in a remote process) is brought in over the binary UNO to C++ bridge, a fake C++ object is created as a proxy for that external object, and that fake object's vtable function pointers pointer at such dynamically generated stubs. On the other hand, when directly calling from C++ to C++, no bridging is involved.
[Libreoffice-bugs] [Bug 157619] otro usuario ha bloqueado este archivo
https://bugs.documentfoundation.org/show_bug.cgi?id=157619 Jesus G Apolinar changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |gerardo.apoli...@gmail.com |desktop.org | Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC||gerardo.apoli...@gmail.com --- Comment #1 from Jesus G Apolinar --- Created attachment 190049 --> https://bugs.documentfoundation.org/attachment.cgi?id=190049=edit Imagen del problema -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157619] New: otro usuario ha bloqueado este archivo
https://bugs.documentfoundation.org/show_bug.cgi?id=157619 Bug ID: 157619 Summary: otro usuario ha bloqueado este archivo Product: LibreOffice Version: 7.6.1.2 release Hardware: x86-64 (AMD64) OS: other Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: gerardo.apoli...@gmail.com Description: Cada vez que abro un archivo de woord o libre office writer (en ese caso) me aparece la leyenda otro usuario ha bloqueado este archivo, y aparece el archivo como "sin titulo" si lo transcribo no me deja guardarlo con el nombre , es decir debo ponerle nombre, esto paso recientemente, despues de instalar windows 11, pero Actualmente ya DESINSTALE windows 11 y sigue el problema Steps to Reproduce: 1.Abro el archivo 2.Aparece la leyenda otro usuario ha bloqueado este archivo y el archivo como "sin titulo" cuando antes si tenia nombre, lo abro solo en copia 3.Para guardarlo debo renombrarlo Actual Results: 1.Abro el archivo 2.Aparece la leyenda otro usuario ha bloqueado este archivo y el archivo como "sin titulo" cuando antes si tenia nombre, lo abro solo en copia 3.Para guardarlo debo renombrarlo Expected Results: Que todo vuelva a la normalidad, pues soy el unico usuario en la PC Reproducible: Always User Profile Reset: Yes Additional Info: Deberia dejarme abrir el archivo, sin quitarle el nombre, y poderlo transcribir, luego guardar sin problemas y sin tener que renombrarlo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/inc sw/qa sw/source
sw/inc/viewopt.hxx |5
sw/qa/extras/tiledrendering/data/hiddenLoremIpsum.docx |binary
sw/qa/extras/tiledrendering/tiledrendering.cxx | 18 +
sw/source/uibase/config/viewopt.cxx|6 +
4 files changed, 25 insertions(+), 4 deletions(-)
New commits:
commit 27d0c8cbba2a9c2b6aa43e97d56f62d15b3b5bca
Author: Justin Luth
AuthorDate: Wed Oct 4 10:04:42 2023 -0400
Commit: Miklos Vajna
CommitDate: Thu Oct 5 19:21:03 2023 +0200
LOKit: always display hidden chars when showing formatting marks
This is related to the request in tdf#107658 to do the same for core.
However, this is something fairly easily doable with an extension
in core, so I'm not in favour of forcing one user's opinion over top
of status quo.
Doing this only for Online.
make CppunitTest_sw_tiledrendering \
CPPUNIT_TEST_NAME=testShowHiddenCharsWhenShowFormatting
Change-Id: I34bbe50dd4bbff92577b18f8a05d2f8dd67ea771
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/157562
Tested-by: Jenkins
Reviewed-by: Justin Luth
Reviewed-by: Miklos Vajna
diff --git a/sw/inc/viewopt.hxx b/sw/inc/viewopt.hxx
index b82b970cb540..b5bf16b5ca22 100644
--- a/sw/inc/viewopt.hxx
+++ b/sw/inc/viewopt.hxx
@@ -484,10 +484,7 @@ public:
void SetTreatSubOutlineLevelsAsContent(bool b)
{ m_nCoreOptions.bTreatSubOutlineLevelsAsContent = b; }
-bool IsShowHiddenChar(bool bHard = false) const
-{ return !m_bReadonly && m_nCoreOptions.bCharHidden &&
-(m_nCoreOptions.bViewMetachars || bHard); }
-
+bool IsShowHiddenChar(bool bHard = false) const;
void SetShowHiddenChar( bool b )
{ m_nCoreOptions.bCharHidden = b; }
diff --git a/sw/qa/extras/tiledrendering/data/hiddenLoremIpsum.docx
b/sw/qa/extras/tiledrendering/data/hiddenLoremIpsum.docx
new file mode 100644
index ..0802f6e7d314
Binary files /dev/null and
b/sw/qa/extras/tiledrendering/data/hiddenLoremIpsum.docx differ
diff --git a/sw/qa/extras/tiledrendering/tiledrendering.cxx
b/sw/qa/extras/tiledrendering/tiledrendering.cxx
index 2e43441958f8..b3b6c948d884 100644
--- a/sw/qa/extras/tiledrendering/tiledrendering.cxx
+++ b/sw/qa/extras/tiledrendering/tiledrendering.cxx
@@ -2971,6 +2971,24 @@ CPPUNIT_TEST_FIXTURE(SwTiledRenderingTest,
testPilcrowRedlining)
comphelper::dispatchCommand(".uno:ControlCodes", {});
}
+CPPUNIT_TEST_FIXTURE(SwTiledRenderingTest,
testShowHiddenCharsWhenShowFormatting)
+{
+// In LOKit, ignore the config setting for
+// Tools - Options - Writer - Formatting Aids - Display Formatting -
Hidden characters
+// and always show hidden content when showing pilcrow formatting
+
+createSwDoc("hiddenLoremIpsum.docx");
+
+// Since LOKit is active in TiledRendering, turning on "Show formatting"
will show hidden text.
+comphelper::dispatchCommand(".uno:ControlCodes", {}); // show format marks
+Scheduler::ProcessEventsToIdle();
+
+// Without this patch, no body text would be visible - so only 1 page
instead of 3.
+CPPUNIT_ASSERT_EQUAL(3, getPages());
+
+comphelper::dispatchCommand(".uno:ControlCodes", {});
+}
+
CPPUNIT_TEST_FIXTURE(SwTiledRenderingTest, testDoubleUnderlineAndStrikeOut)
{
// Load a document where the tracked text moving is visible with
diff --git a/sw/source/uibase/config/viewopt.cxx
b/sw/source/uibase/config/viewopt.cxx
index 93ee5f710653..1e78b1fdac02 100644
--- a/sw/source/uibase/config/viewopt.cxx
+++ b/sw/source/uibase/config/viewopt.cxx
@@ -184,6 +184,12 @@ bool SwViewOption::IsTreatSubOutlineLevelsAsContent() const
return m_nCoreOptions.bTreatSubOutlineLevelsAsContent;
}
+bool SwViewOption::IsShowHiddenChar(bool bHard) const
+{
+bool bCharHidden = comphelper::LibreOfficeKit::isActive() ? true :
m_nCoreOptions.bCharHidden;
+return !m_bReadonly && bCharHidden && (m_nCoreOptions.bViewMetachars ||
bHard);
+}
+
void SwViewOption::DrawRect( OutputDevice *pOut,
const SwRect , ::Color nCol )
{
[Libreoffice-bugs] [Bug 95385] Sidebar : category General does not exist and inconsistent with cell formatting dialog (see comment 7, comment 8, comment 21)
https://bugs.documentfoundation.org/show_bug.cgi?id=95385 Eike Rathke changed: What|Removed |Added Summary|Sidebar : category General |Sidebar : category General |does not exist and |does not exist and |inconsistent with cell |inconsistent with cell |formatting dialog |formatting dialog (see ||comment 7, comment 8, ||comment 21) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 101970] [PACKAGING] Make default templates installation optional
https://bugs.documentfoundation.org/show_bug.cgi?id=101970 Balázs Varga (allotropia) changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |balazs.varga...@gmail.com |desktop.org | Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153181] Menu key on keyboard can open context menu outside screen
https://bugs.documentfoundation.org/show_bug.cgi?id=153181 --- Comment #6 from ilya.y.koma...@gmail.com --- Created attachment 190048 --> https://bugs.documentfoundation.org/attachment.cgi?id=190048=edit Context menu -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153181] Menu key on keyboard can open context menu outside screen
https://bugs.documentfoundation.org/show_bug.cgi?id=153181 ilya.y.koma...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153181] Menu key on keyboard can open context menu outside screen
https://bugs.documentfoundation.org/show_bug.cgi?id=153181 ilya.y.koma...@gmail.com changed: What|Removed |Added CC||ilya.y.koma...@gmail.com --- Comment #5 from ilya.y.koma...@gmail.com --- Same bug in Version: 24.2.0.0.alpha0+ (x86) / LibreOffice Community Build ID: 2902ab24ecc5ffbf4907ea83b2028508b9de6364 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-CA (en_CA); UI: en-US Calc: CL threaded and Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-CA (en_CA); UI: en-US Calc: CL threaded the lower or higher the last visible selected cell, the less of the menu is visible. -- You are receiving this mail because: You are the assignee for the bug.
Re: new bridgetest failures in 7.6 on ppc64le
On Thu, 5 Oct 2023 17:46:13 +0200
Dan Horák wrote:
> On Thu, 5 Oct 2023 17:11:55 +0200
> Stephan Bergmann wrote:
>
> > On 10/5/23 10:38, Dan Horák wrote:
> > > I would appreciate any tips and tricks how to attack this problem with
> > > gdb, because I wasn't successful in getting into the right place or
> > > process and relied mainly on the old school "printf" method :-)
> >
> > The call
> >
> > > TwoFloats aOut = xLBT->echoTwoFloats(aIn);
> >
> > at testtools/source/bridgetest/bridgetest.cxx:474 goes to a dynamically
> > created stub, generated at runtime by codeSnippet in
> > bridges/source/cpp_uno/gcc3_linux_powerpc64/cpp2uno.cxx, which calls
> > privateSnippetExecutor, which calls cpp_mediate, which (in its case
> > typelib_TypeClass_INTERFACE_METHOD case's default case) calls
> > cpp2uno_call, which at
> >
> > > // invoke uno dispatch call
> > > (*pThis->getUnoI()->pDispatcher)( pThis->getUnoI(), pMemberTypeDescr,
> > > pUnoReturn, pUnoArgs, );
> >
> > calls into the binary UNO to Java bridge. So if you assume that things
> > are fine between binary UNO and Java (which is a reasonable assumption,
> > as that part should be mostly architecture-agnostic), I'd start to debug
> > at the return of that pDispatcher call, and see how its return value
> > (i.e., the return value from
> >
> > > public TwoFloats echoTwoFloats( TwoFloats i_Struct) throws
> > > com.sun.star.uno.RuntimeException {
> > > return i_Struct;
> > > }
> >
> > in testtools/com/sun/star/comp/bridge/TestComponent.java) propagates
> > back down to the original C++ call at
> > testtools/source/bridgetest/bridgetest.cxx:474.
> >
>
> thanks and for the record, with https://fedora.danny.cz/ppc/bridge-debug.patch
> I am getting https://fedora.danny.cz/ppc/bridge-debug.log after "make
> unitcheck"
> under testtools/
>
> You can see both the C++ and Java test running (IMO good for comparison)
> and when the struct is translated from Java to UNO, it still looks good
> (IMHO), search for "STRUCT top-level". Then the "f1" and "f2" prints from
> right after
> https://git.libreoffice.org/core/+/refs/heads/master/bridges/source/cpp_uno/gcc3_linux_powerpc64/uno2cpp.cxx#218
> they are bad.
>
> I will look further especially at the dynamically generated stubs,
> which is new to me. Apply those stubs to the C++ bridge as well?
rough guess, but we might be missing something like
https://git.libreoffice.org/core/+/refs/heads/master/bridges/source/cpp_uno/gcc3_linux_aarch64/cpp2uno.cxx#352
Dan
[Libreoffice-bugs] [Bug 150915] [META] Windows Dark Mode bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=150915 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on|157365 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=157365 [Bug 157365] Changing default fonts forces page color to display as white, in dark mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142074] [META] Application Colours settings bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=142074 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||157365 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=157365 [Bug 157365] Changing default fonts forces page color to display as white, in dark mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157365] Changing default fonts forces page color to display as white, in dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=157365 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks|150915 |142074 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=142074 [Bug 142074] [META] Application Colours settings bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=150915 [Bug 150915] [META] Windows Dark Mode bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
