[Libreoffice-bugs] [Bug 155865] EDITING: Crash in vtableCall
https://bugs.documentfoundation.org/show_bug.cgi?id=155865 --- Comment #12 from Julien Nabet --- A new daily build is available here: https://dev-builds.libreoffice.org/daily/master/Win-Arm64@tb77-TDF/current/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 95476] FILESAVE Export to xhtml shows display:condition; for section, which is defined as displayed with condition
https://bugs.documentfoundation.org/show_bug.cgi?id=95476 --- Comment #13 from Robert Großkopf --- Bug still exists in LO 7.5.4.2 on OpenSUSE 15.4 64bit rpm Linux. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155850] pasting multiple of the same emoji makes them overlap
https://bugs.documentfoundation.org/show_bug.cgi?id=155850 Dieter changed: What|Removed |Added CC||dgp-m...@gmx.de Whiteboard| QA:needsComment| Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155858] PRINTING on Super B landscape has wide L/R margins
https://bugs.documentfoundation.org/show_bug.cgi?id=155858 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 156093] XHTML-Export: White background of caption will be shown as blue background
https://bugs.documentfoundation.org/show_bug.cgi?id=156093 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155859] Insert hyperlinks to positions in current document is more tedious that it needs to be
https://bugs.documentfoundation.org/show_bug.cgi?id=155859 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 155861] Quick parts or autotext are not being filled.
https://bugs.documentfoundation.org/show_bug.cgi?id=155861 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 155845] Security Warning for disabling macros: Enable Macros doesn't execute macros at event "View Created"
https://bugs.documentfoundation.org/show_bug.cgi?id=155845 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 155856] Port C++ SDK examples make files to cmake / qmake
https://bugs.documentfoundation.org/show_bug.cgi?id=155856 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 155850] pasting multiple of the same emoji makes them overlap
https://bugs.documentfoundation.org/show_bug.cgi?id=155850 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 155897] Inconsistency concerning the deletion of single empty paragraph below TextTable
https://bugs.documentfoundation.org/show_bug.cgi?id=155897 --- Comment #3 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155772] Japanese, vertical CTL text: some pasted text displayed incorrectly
https://bugs.documentfoundation.org/show_bug.cgi?id=155772 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 154479] Writer don't attach the document when using the attach at email button
https://bugs.documentfoundation.org/show_bug.cgi?id=154479 --- Comment #14 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113363] [META] DOCX (OOXML) content control-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=113363 Bug 113363 depends on bug 152164, which changed state. Bug 152164 Summary: Use the same background and style for content control and other fields' placeholder text https://bugs.documentfoundation.org/show_bug.cgi?id=152164 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107739] [META] Field bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107739 Bug 107739 depends on bug 152164, which changed state. Bug 152164 Summary: Use the same background and style for content control and other fields' placeholder text https://bugs.documentfoundation.org/show_bug.cgi?id=152164 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152164] Use the same background and style for content control and other fields' placeholder text
https://bugs.documentfoundation.org/show_bug.cgi?id=152164 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 152326] wrong month sort in pivot table
https://bugs.documentfoundation.org/show_bug.cgi?id=152326 --- Comment #3 from QA Administrators --- Dear John Hopkins, 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 152164] Use the same background and style for content control and other fields' placeholder text
https://bugs.documentfoundation.org/show_bug.cgi?id=152164 --- Comment #8 from QA Administrators --- Dear Hossein, 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 149684] converting .docx to .pdf - but not all pages and also two pages merged into same page in pdf
https://bugs.documentfoundation.org/show_bug.cgi?id=149684 --- Comment #7 from QA Administrators --- Dear prasadgsk, 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 152063] version 7.4.2 update won't run after installation
https://bugs.documentfoundation.org/show_bug.cgi?id=152063 --- Comment #4 from QA Administrators --- Dear shearist, 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 146461] LibreOffice Spreadsheet crash when clicking and dragging over formulas
https://bugs.documentfoundation.org/show_bug.cgi?id=146461 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146461] LibreOffice Spreadsheet crash when clicking and dragging over formulas
https://bugs.documentfoundation.org/show_bug.cgi?id=146461 --- Comment #20 from QA Administrators --- Dear Ken, 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 140156] Significant slow-down when entering two languages in the line
https://bugs.documentfoundation.org/show_bug.cgi?id=140156 --- Comment #6 from QA Administrators --- Dear elya.wygoda, 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 140156] Significant slow-down when entering two languages in the line
https://bugs.documentfoundation.org/show_bug.cgi?id=140156 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 140568] Allow page gutter position 'Right' for left pages
https://bugs.documentfoundation.org/show_bug.cgi?id=140568 --- Comment #8 from QA Administrators --- Dear Regina Henschel, 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 95476] FILESAVE Export to xhtml shows display:condition; for section, which is defined as displayed with condition
https://bugs.documentfoundation.org/show_bug.cgi?id=95476 --- Comment #12 from QA Administrators --- Dear Robert Großkopf, 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 90667] Problem with alignment in index / TOC in specific DOT (per Comment 10)
https://bugs.documentfoundation.org/show_bug.cgi?id=90667 --- Comment #15 from QA Administrators --- Dear gon_aranda, 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 136837] Fileopen and filesave to DOCX: Table Title not read and saved as Alt Text
https://bugs.documentfoundation.org/show_bug.cgi?id=136837 --- Comment #7 from QA Administrators --- Dear Timur, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142811] UI: Ruler grid inaccurate for tabstops in metric units
https://bugs.documentfoundation.org/show_bug.cgi?id=142811 --- Comment #2 from QA Administrators --- Dear mail2.0, 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 135352] Report Builder requires double entry of query parameter for Calc document type output when based on a query with required parameter input
https://bugs.documentfoundation.org/show_bug.cgi?id=135352 --- Comment #14 from QA Administrators --- Dear Dreamquartz, 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 131693] Unable to open document if path has "\\?\" UNC prefix in Windows
https://bugs.documentfoundation.org/show_bug.cgi?id=131693 --- Comment #3 from QA Administrators --- Dear Tomas, 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 118928] FILESAVE DOCX: Table loses set name after save
https://bugs.documentfoundation.org/show_bug.cgi?id=118928 --- Comment #8 from QA Administrators --- Dear Miloš Samek, 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 108074] Merged cells can overlap page break, and are displayed incorrectly
https://bugs.documentfoundation.org/show_bug.cgi?id=108074 --- Comment #10 from QA Administrators --- Dear Aron Budea, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107508] XY Chart auto scaling on X axis with only 1 data point generates excessive number of major units
https://bugs.documentfoundation.org/show_bug.cgi?id=107508 --- Comment #11 from QA Administrators --- Dear branestawm, 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 126006] Calc with Tabbed UI used to crash after File>>Reload; many toolbar items aren't working including save
https://bugs.documentfoundation.org/show_bug.cgi?id=126006 --- Comment #19 from ady --- (In reply to Justin L from comment #18) > *** Bug 151066 has been marked as a duplicate of this bug. *** I am not sure that bug 151066 should be considered as duplicate of bug 126006. If the crash that was reproduced in this bug 126006 is no longer so, but the behavior as described in bug 151066 still is, then this bug 126006 could be closed and bug 151066 could be kept opened, to be resolved. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155803] Can't do "undo" or "redo" for freezing actions
https://bugs.documentfoundation.org/show_bug.cgi?id=155803 --- Comment #4 from ady --- (In reply to AvidSeeker from comment #3) > Freezing action is a "real action" because it's saved to the .ods file. > Resizing window, zooming in, or zooming out are not saved because they're > only relevant for the current session, unlike freezing rows/cols. The cell/position, visible "home" cell/position, zoom factor, view grid and many other settings are saved in the file but do not add any item to the (potentially) "undo" list. Let's not get off-topic. We should leave this request for developer's evaluation. In the meantime, my question from comment 2 is still relevant: Are there other spreadsheet tools that behave differently? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156093] XHTML-Export: White background of caption will be shown as blue background
https://bugs.documentfoundation.org/show_bug.cgi?id=156093 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- Reproducible Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: default; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: f1b0aca6bf520626d3c9a1fac67cd2de2c10c78c CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145553] Improve UI on export of form-fillable pdfs, provide UI to set a suitable "PDF default" (now is Helevetica by default) and warn of subset for other user-selected (non-PD
https://bugs.documentfoundation.org/show_bug.cgi?id=145553 --- Comment #10 from Brenton Chapin --- I think you should reconsider. Firstly, I admire efficiency, of space. But that's not what PDF is about. As everyone who works with PDF knows, it is an absolutely terrible format if your goal is to save space. Go ahead and bloat the PDF file with an entire font, to support entry of any text characters. That's what Acrobat does, and it works. The forms fields can display any user entered character in any desired font. Every mainline PDF reader I have tested can show the entered text in the correct font. So, that's what LibreOffice should do too. And yes, the resulting PDFs are huge. Also, the LibreOffice native file format supports and preserves the use in text entry boxes of any font desired. It's a bit jarring to see such a form work within Writer, then fail to export identically to PDF. The whole reason for PDF is to preserve the exact look of a document, and when LibreOffice silently changes fonts, it breaks that expectation of PDF. Don't do that. At first, I wondered if the problem was a limitation of PDF. If you're still not convinced, what of the scenario in which both text and text entry fields are using the same non-default font? The PDF must already have the font embedded for the text, and in that case, adding in the unused glyphs to support their use in a text entry box wouldn't be that big an imposition, would it? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145988] macOS skia: colors not displayed correctly for all document previews e.g. start center or impress templates
https://bugs.documentfoundation.org/show_bug.cgi?id=145988 --- Comment #79 from Patrick Luby --- I saw that LibreOffice uses a much newer version of Skia. Has anyone who has experienced this bug tried the latest nightly master build? If yes, do you see any change good or bad? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146346] FILEOPEN: DOCX: paragraphs between the body and the footnote are gone
https://bugs.documentfoundation.org/show_bug.cgi?id=146346 Commit Notification changed: What|Removed |Added Whiteboard|target:7.4.0 target:7.3.4 |target:7.4.0 target:7.3.4 ||target:24.2.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 118335] Writer's Groupedbar. Print preview called "Close Preview" in drop-down menu File
https://bugs.documentfoundation.org/show_bug.cgi?id=118335 --- Comment #15 from Commit Notification --- Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/736cf835b9edb7a18fa52a12b03c252a9b63ff7c tdf#118335 use .uno:ClosePreview instead of PrintPreview It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 66791] FORMATTING: Incorrect application of "Asian text font" for quotation marks when the paragraph contains a mixture of western and asian characters
https://bugs.documentfoundation.org/show_bug.cgi?id=66791 --- Comment #25 from Volga --- Created attachment 188134 --> https://bugs.documentfoundation.org/attachment.cgi?id=188134=edit The same file opened with LibreOffice Writer Then this screenshot is made after the same file opened with LibreOffice Writer, note both two apps are zh-CN locale when I see them. So Khaled, what happened if you open this ODT in WordPad or MS Word? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 66791] FORMATTING: Incorrect application of "Asian text font" for quotation marks when the paragraph contains a mixture of western and asian characters
https://bugs.documentfoundation.org/show_bug.cgi?id=66791 --- Comment #24 from Volga --- Created attachment 188133 --> https://bugs.documentfoundation.org/attachment.cgi?id=188133=edit Screenshot on WordPad >From the last comment I found this test file by blog author https://yongweiwu.files.wordpress.com/2014/12/odf_test.odt Then I remembered WordPad, a native word processor in Windows, so let's see what happened on WordPad. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 85435] FILEOPEN: line spacing wrong in DOC file
https://bugs.documentfoundation.org/show_bug.cgi?id=85435 --- Comment #14 from Justin L --- In https://gerrit.libreoffice.org/c/core/+/152375 I suggest just reverting that part, but what do I know about the grid? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156091] BASIC IDE or Development Tools crash when expanding the + of 'Background' of master page
https://bugs.documentfoundation.org/show_bug.cgi?id=156091 Mike Kaganski changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |mikekagan...@hotmail.com |desktop.org | --- Comment #10 from Mike Kaganski --- (In reply to Julien Nabet from comment #9) Thank you! You made a great detective work, and provided ideas. I will take over. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148678] SECURITY: Connection of a database won't be closed when database has been closed
https://bugs.documentfoundation.org/show_bug.cgi?id=148678 Robert Großkopf changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #5 from Robert Großkopf --- Depending on commet3 and comment4 I will set this one to NEW. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156091] BASIC IDE or Development Tools crash when expanding the + of 'Background' of master page
https://bugs.documentfoundation.org/show_bug.cgi?id=156091 --- Comment #9 from Julien Nabet --- (In reply to Julien Nabet from comment #8) > ... > Started here https://gerrit.libreoffice.org/c/core/+/153772 Just for the record, I abandoned the patch since it's too much complicated for me. Hopefully, someone will be able to fix this properly :-) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155897] Inconsistency concerning the deletion of single empty paragraph below TextTable
https://bugs.documentfoundation.org/show_bug.cgi?id=155897 Wolfgang Jäger changed: What|Removed |Added CC||j...@psilosoph.de --- Comment #2 from Wolfgang Jäger --- Sorry! I wasn't clear enough about what's the inconsistency. Let me start completely anew. The full-grown text objects of a TextFrame or of a cell of a TextTable (badly presented as identical with the cell itself) can contain a TextTable object as the only or as the last (bottom) element of the text enumeration (paragraphs level). The text of the Writer model itself can not. Behind its last TextTable object (if any) there is always at least one paragraph. So, why worry? Users complained about the fact (in the ask site) that the described behaviour produces an unwanted page break and by that an empty trailing page under specific circumstances. The empty trailing paragraph goes to that page then. You see? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156066] [META] SVG filters
https://bugs.documentfoundation.org/show_bug.cgi?id=156066 --- Comment #4 from Commit Notification --- Xisco Fauli committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/74c9fd3ae5b63981fb256e019f0cf974329157f0 tdf#156066: Add support for feImage filter It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156087] Add an "all pages" view mode to Draw to scroll through all pages in canvas (without needing Page Pane)
https://bugs.documentfoundation.org/show_bug.cgi?id=156087 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org --- Comment #6 from V Stuart Foote --- Confirm that yes the sd canvas offers no multi-page view for Draw or Impress. But would note that is the normal workflow OOo evolved. A drawing canvas or a presentation slide is manipulated one at a time. The Page/Slide pane provides a sorter that compliments that workflow. Can not justify the dev effort that would be needed to provide a multi-page canvas view for either Draw or Impress as there is no workflow that requires the view. IMHO => WF Otherwise--to state the obvious--LibreOffice is not a PDF editor! We import via filter the elements making up the PDF publication and render them to document canvas. Depending on the import filter, we either parse content of the entire PDF into ODF drawing objects placed on multiple pages, or we parse the content of a single PDF page into a raster image placed onto a single ODF page. That is the difference between the internal LO Import and our Insert filters. The pdfium project based insert filter works one page at a time and currently only the first page. The import filters work against the entire PDF and renders the PDF pages as individual ODF drawing, presentation or text document pages (select the corresponding filter for the module needed). By default a PDF will filter import to Draw, pages of the PDF will render as drawing pages. Importing to Impress will render the PDF pages as presentation slides. The sd module's Pages or Slides pane give "filmstrip" style view of the page/slide previews. Once imported, you can delete a Draw page or Impress slide. When import to a Writer ODF text document, the drawing objects from the PDF will be placed onto document pages. Normal 'Single-page', 'Multi-page', and 'Book' view modes of the document are available familiar to other PDF readers. You can select and delete page content/pages from Writer as well. Additional work is needed for both import and insert filters to be able to select a range of pages from a PDF (e.g. bug 114234). While publishing document content back from LO to PDF is an entirely different set of print filters. And while you can overwrite the original PDF, it is ill-advised as it is highly destructive! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156099] New: Rename "rotation object" to "solid of revolution"
https://bugs.documentfoundation.org/show_bug.cgi?id=156099 Bug ID: 156099 Summary: Rename "rotation object" to "solid of revolution" Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: minor Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tuomas.hiet...@iki.fi Description: LO uses the term "rotation object" for 3D objects that are formed by rotating a 2D shape around an axis. However, that does not seem to be the usual English term for this kind of thing. The term "solid of revolution" is used instead: https://en.wikipedia.org/wiki/Solid_of_revolution "Rotation object" is possibly a literal translation from German: https://de.wikipedia.org/wiki/Rotationsk%C3%B6rper It would be better to use generally accepted English terms, though (unless there are other more important considerations). Steps to Reproduce: 1. See https://translations.documentfoundation.org/languages/en/libo_ui-master/search/?offset=1=rotation+object_by=-priority%2Cposition= Actual Results: Uncommon English terminology is used. Expected Results: Commonly accepted English terminology is used. Reproducible: Always User Profile Reset: No Additional Info: n/a -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139306] UI: numerical string in formula bar (input line) and cell editing truncated (to 20 digits)
https://bugs.documentfoundation.org/show_bug.cgi?id=139306 --- Comment #8 from Mike Kaganski --- (In reply to Vladislav Tarakanov from comment #7) The "E-14" comes from the implementation of rtl_math_StringFormat_Automatic (see its logic in the same function), where it tries to choose the "optimal" representation of a number. See how it uses the number magnitude to switch between rtl_math_StringFormat_E (when the magnitude is <= -15 or >= 15), and rtl_math_StringFormat_F (when the magnitude is inside the bounds). So - is it this calculation that you intend to improve? Note that this will not help in cases when rtl_math_StringFormat_F is chosen explicitly, in which case, the switching will not happen, and any number, including E-300, will still be output using leading zeroes (and indeed, significands will be cut off). I would recommend you to look at the "nOrigDigits", which shows the count of significant digits in the decimal representation (without any leading/trailing zeroes). You could consider it in combination with magnitude in case of the _F format; but note that you must then pay attention to how the buffer size is calculated, to avoid buffer overflow. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 116253] With MariaDB JDBC connection & Filter property set, an empty Combo Box shows 'NULL' when record inserted
https://bugs.documentfoundation.org/show_bug.cgi?id=116253 Adam664 changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||8678 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148678] SECURITY: Connection of a database won't be closed when database has been closed
https://bugs.documentfoundation.org/show_bug.cgi?id=148678 Adam664 changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||6253 CC||adamsesku...@gmail.com --- Comment #4 from Adam664 --- Confirming the behavior exits with: Version: 7.5.3.2 (X86_64) Build ID: 50(Build:2) CPU threads: 1; OS: Linux 6.3; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded and Version: 7.7.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 5a2c6f4df7149f8c1f543f120fe19bd66abfc189 CPU threads: 1; OS: Linux 6.3; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Not sure if this is the desired behavior or not, maybe someone with more experience can chime in? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139306] UI: numerical string in formula bar (input line) and cell editing truncated (to 20 digits)
https://bugs.documentfoundation.org/show_bug.cgi?id=139306 --- Comment #7 from Vladislav Tarakanov --- Maybe I really miscalculated. 14: E-14 is the last degree value after which a number from 0.123456 starts to be displayed as 0.654321E-15 in the edit line. When E-14 is entered, the output line will display the value normally, with 13 zeros before numbers. 22: Counted again, 15 numbers after the decimal point are displayed + 5 trailing zeros behind them. This is the count of characters that can be displayed after the zeros behind the decimal separator. Then it turns out that up to 28 characters after the separator can be displayed: 13 zeros and 15 digits -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156091] BASIC IDE or Development Tools crash when expanding the + of 'Background' of master page
https://bugs.documentfoundation.org/show_bug.cgi?id=156091 --- Comment #8 from Julien Nabet --- (In reply to Mike Kaganski from comment #7) > ... > I suggest you to start, and we could proceed with discussing a gerrit > change. Thank you! Started here https://gerrit.libreoffice.org/c/core/+/153772 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 101216] [META] Calc comment bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=101216 Bug 101216 depends on bug 73537, which changed state. Bug 73537 Summary: Comments in Calc don't show author and date unlike Writer https://bugs.documentfoundation.org/show_bug.cgi?id=73537 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132932] Strings that need pluralization via ngettext
https://bugs.documentfoundation.org/show_bug.cgi?id=132932 --- Comment #5 from Tuomas Hietala --- This could be an easyhack I guess? A couple of cases here: https://git.libreoffice.org/core/+/master/filter/inc/strings.hrc#41 https://git.libreoffice.org/core/+/master/filter/inc/strings.hrc#44 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139306] UI: numerical string in formula bar (input line) and cell editing truncated (to 20 digits)
https://bugs.documentfoundation.org/show_bug.cgi?id=139306
--- Comment #6 from Mike Kaganski ---
(In reply to Vladislav Tarakanov from comment #5)
> We got the number 36 from the sum of two values: the count of characters
> displayed before 'E' in cells (22) and the maximum count of the degree,
> after which 'E' will also appear in the edit line ('E-14'). The maximum can
> be 14 zeros + 22 numbers after the decimal point.
First of all, the function is not specific to cells. It is a generic function,
and may be used anywhere, e.g. in file format output, or in Basic.
Now what is "22"? what is "14"? I don't quite understand it. In Calc, we only
allow up to 15 significant decimals shown, even if you increase decimal count
to 20 (I *suspect* that 22 might be like "a zero plus a decimal separator plus
20 decimals").
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155902] writer crashes regularly after updating to dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=155902 jim hamilton changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #9 from jim hamilton --- It appears the Libre Writer crash scenario has stopped though the deactivation of Skia. Thanks! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139306] UI: numerical string in formula bar (input line) and cell editing truncated (to 20 digits)
https://bugs.documentfoundation.org/show_bug.cgi?id=139306
--- Comment #5 from Vladislav Tarakanov ---
(In reply to Mike Kaganski from comment #4)
> (In reply to Vladislav Tarakanov from comment #3)
>
> Yes, you found the correct line. The question is: what change do you
> suggest? Simply increasing the value from 20 to 36 (why 36? we only show up
> to 15 significant decimals) is not reasonable, because the next would be a
> report about a number with 20 leading zeroes instead of 10. Do you have a
> reasonable algorithm to find the needed count of total output decimals?
We got the number 36 from the sum of two values: the count of characters
displayed before 'E' in cells (22) and the maximum count of the degree, after
which 'E' will also appear in the edit line ('E-14'). The maximum can be 14
zeros + 22 numbers after the decimal point.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156087] Add an "all pages" view mode to Draw to scroll through all pages in canvas (without needing Page Pane)
https://bugs.documentfoundation.org/show_bug.cgi?id=156087 Stéphane Guillou (stragu) changed: What|Removed |Added Hardware|x86-64 (AMD64) |All URL||https://ask.libreoffice.org ||/t/multiple-page-view-in-lo ||-drawing/75952 Severity|normal |enhancement CC||libreoffice-ux-advise@lists ||.freedesktop.org Summary|LibreOffice Draw - .pdfs|Add an "all pages" view |Only Showing First Page |mode to Draw to scroll ||through all pages in canvas ||(without needing Page Pane) OS|Windows (All) |All Keywords||needsUXEval Version|7.5.4.2 release |Inherited From OOo --- Comment #5 from Stéphane Guillou (stragu) --- The way to navigate pages in Draw is to use the Page Pane. It is a diagram / drawing editor, and the PDF import is only secondary. (The "1:1" in the status bar is the scaling factor, not the page count.) If you want a continuous view of the pages, you can import the PDF into Writer: - Open LO - Open... > choose the "PDF (Writer)" filter in the dropdown, pick your file. However, and regardless of PDF import or not, I see others asking for a similar feature or who would benefit from one: - https://www.reddit.com/r/libreoffice/comments/fh27wz/draw_see_all_pages_at_once/ - https://ask.libreoffice.org/t/multiple-page-view-in-lo-drawing/75952 - https://ask.libreoffice.org/t/in-draw-i-have-a-6-page-document-but-it-only-lets-me-see-1-page-i-may-of-clicked-on-something-and-now-cannot-see-the-whole-document/46606 - https://ask.libreoffice.org/t/how-can-i-see-and-edit-two-pages-in-draw/13635 - https://forum.openoffice.org/en/forum/viewtopic.php?t=98595 So I'll copy the Design team in to have their opinion on an enhancement request. I thought I would find a duplicate but couldn't. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139306] UI: numerical string in formula bar (input line) and cell editing truncated (to 20 digits)
https://bugs.documentfoundation.org/show_bug.cgi?id=139306 --- Comment #4 from Mike Kaganski --- (In reply to Vladislav Tarakanov from comment #3) Yes, you found the correct line. The question is: what change do you suggest? Simply increasing the value from 20 to 36 (why 36? we only show up to 15 significant decimals) is not reasonable, because the next would be a report about a number with 20 leading zeroes instead of 10. Do you have a reasonable algorithm to find the needed count of total output decimals? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154477] Color attribute set by colorscale conditional format not copied to HTML
https://bugs.documentfoundation.org/show_bug.cgi?id=154477 --- Comment #10 from Commit Notification --- Henry Castro committed a patch related to this issue. It has been pushed to "libreoffice-7-5": https://git.libreoffice.org/core/commit/87d1e49f0cdbff6023bc6083a561c96192eb1eed tdf#154477: sc: filter: html: fix missing color scale conditional format It will be available in 7.5.5. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154477] Color attribute set by colorscale conditional format not copied to HTML
https://bugs.documentfoundation.org/show_bug.cgi?id=154477 --- Comment #9 from Commit Notification --- Henry Castro committed a patch related to this issue. It has been pushed to "libreoffice-7-5": https://git.libreoffice.org/core/commit/e4010b7d83244d9d51f36e22c9d9cd63eda870cb tdf#154477: sc: add "updateValues" method to conditional format list It will be available in 7.5.5. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154477] Color attribute set by colorscale conditional format not copied to HTML
https://bugs.documentfoundation.org/show_bug.cgi?id=154477 --- Comment #8 from Commit Notification --- Henry Castro committed a patch related to this issue. It has been pushed to "libreoffice-7-5": https://git.libreoffice.org/core/commit/284ac82b1af70c8734bae6eb841ae01735bb6b41 tdf#154477: sc: copy cache values when clone color conditional format It will be available in 7.5.5. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154477] Color attribute set by colorscale conditional format not copied to HTML
https://bugs.documentfoundation.org/show_bug.cgi?id=154477 Commit Notification changed: What|Removed |Added Whiteboard|target:7.6.0|target:7.6.0 target:7.5.5 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102062] [META] Notebookbar: bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102062 Bug 102062 depends on bug 126130, which changed state. Bug 126130 Summary: .uno:Heading1ParaStyle not working in Notebookbar .ui files https://bugs.documentfoundation.org/show_bug.cgi?id=126130 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 126130] .uno:Heading1ParaStyle not working in Notebookbar .ui files
https://bugs.documentfoundation.org/show_bug.cgi?id=126130 Justin L changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #7 from Justin L --- It seems to work for me. I used Heading1ParaStyle in MenuFile - and it showed up (with a checkbox) and worked. I used Heading1ParaStyle in File- and it showed up and worked -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139306] UI: numerical string in formula bar (input line) and cell editing truncated (to 20 digits)
https://bugs.documentfoundation.org/show_bug.cgi?id=139306 --- Comment #3 from Vladislav Tarakanov --- This error is still reproducible. Check with: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 160ea29f0003812ab1d4e1f6689c608c879ef509 CPU threads: 12; OS: Linux 6.1; UI render: default; VCL: gtk3 Locale: ru-RU (ru_RU.UTF-8); UI: en-US Calc: CL threaded It seems that we have found a solution to this problem. To do this, when casting a double value to a string, it was necessary to add an additional count of characters after the decimal point (now 20, in local build the error is corrected at 36) The line that was changed has the note "we don't want to allocate/deallocate 2GB just to fill it with trailing '0' characters". We would like to first discuss with other developers the correctness of such changes in the code -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140140] WRITER Notebookbar configuration window allows for drag and drop, but this has no effect and is reverted once OK is pressed
https://bugs.documentfoundation.org/show_bug.cgi?id=140140 Justin L changed: What|Removed |Added OS|Windows (All) |All -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141135] GTK3 version: in tabbed, tabbed compact, and groupedbar compact toolbar modes, the menu entries to switch between Normal and Web view modes are checkboxes instead of ra
https://bugs.documentfoundation.org/show_bug.cgi?id=141135 --- Comment #6 from Justin L --- Anything that toggles appears to be treated as a checkbox in NBB. For example uno:PrintPreview. So probably something inherent in the NBB design itself. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144839] Cannot access certain options (AutoCorrect/Trend Lines/Horizontal Lines) in Tabbed interface
https://bugs.documentfoundation.org/show_bug.cgi?id=144839 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||1137 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141137] "AutoCorrect" submenu (and autocorrect options) are missing from the Groupedbar Compact and Tabbed toolbars
https://bugs.documentfoundation.org/show_bug.cgi?id=141137 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||4839 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 126006] Calc with Tabbed UI used to crash after File>>Reload; many toolbar items aren't working including save
https://bugs.documentfoundation.org/show_bug.cgi?id=126006 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||6758 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146758] Option to Reload a document is missing with Notebookbar enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=146758 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||6006 --- Comment #9 from Justin L --- Note that bug 126006 indicates that doing this in Calc is a bad idea... -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152357] Show "more options" symbol also in the tabs (requesting for something like MS Word's paragraph properties)
https://bugs.documentfoundation.org/show_bug.cgi?id=152357 Justin L changed: What|Removed |Added Summary|Show "more options" symbol |Show "more options" symbol |also in the tabs|also in the tabs ||(requesting for something ||like MS Word's paragraph ||properties) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 126006] Calc with Tabbed UI used to crash after File>>Reload; many toolbar items aren't working including save
https://bugs.documentfoundation.org/show_bug.cgi?id=126006 Justin L changed: What|Removed |Added Summary|Calc with Tabbed UI crashes |Calc with Tabbed UI used to |on Autofilter icon after|crash after File>>Reload; |File>>Reload if you had |many toolbar items aren't |autofilter on in the old|working including save |document| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107237] [META] Notebookbar Tabbed
https://bugs.documentfoundation.org/show_bug.cgi?id=107237 Bug 107237 depends on bug 151066, which changed state. Bug 151066 Summary: [SAVING][UI] Tabbed toolbar Data Loss after file Reload; icons don't work either https://bugs.documentfoundation.org/show_bug.cgi?id=151066 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 126006] Calc with Tabbed UI crashes on Autofilter icon after File>>Reload if you had autofilter on in the old document
https://bugs.documentfoundation.org/show_bug.cgi?id=126006 Justin L changed: What|Removed |Added CC||jebsoluti...@gmail.com --- Comment #18 from Justin L --- *** Bug 151066 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151066] [SAVING][UI] Tabbed toolbar Data Loss after file Reload; icons don't work either
https://bugs.documentfoundation.org/show_bug.cgi?id=151066 Justin L changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #11 from Justin L --- *** This bug has been marked as a duplicate of bug 126006 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144839] Cannot access certain options (AutoCorrect/Trend Lines/Horizontal Lines) in Tabbed interface
https://bugs.documentfoundation.org/show_bug.cgi?id=144839 Justin L changed: What|Removed |Added Summary|Cannot access certain |Cannot access certain |options in Tabbed interface |options (AutoCorrect/Trend ||Lines/Horizontal Lines) in ||Tabbed interface -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107237] [META] Notebookbar Tabbed
https://bugs.documentfoundation.org/show_bug.cgi?id=107237 Bug 107237 depends on bug 144366, which changed state. Bug 144366 Summary: LO crashes when text in search field is entered in Tabbed and Tabbed Compact UI https://bugs.documentfoundation.org/show_bug.cgi?id=144366 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144366] LO crashes when text in search field is entered in Tabbed and Tabbed Compact UI
https://bugs.documentfoundation.org/show_bug.cgi?id=144366 Justin L changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103239] [META] Toolbars bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103239 Timur changed: What|Removed |Added Depends on|156097 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156097 [Bug 156097] Impress: Vertical Text missing as Insert menu item in Classic UI -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156097] Impress: Vertical Text missing as Insert menu item in Classic UI
https://bugs.documentfoundation.org/show_bug.cgi?id=156097 Timur changed: What|Removed |Added Blocks|103239 |84909 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=84909 [Bug 84909] [META] Enhancing Impress/Draw toolbars and context menu https://bugs.documentfoundation.org/show_bug.cgi?id=103239 [Bug 103239] [META] Toolbars bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 84909] [META] Enhancing Impress/Draw toolbars and context menu
https://bugs.documentfoundation.org/show_bug.cgi?id=84909 Timur changed: What|Removed |Added Depends on||156097 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156097 [Bug 156097] Impress: Vertical Text missing as Insert menu item in Classic UI -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145553] Improve UI on export of form-fillable pdfs, provide UI to set a suitable "PDF default" (now is Helevetica by default) and warn of subset for other user-selected (non-PD
https://bugs.documentfoundation.org/show_bug.cgi?id=145553 V Stuart Foote changed: What|Removed |Added CC||kha...@libreoffice.org, ||vmik...@collabora.com --- Comment #9 from V Stuart Foote --- (In reply to Brenton Chapin from comment #8) > I reported bug 143110 which was tagged as a duplicate of this bug. Per the > request in bug 126687 that 143110 was mistakenly tagged as duplicating, I > tested for the problem again. As of 7.5.4.2, it is still not working. > > In 143110, I said why it wasn't working: support for different fonts for > text entry fields was never implemented. LibreOffice still does and will > still always uses Helvetica for text entry fields in PDF forms until support > for different fonts is implemented. Fixing it could be as simple as using > the existing code that embeds the fonts used for text in plain PDFs. This is the correct BZ issue and is intentional, see comment 3 here and discussion on bug 50879 as resolved [1]. Issue is not the embedding. Rather that PDF do not embed full font's, just subsets (and even then those are not installable). Meaning, authoring a PDF form with fields that can not be filled makes no sense--to ensure a form can be filled the PDF export filter changes font used for fields to PDF "standard" compliant font that "should" be available to the PDF reader in use. Normally Helvetica, but it will respond to font family selection made in Writer. Meaning--still up to the form designer to select a suitable [2] font in Writer if they need WYSIWYG for the form. Of course YMMV with os/DE font fallback handling of the output from the PDF reader. Potential to refactor (major dev effort), but as noted project approach is to acknowledge that incomplete subsetting leads to useless forms (or bloated PDF with a full font) and instead to use one of the core 14 PDF fonts defined by Adobe--so that any reader/form filler will accommodate. We can't/shouldn't do more than that. But what is still needed, for UX, is missing UI feedback to author when exporting to form from Writer that they are exporting a form designed with fillable fields without font support. @Miklos, Khaled -- anything to add? =-ref-= [1] https://gerrit.libreoffice.org/c/core/+/99032 [2] Fixed Pitch Fonts Courier Courier-Bold Courier-Oblique Courier-BoldOblique Proportional Fonts Helvetica Helvetica-Bold Helvetica-Oblique Helvetica-BoldOblique Times-Roman Times-Bold Times-Italic Times-BoldItalic Symbol ZapfDingbats -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156097] Impress: Vertical Text missing as Insert menu item in Classic UI
https://bugs.documentfoundation.org/show_bug.cgi?id=156097 Timur changed: What|Removed |Added Summary|Vertical Text missing as|Impress: Vertical Text |Insert menu item in Classic |missing as Insert menu item |UI |in Classic UI Blocks||103239 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103239 [Bug 103239] [META] Toolbars bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103239] [META] Toolbars bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103239 Timur changed: What|Removed |Added Depends on||156097 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156097 [Bug 156097] Impress: Vertical Text missing as Insert menu item in Classic UI -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107237] [META] Notebookbar Tabbed
https://bugs.documentfoundation.org/show_bug.cgi?id=107237 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||156098 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156098 [Bug 156098] Writer: "Insert - Page number" button missing in Tabbed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156098] Writer: "Insert - Page number" button missing in Tabbed
https://bugs.documentfoundation.org/show_bug.cgi?id=156098 Stéphane Guillou (stragu) changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=15 | |5374| Blocks||107237 Depends on||155374 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107237 [Bug 107237] [META] Notebookbar Tabbed https://bugs.documentfoundation.org/show_bug.cgi?id=155374 [Bug 155374] Icons needed for new Uno command PageNumberWizard -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156098] Writer: "Insert - Page number" button missing in Tabbed
https://bugs.documentfoundation.org/show_bug.cgi?id=156098 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||5374 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156098] Writer: "Insert - Page number" button missing in Tabbed
https://bugs.documentfoundation.org/show_bug.cgi?id=156098 --- Comment #1 from Timur --- There is a patch but needs icon: https://gerrit.libreoffice.org/c/core/+/151398. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141720] Add Gutter Margin in Page Margin drop down menu of layout tab of Tabbed interface
https://bugs.documentfoundation.org/show_bug.cgi?id=141720 Justin L changed: What|Removed |Added CC||jl...@mail.com Assignee|libreoffice-b...@lists.free |jl...@mail.com |desktop.org | Status|NEW |ASSIGNED --- Comment #4 from Justin L --- At best, I could see adding a "more options" (same as Page Size/Columns). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156091] BASIC IDE or Development Tools crash when expanding the + of 'Background' of master page
https://bugs.documentfoundation.org/show_bug.cgi?id=156091 --- Comment #7 from Mike Kaganski --- (In reply to Julien Nabet from comment #6) > shouldn't we create SDRATTR_TEXTCOLUMNS and then use it in > include/svx/svddef.hxx > ... > 238 constexpr TypedWhichId > SSDRATTR_TEXTCOLUMNS (SDRATTR_MISC_FIRST +27); // 1096 I suppose text columns wouldn't be an On Off Item. I don't remember it clearly, but my first instinct would be to try to mimic what SvxXTextColumns::getPropertyValue does with this WID, and proceed with implementation of columns support in the Draw styles. I suggest you to start, and we could proceed with discussing a gerrit change. Thank you! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156098] Writer: "Insert - Page number" button missing in Tabbed
https://bugs.documentfoundation.org/show_bug.cgi?id=156098 Timur changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=86 ||630 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156098] New: Writer: "Insert - Page number" button missing in Tabbed
https://bugs.documentfoundation.org/show_bug.cgi?id=156098 Bug ID: 156098 Summary: Writer: "Insert - Page number" button missing in Tabbed Product: LibreOffice Version: 24.2.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ti...@libreoffice.org Writer: "Insert - Page number" button is in Classic but missing in Tabbed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156091] BASIC IDE or Development Tools crash when expanding the + of 'Background' of master page
https://bugs.documentfoundation.org/show_bug.cgi?id=156091
Julien Nabet changed:
What|Removed |Added
CC||mikekagan...@hotmail.com
--- Comment #6 from Julien Nabet ---
Noticing property name "TextColumns", I noticed it's been added with:
95ebd24a629b4c8cd62cc20c0701683512cc8fa0
"editengine-columns: ODF support [API CHANGE]
This uses existing ODF markup, as used by Writer's text frame:
style::columns child element of style:graphic-properties, its
fo:column-count and fo:column-gap attributes. No ODF extension
is required.
Since currently only columns with same width and spacing are
implemented, without additional settings, style:column child
elements are exported, but ignored on import.
This adds new property to css::drawing::TextProperties service:
TextColumns (of type css::text::XTextColumns)."
in 2021/05
Mike: I noticed this part:
{ u"TextColumns", OWN_ATTR_TEXTCOLUMNS,
cppu::UnoType::get(), 0, 0 }
shouldn't we create SDRATTR_TEXTCOLUMNS and then use it in
include/svx/svddef.hxx
to replace:
237 constexpr TypedWhichId
SDRATTR_TEXT_CLIPVERTOVERFLOW (SDRATTR_MISC_FIRST +26); // 1095
238 constexpr sal_uInt16 SDRATTR_MISC_LAST
(SDRATTR_TEXT_CLIPVERTOVERFLOW); // 1095
by:
237 constexpr TypedWhichId
SDRATTR_TEXT_CLIPVERTOVERFLOW (SDRATTR_MISC_FIRST +26); // 1095
238 constexpr TypedWhichId SSDRATTR_TEXTCOLUMNS
(SDRATTR_MISC_FIRST +27); // 1096
239 constexpr sal_uInt16 SDRATTR_MISC_LAST
(SDRATTR_TEXTCOLUMNS); // 1096
I thought about a patch starting to write a patch from this, what do you think?
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141457] Statistics button doesn't works in Calc's tabbed compact UI
https://bugs.documentfoundation.org/show_bug.cgi?id=141457 Justin L changed: What|Removed |Added Hardware|x86-64 (AMD64) |All -- You are receiving this mail because: You are the assignee for the bug.
