[Libreoffice-bugs] [Bug 109251] FILEOPEN, DOC: Rows in certain tables have wrong height in the attached doc
https://bugs.documentfoundation.org/show_bug.cgi?id=109251 --- Comment #8 from Aron Budea --- Still in LO 7.6.0.0.alpha0+ (250b820a24640a33d73a6e690e04e36be01cda28) / Ubuntu. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154399] FILEOPEN PPTX: table cells renders differently due to missing word break (unless manually enabling hyphenation)
https://bugs.documentfoundation.org/show_bug.cgi?id=154399 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 154737] Mac forces printing in landscape mode
https://bugs.documentfoundation.org/show_bug.cgi?id=154737 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 154268] CALC - Export to(X)HTML should have option to format output
https://bugs.documentfoundation.org/show_bug.cgi?id=154268 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 154390] autohide toolbars
https://bugs.documentfoundation.org/show_bug.cgi?id=154390 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 154737] Mac forces printing in landscape mode
https://bugs.documentfoundation.org/show_bug.cgi?id=154737 --- 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 150590] 文件列印顏色錯誤
https://bugs.documentfoundation.org/show_bug.cgi?id=150590 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 99630] LO5 HTML editor does not split/merge lines in HTML to fit max line size (as done in LO3 and LO4)
https://bugs.documentfoundation.org/show_bug.cgi?id=99630 --- Comment #5 from QA Administrators --- Dear matta2006, 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 150590] 文件列印顏色錯誤
https://bugs.documentfoundation.org/show_bug.cgi?id=150590 --- Comment #4 from QA Administrators --- Dear 陳榮聰, 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 150154] Axis Format in Libre Office Calc Does Not Change
https://bugs.documentfoundation.org/show_bug.cgi?id=150154 --- Comment #6 from QA Administrators --- Dear Emory, 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 149925] Changes color of text in Excel files from "Red" to "Orange".
https://bugs.documentfoundation.org/show_bug.cgi?id=149925 --- Comment #6 from QA Administrators --- Dear mindunder36, 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 148754] bug - libreoffice portable math [Polish] - bad characters
https://bugs.documentfoundation.org/show_bug.cgi?id=148754 --- Comment #6 from QA Administrators --- Dear forrest1, 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 96102] FILEOPEN: LibO hangs with 100% CPU when loading an .html incorrectly labeled as .doc
https://bugs.documentfoundation.org/show_bug.cgi?id=96102 --- Comment #6 from QA Administrators --- Dear Christian Uceda, 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 89151] UI: Newly reassigned menu shortcut can lead to data loss
https://bugs.documentfoundation.org/show_bug.cgi?id=89151 --- Comment #7 from QA Administrators --- Dear tdfb, 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 66333] formula corrupted on creation in LibO Math (Formula Editor)
https://bugs.documentfoundation.org/show_bug.cgi?id=66333 --- Comment #11 from QA Administrators --- Dear Yury, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141588] FILEOPEN XLSX Cell borders missing
https://bugs.documentfoundation.org/show_bug.cgi?id=141588 --- Comment #4 from QA Administrators --- Dear Buovjaga, 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 136653] Update styles & formatting sidebar when then focus enters the document area
https://bugs.documentfoundation.org/show_bug.cgi?id=136653 --- 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 133923] File-Export to image only exports text and not chart
https://bugs.documentfoundation.org/show_bug.cgi?id=133923 --- Comment #11 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 127210] DDE function breaks if Item/range parameter is from another cell
https://bugs.documentfoundation.org/show_bug.cgi?id=127210 --- Comment #13 from QA Administrators --- Dear Bernard, 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 124273] Writer's chart preview shows wrong font size until edited
https://bugs.documentfoundation.org/show_bug.cgi?id=124273 --- Comment #7 from QA Administrators --- Dear Martin Kofahl, 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 121301] FILEOPEN DOCX Writer unable to recognize the font when it is defined as “Times New Roman félkövér” (Times New Roman Bold)
https://bugs.documentfoundation.org/show_bug.cgi?id=121301 --- Comment #8 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 119944] Writer does not resolve some/most HTML entities.
https://bugs.documentfoundation.org/show_bug.cgi?id=119944 --- Comment #8 from QA Administrators --- Dear Jens Troeger, 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 107582] FILESAVE: DOC gradient background is not supported in export
https://bugs.documentfoundation.org/show_bug.cgi?id=107582 --- Comment #8 from QA Administrators --- Dear Xisco Faulí, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109251] FILEOPEN, DOC: Rows in certain tables have wrong height in the attached doc
https://bugs.documentfoundation.org/show_bug.cgi?id=109251 --- Comment #7 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 116088] Export to XHTML issue with numbering in multi-columns sections
https://bugs.documentfoundation.org/show_bug.cgi?id=116088 --- Comment #5 from QA Administrators --- Dear Philippe Laugier, 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 106561] Transparent image saved in ms word format is not transparent when opened in MS Word.
https://bugs.documentfoundation.org/show_bug.cgi?id=106561 --- Comment #11 from QA Administrators --- Dear Jeff Martin, 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 151474] Allow formatting footnotes in columns or separated by spaces
https://bugs.documentfoundation.org/show_bug.cgi?id=151474 --- Comment #8 from Seán Ó Séaghdha --- How can it be reproduced when it’s an enhancement, i.e. something that cannot be done currently? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154739] New: Spelling correction
https://bugs.documentfoundation.org/show_bug.cgi?id=154739 Bug ID: 154739 Summary: Spelling correction Product: LibreOffice Version: 7.5.2.2 release Hardware: IA64 (Itanium) OS: Windows (All) Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: dgreus...@gmail.com Description: Spelling correction Since several versions, a right click on a word with a spelling error and then the choice "Corregir siempre como" (Always correct as?), deletes the word from the text instead of saving the automatic correction. Windows 10 and 11 Steps to Reproduce: 1. word with a spelling error 2. right click 3. choice "Corregir siempre como" Actual Results: deletes the word from the text Expected Results: saving the automatic correction Reproducible: Always User Profile Reset: Yes Additional Info: [Information automatically included from LibreOffice] Locale: es Module: TextDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: YES (not detected by Libre office) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140032] Double-line cell borders not exported to XLSX and XLS
https://bugs.documentfoundation.org/show_bug.cgi?id=140032 --- Comment #17 from ady --- (In reply to ady from comment #16) > This part (exporting XML) still needs a solution. That's a new report, bug 154738 now. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140032] Double-line cell borders not exported to XLSX and XLS
https://bugs.documentfoundation.org/show_bug.cgi?id=140032 ady changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4738 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154738] New: Double-line cell borders not exported to XML
https://bugs.documentfoundation.org/show_bug.cgi?id=154738 Bug ID: 154738 Summary: Double-line cell borders not exported to XML Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: adylo811...@gmail.com Spin-off of https://bugs.documentfoundation.org/show_bug.cgi?id=140032#c14 Creating an ods file with: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 67bb7f71b785d3d831ffaa47262b6cbd84e71c42 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (es_AR); UI: en-US Calc: threaded Built 2023-03-25 ...containing cells with double border style and width of 1.5pt. Exporting from LO as xml and opening it in LO and in Excel online > both show the xml file incorrectly, especially when testing a range of contiguous cells (as opposed to testing one cell alone, which fails too). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140032] Double-line cell borders not exported to XLSX and XLS
https://bugs.documentfoundation.org/show_bug.cgi?id=140032 --- Comment #16 from ady --- (In reply to ady from comment #14) > Warning / note: > > Exporting from LO as xml and opening it in LO and in Excel online > both > show the xml file incorrectly, especially when testing a range of contiguous > cells (as opposed to testing one cell alone, which fails too). This part (exporting XML) still needs a solution. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154721] Jalali Calendar does not work correct in Libre office calc
https://bugs.documentfoundation.org/show_bug.cgi?id=154721
--- Comment #4 from ady ---
Without knowing specifics about Persian Calendar, here is the test I performed.
Starting with attachment 186548 from comment 2, I added:
C1: =A1
D1: =B1
Then I Clear Direct Formatting on C1:D1 ([CTRL]+[M]).
The resulting values are different, which means those dates are not the same
for Calc.
C1: -181861
D1: 45025
Then:
_ E1: =D1
_ Clone format from A1 to E1.
I copied the result from E1 to some translation web page, and the resulting
translation to English was "Sunday, July 9, 2023", which is the same date and
day of the week of B1.
Using the original text from A1 in the same translation web page, the result is
"Friday, April 20, 1402".
Using the same serial number from C1, the result is "Fri, January 20, 1402",
which is a different date than the translated text ("Friday, April 20, 1402").
We seem to have here a Gregorian vs Julian Calendar issue, before considering
what is the date format for the cell and the corresponding calculation of the
day of the week for a given date.
I think we need more info – I thought that the date was supposed to be the same
in A1 and in B1 according to comment 0, but it's not – but we also need someone
that understands the 3 different Calendars (or at least 2 of them) and how Calc
deals with the '[NatNum1]""D ' format.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 59284] [META] Calc cell border related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=59284 Bug 59284 depends on bug 140032, which changed state. Bug 140032 Summary: Double-line cell borders not exported to XLSX and XLS https://bugs.documentfoundation.org/show_bug.cgi?id=140032 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140032] Double-line cell borders not exported to XLSX and XLS
https://bugs.documentfoundation.org/show_bug.cgi?id=140032 Peter S Anderson changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #15 from Peter S Anderson --- I have just tried to reproduce this bug using 7.5.0.3 without success. Both the the original ods and a newly created ods displayed fine in MS Excel and after saving as XLSX and then loading in Libreoffice. Have changed status as per email to me dated 28 Mar 2023, 14:21. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125938] Paste cell with cell-anchored images does not put anchor in target cell.
https://bugs.documentfoundation.org/show_bug.cgi?id=125938 Regina Henschel changed: What|Removed |Added CC||rb.hensc...@t-online.de --- Comment #5 from Regina Henschel --- The anchor is still wrong in Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 23bd3bd10e74b0c23c2654d02d7d830e7693adac CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154737] Mac forces printing in landscape mode
https://bugs.documentfoundation.org/show_bug.cgi?id=154737 --- Comment #2 from Adam Smith --- (In reply to m.a.riosv from comment #1) > Please test with a clean profile, Menu/Help/Restart in Safe Mode Done. Makes not a bit of difference. It forces a print in landscape mode, with no apparent way to change this. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154737] Mac forces printing in landscape mode
https://bugs.documentfoundation.org/show_bug.cgi?id=154737 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #1 from m.a.riosv --- Please test with a clean profile, Menu/Help/Restart in Safe Mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129294] [META] Variable field bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=129294 Bug 129294 depends on bug 154217, which changed state. Bug 154217 Summary: Fields variables (user field and variable) cannot format value for update as date (or similar) https://bugs.documentfoundation.org/show_bug.cgi?id=154217 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102019] [META] Dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102019 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||152220 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152220 [Bug 152220] macOS: UI in dark mode - tabs in dialogs get overlaid with previously shown tabs -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152220] macOS: UI in dark mode - tabs in dialogs get overlaid with previously shown tabs
https://bugs.documentfoundation.org/show_bug.cgi?id=152220 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||102019 Summary|Previously displayed|macOS: UI in dark mode - |Preference tab is shown in |tabs in dialogs get |background (in macOS dark |overlaid with previously |mode) |shown tabs --- Comment #14 from Stéphane Guillou (stragu) --- I changed the summary. Would be great if someone who can reproduce could confirm that it is a regression (i.e. that it didn't happen before 7.5) and attempt a bibisection to pinpoint when exactly it started: https://wiki.documentfoundation.org/QA/Bibisect/macOS Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102019 [Bug 102019] [META] Dialog bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154658] XML Form Document: Fields doesn't calculate any more, connection to instance broken
https://bugs.documentfoundation.org/show_bug.cgi?id=154658 raal changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Regression By||Julien Nabet CC||r...@post.cz, ||serval2...@yahoo.fr Keywords||bibisected, bisected --- Comment #1 from raal --- This seems to have begun at the below commit in bibisect repository/OS linux-64-7.3. Adding Cc: to Julien Nabet ; Could you possibly take a look at this one? Thanks 90dfd771ec50051d6f7018a07c8b5dd09b9f99e8 is the first bad commit commit 90dfd771ec50051d6f7018a07c8b5dd09b9f99e8 Author: Jenkins Build User Date: Sun Nov 7 22:03:56 2021 +0100 source sha:73334560b2dd2d60ac58d2cc2b1a5295490b03e1 124827: Replace some macros in forms part 16 | https://gerrit.libreoffice.org/c/core/+/124827 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154736] Having a lot of Writer Crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=154736 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #2 from m.a.riosv --- Please test with a clean profile, Menu/Help/Restart in Safe Mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154733] Enhancement: Consistent behavior for change of zoom factor when using various plus and minus icons
https://bugs.documentfoundation.org/show_bug.cgi?id=154733 m.a.riosv changed: What|Removed |Added Severity|normal |enhancement -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154731] Enhancement: Simplify Zoom & View Layout dialog by eliminating unusable choices
https://bugs.documentfoundation.org/show_bug.cgi?id=154731 m.a.riosv changed: What|Removed |Added Severity|normal |enhancement -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154730] Enhancement: Consistent UI terminology for zooming
https://bugs.documentfoundation.org/show_bug.cgi?id=154730 m.a.riosv changed: What|Removed |Added Severity|normal |enhancement -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154723] Crash when open Page Style > Area > Image
https://bugs.documentfoundation.org/show_bug.cgi?id=154723 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #2 from m.a.riosv --- Not reproducible. Version: 7.5.2.2 (X86_64) / LibreOffice Community Build ID: 53bb9681a964705cf672590721dbc85eb4d0c3a2 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Maybe you can find easy test with a clean profile, through Menu/Help/Restart in Safe Mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154737] New: Mac forces printing in landscape mode
https://bugs.documentfoundation.org/show_bug.cgi?id=154737 Bug ID: 154737 Summary: Mac forces printing in landscape mode Product: LibreOffice Version: 7.5.2.2 release Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: aasm...@cs.wisc.edu Description: Different variants of this bug appear to go back to 2015 or so. When you have a letter-sized document, LibreOffice *insists* on printing it in landscape orientation, and there's no apparent way to alter it. However, I can't find any info on it in current versions. (I did find a lot of old, snarky threads. This issue has been marked closed several times.) Yes, some workarounds work. I can set the document width to be 8.49", and it behaves correctly. I can output to PDF and print the PDF, and that works. However I'm trying to teach my techphobic mother-in-law to use this program, and these workarounds really are a bridge too far. I hope that someone is able to fix this bug soon. It appears to have been in LibreOffice for nearly a decade. Steps to Reproduce: 1.Make a letter-sized portrait document on a Mac. 2.Try to print it. 3. Actual Results: It forces you to print in landscape, with a giant margin on the right, and cutting it off on the bottom. Expected Results: Printing should match the orientation of the document. Reproducible: Always User Profile Reset: No Additional Info: We upgraded from LO 7.2.2 to 7.5.2, in an effort to fix this. There was no difference. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154722] Break of line between pages in spite of have spaces in previous page
https://bugs.documentfoundation.org/show_bug.cgi?id=154722 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG CC||miguelangelrv@libreoffice.o ||rg --- Comment #2 from m.a.riosv --- Please ask your question in https://ask.libreoffice.org/c/english/5 (you can select other language different from English) In the meantime we leave it resolved as NOTABUG If there really is a bug, please reopen it again. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154721] Jalali Calendar does not work correct in Libre office calc
https://bugs.documentfoundation.org/show_bug.cgi?id=154721 m.a.riosv changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #3 from m.a.riosv --- Foremost, forgive me, I am not known about Persian and Persian calendar. Let's see if someone else can confirm if there is an issue. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154697] Adding language dictionary extensions via link in Spellcheck - Options Dialog broken
https://bugs.documentfoundation.org/show_bug.cgi?id=154697 raal changed: What|Removed |Added CC||r...@post.cz --- Comment #5 from raal --- Works for me in Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 250b820a24640a33d73a6e690e04e36be01cda28 CPU threads: 4; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154700] special characters in pdf export
https://bugs.documentfoundation.org/show_bug.cgi?id=154700 --- Comment #3 from خالد حسني --- Also, what options do you use with pdfjam? I tried it locally and the output PDF came out fine. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154700] special characters in pdf export
https://bugs.documentfoundation.org/show_bug.cgi?id=154700 --- Comment #2 from خالد حسني --- I don’t see anything unusual about the PDF file LibreOffice generates, can you attach the PDFs created with the old version that were working for you? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152220] Previously displayed Preference tab is shown in background (in macOS dark mode)
https://bugs.documentfoundation.org/show_bug.cgi?id=152220 --- Comment #13 from Martin Srebotnjak --- While you closed my bug report as a duplicate - please rename your bug report with my title - which is much more descriptive about the problem: "macOS: UI in dark mode - tabs in dialogs get overlaid with previously shown tabs". -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154736] Having a lot of Writer Crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=154736 --- Comment #1 from BrendaEM --- It's a frequent crash, but I haven't narrowed the cause, yet. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154736] New: Having a lot of Writer Crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=154736 Bug ID: 154736 Summary: Having a lot of Writer Crashes Product: LibreOffice Version: 7.5.2.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: brendieel...@brenda-make.com Description: I am having a lot of writer crashes. I am not sure, but they might be related to adding/removing text, and or cut/paste. Steps to Reproduce: 1. Use the Program 2. Program crashes, no message. 3. Actual Results: Writer crashes more than a cheap airplane. Expected Results: Hoped it would continue functioning. Reproducible: Always User Profile Reset: No Additional Info: Has there been a regression. A few versions ago, writer was crashing. Then it got better. Now, it's crashing again. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149064] Error when running macro accessing WebDAV twice
https://bugs.documentfoundation.org/show_bug.cgi?id=149064 Commit Notification changed: What|Removed |Added Whiteboard|target:7.6.0 target:7.5.3 |target:7.6.0 target:7.5.3 ||target:7.4.7 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154570] LO Writer not saving macros
https://bugs.documentfoundation.org/show_bug.cgi?id=154570 Dieter changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||dgp-m...@gmx.de --- Comment #1 from Dieter --- Alexis, does it also happen in latest version 7.5.2.2? => NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154701] Writer move paragraph not working properly with Outline Folding
https://bugs.documentfoundation.org/show_bug.cgi?id=154701 Dieter changed: What|Removed |Added Ever confirmed|0 |1 CC||dgp-m...@gmx.de Status|UNCONFIRMED |NEEDINFO --- Comment #1 from Dieter --- Have you reset your user profile or tested in safe mode(Help -> Restart in Safe Mode)? => NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129292] Writer uses the last-used directory for opening and saving files, ignoring the setting in Options > Paths > My Documents
https://bugs.documentfoundation.org/show_bug.cgi?id=129292 m.a.riosv changed: What|Removed |Added CC||roodborst...@gmail.com --- Comment #5 from m.a.riosv --- *** Bug 154719 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 154719] remember last used directory
https://bugs.documentfoundation.org/show_bug.cgi?id=154719 m.a.riosv changed: What|Removed |Added Resolution|FIXED |DUPLICATE --- Comment #3 from m.a.riosv --- Not it should be RESOLVED DUPLICATE *** This bug has been marked as a duplicate of bug 129292 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151474] Allow formatting footnotes in columns or separated by spaces
https://bugs.documentfoundation.org/show_bug.cgi?id=151474 --- Comment #7 from m.a.riosv --- That no one has yet reproduced your report. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152220] Previously displayed Preference tab is shown in background (in macOS dark mode)
https://bugs.documentfoundation.org/show_bug.cgi?id=152220 eisa01 changed: What|Removed |Added CC||mi...@filmsi.net --- Comment #12 from eisa01 --- *** Bug 154729 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 154729] macOS: UI in dark mode - tabs in dialogs get overlaid with previously shown tabs
https://bugs.documentfoundation.org/show_bug.cgi?id=154729 eisa01 changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from eisa01 --- *** This bug has been marked as a duplicate of bug 152220 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154735] New: Crashed when I try to send email with pdf (email correspondence)
https://bugs.documentfoundation.org/show_bug.cgi?id=154735 Bug ID: 154735 Summary: Crashed when I try to send email with pdf (email correspondence) Product: LibreOffice Version: 7.5.2.2 release Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: humlo...@gmail.com Description: When I try to send emails with pdf to some people using the "email correspondence" feature the app crash. I tried with the version 7.4.6 and 7.5.2 Steps to Reproduce: 1. Open and prepare the document 2. Send email (menu correspondence email) 3. Send like pdf 4. Type the Subject 5. Crash Actual Results: Crash and re-start the app Expected Results: Send email with the pdf attached Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.5.2.2 (X86_64) / LibreOffice Community Build ID: 53bb9681a964705cf672590721dbc85eb4d0c3a2 CPU threads: 6; OS: Mac OS X 13.2.1; UI render: default; VCL: osx Locale: es-ES (es_ES.UTF-8); UI: es-ES Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136851] No-break space not working with Asian font text or mixed Western and Asian
https://bugs.documentfoundation.org/show_bug.cgi?id=136851 --- Comment #4 from Thomas Lendo --- Still existing with 7.5.2.2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 116127] Cell Range method ClearContents does not work with com.sun.star.sheet.CellFlags.EDITATTR
https://bugs.documentfoundation.org/show_bug.cgi?id=116127 Andreas Heinisch changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |andreas.heini...@yahoo.de |desktop.org | Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154386] [META] XML Form
https://bugs.documentfoundation.org/show_bug.cgi?id=154386 Robert Großkopf changed: What|Removed |Added Depends on||154734 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154734 [Bug 154734] XML Form Document: All binded fields will be shown as fields with wrong content - except fields, which have wrong content. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154734] XML Form Document: All binded fields will be shown as fields with wrong content - except fields, which have wrong content.
https://bugs.documentfoundation.org/show_bug.cgi?id=154734 Robert Großkopf changed: What|Removed |Added Blocks||154386 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154386 [Bug 154386] [META] XML Form -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154728] XML Form Document: Binding to numeric fields with numeric form controls impossible
https://bugs.documentfoundation.org/show_bug.cgi?id=154728 Robert Großkopf changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4734 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154734] XML Form Document: All binded fields will be shown as fields with wrong content - except fields, which have wrong content.
https://bugs.documentfoundation.org/show_bug.cgi?id=154734 Robert Großkopf changed: What|Removed |Added Keywords||regression See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4728 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154734] New: XML Form Document: All binded fields will be shown as fields with wrong content - except fields, which have wrong content.
https://bugs.documentfoundation.org/show_bug.cgi?id=154734 Bug ID: 154734 Summary: XML Form Document: All binded fields will be shown as fields with wrong content - except fields, which have wrong content. Product: LibreOffice Version: 7.3.0.3 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rob...@familiegrosskopf.de Download https://bugs.documentfoundation.org/attachment.cgi?id=186554 and open the document. There are some fields (numeric) which couldn't get bindings with LO 7.3.0.3 or newer. All fields, which have a binding to data, will be shown as fields with "wrong content" (red line). Only field for Boolean, which has also a binding, won't show this. But this field has wrong content. Has to be '1' or '0' instead, but is empty. Open the same document in LO 7.2.5.2 and fields will be shown right. Might be this bug has been introduce with the same code as bug 154728 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154489] Error in libsclo.so impedes opening any spreadsheet file
https://bugs.documentfoundation.org/show_bug.cgi?id=154489 --- Comment #7 from Devtote --- I tried downgrading.but every version failed. I am suspecting it could be linked to liborcus. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107923] [META] Zoom issues
https://bugs.documentfoundation.org/show_bug.cgi?id=107923 V Stuart Foote changed: What|Removed |Added Depends on||154731 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154731 [Bug 154731] Enhancement: Simplify Zoom & View Layout dialog by eliminating unusable choices -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154731] Enhancement: Simplify Zoom & View Layout dialog by eliminating unusable choices
https://bugs.documentfoundation.org/show_bug.cgi?id=154731 V Stuart Foote changed: What|Removed |Added Blocks||107923 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107923 [Bug 107923] [META] Zoom issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107923] [META] Zoom issues
https://bugs.documentfoundation.org/show_bug.cgi?id=107923 V Stuart Foote changed: What|Removed |Added Depends on||154730 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154730 [Bug 154730] Enhancement: Consistent UI terminology for zooming -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154730] Enhancement: Consistent UI terminology for zooming
https://bugs.documentfoundation.org/show_bug.cgi?id=154730 V Stuart Foote changed: What|Removed |Added Blocks||107923 Summary|Enhancement: Consistent |Enhancement: Consistent UI |menu terminology for|terminology for zooming |zooming | --- Comment #1 from V Stuart Foote --- Agree the labeling of the "Entire Page", "Fit [slide|page] to current window", "Fit width and height" could all be consolidated, I think functionally they are all equal--though different code paths I'd imagine. Would suggest the "Fit width and height" to be the most appropriate across the modules. The residual "Slide" labeling in Draw are those of bug 150477 and your bug 154732 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107923 [Bug 107923] [META] Zoom issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107280] [META] Issues related to the shared code between Impress and Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=107280 V Stuart Foote changed: What|Removed |Added Depends on||154732 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154732 [Bug 154732] Zoom bar "Fit slide to current window" should be "page" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154732] Zoom bar "Fit slide to current window" should be "page"
https://bugs.documentfoundation.org/show_bug.cgi?id=154732 V Stuart Foote changed: What|Removed |Added Summary|Enhancement: Consistent |Zoom bar "Fit slide to |terminology for Page/Slide |current window" should be ||"page" CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vsfo...@libreoffice.org Severity|normal |trivial Blocks||107280 Keywords||needsUXEval See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||4175, ||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||0477 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from V Stuart Foote --- This is valid, but trivial. Draw and Impress share major components of the sd module. Similar to the "Slide # of #" labeling for both Draw and Impress UI. Seems like an item that should have picked up for see also bug 114175, there are a few e.g. bug 150477 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107280 [Bug 107280] [META] Issues related to the shared code between Impress and Draw -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154489] Error in libsclo.so impedes opening any spreadsheet file
https://bugs.documentfoundation.org/show_bug.cgi?id=154489 --- Comment #6 from Devtote --- **Fixing last comment typos The problem appears when creating or accessing to a Spreadsheet, Write, Draw or Math docs. Impress Presentations run smoothly though. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154733] New: Enhancement: Consistent behavior for change of zoom factor when using various plus and minus icons
https://bugs.documentfoundation.org/show_bug.cgi?id=154733 Bug ID: 154733 Summary: Enhancement: Consistent behavior for change of zoom factor when using various plus and minus icons Product: LibreOffice Version: 7.4.6.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: dmatsch...@quietriding.com Clicking on the Plus Sign at the right end of the Status Bar increases the zoom factor by 10%. Clicking on the icon with the Plus Sign in the Zoom toolbar doubles the zoom factor. Clicking on the Minus Sign at the right end of the Status Bar decreases the zoom factor by 10%. Clicking on the icon with the Minus Sign in the Zoom toolbar reduces the zoom factor by one-half. Consistent behavior by the plus and minus signs in these two areas would help eliminate confusion when working in LibreOffice Draw. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154489] Error in libsclo.so impedes opening any spreadsheet file
https://bugs.documentfoundation.org/show_bug.cgi?id=154489 --- Comment #5 from Devtote --- The problem appears when creating or acessing to a Spreadsheet, Write, Impress or Math document. Publisher docs run smoothly though. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154489] Error in libsclo.so impedes opening any spreadsheet file
https://bugs.documentfoundation.org/show_bug.cgi?id=154489 --- Comment #4 from Devtote --- Same error here. Also tried reinstalling, and deleting libsclo.so and reinstalling. It does not work. libsclo.so file is illegible. libsclo.so recreates after every installation of libreoffice-fresh. No shlib.cxx is found though, so I could not read the line 332. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154731] Enhancement: Simplify Zoom & View Layout dialog by eliminating unusable choices
https://bugs.documentfoundation.org/show_bug.cgi?id=154731 V Stuart Foote changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vsfo...@libreoffice.org Keywords||needsUXEval --- Comment #1 from V Stuart Foote --- The options are greyed out/non-selectable and that is sufficient as hiding it from the global Zoom & View layout would require either splitting the two functions, or unreasonable rework of the dialog. IMHO => WF -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154730] Enhancement: Consistent menu terminology for zooming
https://bugs.documentfoundation.org/show_bug.cgi?id=154730 V Stuart Foote changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vsfo...@libreoffice.org -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154732] New: Enhancement: Consistent terminology for Page/Slide
https://bugs.documentfoundation.org/show_bug.cgi?id=154732 Bug ID: 154732 Summary: Enhancement: Consistent terminology for Page/Slide Product: LibreOffice Version: 7.4.6.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: dmatsch...@quietriding.com The white portion of the Workspace is referred to as a "page" in the Pages pane. The tooltip for the four-pointed arrow at the right of the Status Bar refers to this white portion of the Workspace as a "slide" when it states: "Fit slide to current window." Using inconsistent terminology in this way can make LibreOffice draw appear confusing and hard to work with -- especially to those checking out LibreOffice Draw for the first time. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154718] LibreOffice theme impacts menu color (XFCE)
https://bugs.documentfoundation.org/show_bug.cgi?id=154718 V Stuart Foote changed: What|Removed |Added Blocks||125823 Summary|LibreOffice theme impacts |LibreOffice theme impacts |menu color |menu color (XFCE) CC||vsfo...@libreoffice.org --- Comment #1 from V Stuart Foote --- Don't use the legacy Mozilla styled themes. We know they're broken bug 125217 IMHO => WF Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=125823 [Bug 125823] [META] Personalization (LibreOffice Themes) bugs and Improvements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125823] [META] Personalization (LibreOffice Themes) bugs and Improvements
https://bugs.documentfoundation.org/show_bug.cgi?id=125823 V Stuart Foote changed: What|Removed |Added Depends on||154718 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154718 [Bug 154718] LibreOffice theme impacts menu color (XFCE) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154727] pdf import: odd text layout (tabs?) (UK IHT 407)
https://bugs.documentfoundation.org/show_bug.cgi?id=154727 --- Comment #7 from V Stuart Foote --- (In reply to V Stuart Foote from comment #6) > ipdf filter import seemingly grid/tabed layout issues noted these builds: > likewise with Version: 5.4.7.2 (x64) Build ID: c838ef25c16710f8838b1faec480ebba495259d0 CPU threads: 8; OS: Windows 6.19; UI render: GL; Locale: en-US (en_US); Calc: group so work on bug 50879 is not involved (export only but just checking). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154731] New: Enhancement: Simplify Zoom & View Layout dialog by eliminating unusable choices
https://bugs.documentfoundation.org/show_bug.cgi?id=154731 Bug ID: 154731 Summary: Enhancement: Simplify Zoom & View Layout dialog by eliminating unusable choices Product: LibreOffice Version: 7.4.6.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: dmatsch...@quietriding.com The right side of the Zoom & View Layout dialog has an area titled "View Layout". This area was grayed out when I first saw it, so I searched to find out when and how it might be used. I finally found a reference to the Zoom & View Layout in Chapter 3 of the Draw Guide that says of the View Layout area: "Used to set the view layout and is not available for drawings. View layout is normally used in text documents to see the effects of different layout settings." Since this area is "not available for drawings", removing it from the dialog would eliminate confusion. The less confusing an application is, the easier it is to use. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154727] pdf import: odd text layout (tabs?) (UK IHT 407)
https://bugs.documentfoundation.org/show_bug.cgi?id=154727 V Stuart Foote changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #6 from V Stuart Foote --- ipdf filter import seemingly grid/tabed layout issues noted these builds: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1e9f4de320f67d1218c710bcee1969a2324c6888 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Version: 7.5.2.2 (X86_64) / LibreOffice Community Build ID: 53bb9681a964705cf672590721dbc85eb4d0c3a2 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Version: 6.4.7.2 (x64) Build ID: 639b8ac485750d5696d7590a72ef1b496725cfb5 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: GL; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99746] [META] PDF import filter in Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=99746 V Stuart Foote changed: What|Removed |Added Depends on||154727 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154727 [Bug 154727] pdf import: odd text layout (tabs?) (UK IHT 407) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154727] pdf import: odd text layout (tabs?) (UK IHT 407)
https://bugs.documentfoundation.org/show_bug.cgi?id=154727 V Stuart Foote changed: What|Removed |Added Blocks||99746 CC||vmik...@collabora.com Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=99746 [Bug 99746] [META] PDF import filter in Draw -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154727] pdf import: odd text layout (tabs?) (UK IHT 407)
https://bugs.documentfoundation.org/show_bug.cgi?id=154727 --- Comment #5 from V Stuart Foote --- @Miklos, the Cairo based ipdf import filter does fail rather notably parsing the draw text object placements and sizing compared to the pdfium based filter. Should we do better? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154730] New: Enhancement: Consistent menu terminology for zooming
https://bugs.documentfoundation.org/show_bug.cgi?id=154730 Bug ID: 154730 Summary: Enhancement: Consistent menu terminology for zooming Product: LibreOffice Version: 7.4.6.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: dmatsch...@quietriding.com Tooltips, dialogs, and menu choices use several different terms to achieve the effect of showing the complete page in the Workspace in LibreOffice Draw. The menu that appears when you right click on the percentage number at the right end of the Status Bar offers a choice of zooming to "Entire Page". The Zoom & View Layout dialog that appears when you left click on this same percentage number at the right end of the Status Bar labels the choice as "Fit width and height". The four-pointed arrow a little to the left in the Status Bar displays a tooltip that says: "Fit slide to current window." If you go to View>Zoom, you're given a choice of "Entire Page". If you go to the bottom of this same menu and select Zoom..., the Zoom & View Layout dialog opens that labels the choice as "Fit width and height". The icon for this zoom factor shown in the Zoom toolbar displays a Tooltip that says "Entire Page". Such use of various terminology can cause unnecessary confusion, especially when someone is first trying to learn how to use LibreOffice Draw. It can also lead people to believe LibreOffice Draw is more complicated and hard to learn than is actually the case. Describing the same action in consistent terminology would be a major improvement. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154729] macOS: UI in dark mode - tabs in dialogs get overlaid with previously shown tabs
https://bugs.documentfoundation.org/show_bug.cgi?id=154729 --- Comment #2 from Martin Srebotnjak --- Created attachment 186557 --> https://bugs.documentfoundation.org/attachment.cgi?id=186557=edit Security page of the LibreOffice Options dialog with a "ghost" tab -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154729] macOS: UI in dark mode - tabs in dialogs get overlaid with previously shown tabs
https://bugs.documentfoundation.org/show_bug.cgi?id=154729 --- Comment #1 from Martin Srebotnjak --- Created attachment 186556 --> https://bugs.documentfoundation.org/attachment.cgi?id=186556=edit Area tab of the Paragraph dialog with a "ghost" tab -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154729] New: macOS: UI in dark mode - tabs in dialogs get overlaid with previously shown tabs
https://bugs.documentfoundation.org/show_bug.cgi?id=154729 Bug ID: 154729 Summary: macOS: UI in dark mode - tabs in dialogs get overlaid with previously shown tabs Product: LibreOffice Version: 7.5.2.2 release Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mi...@filmsi.net Description: Using LO 7.5.2.2 (on macOS) in dark mode - when opening dialogs with tabs - when selecting another tab the display of the previous tab remains partly (semi-transparently) visible. It happens also with the Option dialog and its pages. I am attaching two screenshots, one with Paragraph dialog (Area tab) and the other one with the Options dialog (LibreOffice - Security tab). I am not sure whether this is reproducible only on macOS or if it can be seen also on other systems. Steps to Reproduce: 1. Open a document in Writer in dark mode. 2. Open any window with tabs (like Format - Paragraph). 3. Select another tab in that window. Actual Results: Current tab is shown, with the underlay of semi-transparent display of the previous tab. Expected Results: No semi-transparent display of the previously shown tab content. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.5.2.2 (X86_64) / LibreOffice Community Build ID: 53bb9681a964705cf672590721dbc85eb4d0c3a2 CPU threads: 8; OS: Mac OS X 11.7.4; UI render: default; VCL: osx Locale: sl-SI (sl_SI.UTF-8); UI: sl-SI Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154727] pdf import: odd text layout (tabs?) (UK IHT 407)
https://bugs.documentfoundation.org/show_bug.cgi?id=154727 --- Comment #4 from Dave Gilbert --- Hi, Thanks - however, I'm not sure this is a simple font substitution screwup. Each of the words seems to have been tab aligned - how did that happen? (IHT411 is showing simple font substitution issues with simple places just a bit longer than needed and overlapping stuff, but I'd agree that's not a bug). I agree about not using LO for form filling; but what I was actually trying to do was use it when the other PDF viewers were breaking and screwing up form field values so use it for manual editing. (We've just fixed two Okular bugs on this). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 88436] CALC: R1C1 formula broken by worksheets names started by number
https://bugs.documentfoundation.org/show_bug.cgi?id=88436 Andreas Heinisch changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=60 ||385 -- You are receiving this mail because: You are the assignee for the bug.
