[Libreoffice-bugs] [Bug 153561] Rename "Chapter -> Heading" and "E# -> H#" in Entries tab of Insert Table of Contents, Index, Bibliography dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=153561 --- Comment #23 from Mike Kaganski --- So, now it changed from "E#" (read: Entry Number, quite correct and covering everything) into "N#" (read: Numbering Number) ... well, likely an improvement ;) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153561] Rename "Chapter -> Heading" and "E# -> H#" in Entries tab of Insert Table of Contents, Index, Bibliography dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=153561 --- Comment #22 from Commit Notification --- Seth Chaiklin committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/09aca4a8bff06a719fa85d7287969e484fcb5e3f tdf#153561 rename Heading No. and widget, update tool/extended tips It will be available in 7.6.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 153995] No UI for flipping the column order of a table
https://bugs.documentfoundation.org/show_bug.cgi?id=153995 --- Comment #2 from Heiko Tietze --- (In reply to Eyal Rozenberg from comment #0) > There is no UI for doing that, and probably no code either. There should be! > When we want to switch the direct of a paragraph, we can do that; so - why > not also that of a table? Have you ever seen such a UI? Rather than some interface I'd want to use a shortcut, something like ctrl+c and +v that not only inserts the copied content but switches it. Would be hard to figure out, if not existent anywhere else. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153919] Shift+resize aspect ratio not maintained for images
https://bugs.documentfoundation.org/show_bug.cgi?id=153919 Heiko Tietze changed: What|Removed |Added CC||c...@nouenoff.nl --- Comment #7 from Heiko Tietze --- (In reply to Eyal Rozenberg from comment #6) > Were alternatives (other than the previous state of affairs) presented, > considered and rejected? Wasn't involved myself but maybe Cor has insights. My take in general: do not touch existing functionality without a clear issue, use case, scenario. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153999] New: Form fields invisible on printing in Writer when in dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=153999 Bug ID: 153999 Summary: Form fields invisible on printing in Writer when in dark mode Product: LibreOffice Version: 7.5.1.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: fkon...@gmail.com Description: When i switch on dark mode, any form elements I have in the page, text, drop-down list or date, do not print. They are invisible. When I switch dark mode off, they appear again. Windows 11 and the problem started since 7.4.3 and continues on 7.5. Steps to Reproduce: 1.Create drop-down list 2.Go to Tools -Settings-Enable experimental features 3.Try to print the document Actual Results: Form fields are invisible in print preview and also in the printed paper Expected Results: Form fields suppose to print Reproducible: Always User Profile Reset: Yes Additional Info: Bug still exists in LO 7.5.1. The only combination of settings that worked is: Tools-Options-Application Colors-Libre Office Dark AND Tools-Options-View-Mode-Light. With this combination of settings form fields are visible in Print Preview and printing fine. In every other combination of settings, form fields are invisible in print preview and also in the printed paper. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128671] master branch cannot be built without manual hacks with Aarch64 distro config
https://bugs.documentfoundation.org/show_bug.cgi?id=128671 Michael Weghorn changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128671] master branch cannot be built without manual hacks with Aarch64 distro config
https://bugs.documentfoundation.org/show_bug.cgi?id=128671 saffron exchange changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|NEW --- Comment #37 from saffron exchange --- Saffron Exchange Is The World’s Largest Online Fantasy Sport Identification Platform. It’s an India based fantasy sports platform that allows users to play fantasy cricket, hockey, football, kabaddi, handball, basketball, volleyball, rugby, futsal, American football and baseball. https://saffronexchange7.com/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153993] FORMATTING: Calc alters custom number format on save
https://bugs.documentfoundation.org/show_bug.cgi?id=153993 --- Comment #4 from Matt Keveney --- > B_ Have you tried the same steps using other software > (e.g. AOO and/or Excel for MacOS or any other) to see how the > behavior is there? Just tested Apache OpenOffice 4.1.14. It has similar behavior, only worse! It does not recognize the three ### as signifying engineering units, so the test data listed above initially displays as: 123.456 e0 123.456 e1 123.456 e2 Then, after save/reload it looks like this: 123.456E+0 123.456E+1 123.456E+2 And the format code has been changed to this: 000.000E+0 If you place your cursor in the format code edit window, you can see that a _trailing_ space has been added to the format code, but no double-quote characters are visible as in LibreOffice. so... please don't use the current OpenOffice code as a source of inspiration :). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153993] FORMATTING: Calc alters custom number format on save
https://bugs.documentfoundation.org/show_bug.cgi?id=153993 --- Comment #3 from Matt Keveney --- added related feature request: https://ask.libreoffice.org/t/please-add-support-for-si-prefixes-in-number-formats/88844 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151916] Not working if I choose Mongolian Cyrillic
https://bugs.documentfoundation.org/show_bug.cgi?id=151916 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 153975] Win11 BSOD when I click LibreOfc "Help"
https://bugs.documentfoundation.org/show_bug.cgi?id=153975 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147216] LibreOffice seems to be properly scaled only for the primary screen
https://bugs.documentfoundation.org/show_bug.cgi?id=147216 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 153975] Win11 BSOD when I click LibreOfc "Help"
https://bugs.documentfoundation.org/show_bug.cgi?id=153975 --- Comment #5 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153698] LibreOffice Impress did not store pictures
https://bugs.documentfoundation.org/show_bug.cgi?id=153698 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153698] LibreOffice Impress did not store pictures
https://bugs.documentfoundation.org/show_bug.cgi?id=153698 --- 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 153537] A field should have its own character style
https://bugs.documentfoundation.org/show_bug.cgi?id=153537 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 153537] A field should have its own character style
https://bugs.documentfoundation.org/show_bug.cgi?id=153537 --- Comment #4 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150215] CONFIGURATION (possibility of allowing multiple sheets/tabs)
https://bugs.documentfoundation.org/show_bug.cgi?id=150215 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 150021] Sentence disappear when I press Enter
https://bugs.documentfoundation.org/show_bug.cgi?id=150021 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 150215] CONFIGURATION (possibility of allowing multiple sheets/tabs)
https://bugs.documentfoundation.org/show_bug.cgi?id=150215 --- Comment #5 from QA Administrators --- Dear Chris, 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 150021] Sentence disappear when I press Enter
https://bugs.documentfoundation.org/show_bug.cgi?id=150021 --- Comment #3 from QA Administrators --- Dear up61963, 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 96775] Android: LibreOffice Viewer cannot open .xlsm files
https://bugs.documentfoundation.org/show_bug.cgi?id=96775 --- Comment #5 from QA Administrators --- Dear Feyza, 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 149188] Crash if I try to load a MicrosoftWorddocument.doc or .docx 2003 or 2007
https://bugs.documentfoundation.org/show_bug.cgi?id=149188 --- Comment #3 from QA Administrators --- Dear danjou_remi, 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 144063] LibreOffice shows Shift-ESC assigned to "Search Command"... Doesn't work
https://bugs.documentfoundation.org/show_bug.cgi?id=144063 --- Comment #13 from QA Administrators --- Dear David W. Snow, 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 87219] FILEOPEN: line at the top displayed at the bottom in .rtf
https://bugs.documentfoundation.org/show_bug.cgi?id=87219 --- Comment #11 from QA Administrators --- Dear tommy27, 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 87218] FILEOPEN: table displayed in wrong position in .rtf
https://bugs.documentfoundation.org/show_bug.cgi?id=87218 --- Comment #14 from QA Administrators --- Dear tommy27, 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 83133] FORMATTING: Frames styles change
https://bugs.documentfoundation.org/show_bug.cgi?id=83133 --- Comment #9 from QA Administrators --- Dear Pedro I. Hernandez, 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 69579] SCANNING: dpi-values are not processed correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=69579 --- Comment #16 from QA Administrators --- Dear bordfeldt, 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 69524] EDITING Creating new frame style from selected graphic, adds properties for dimensions, and thus changes the size of images that it is applied too, which is wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=69524 --- Comment #13 from QA Administrators --- Dear Cor Nouws, 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 69043] INSTALLATION: On MS-Windows 7, upgrade using 'LibreOffice_4.1.1_Win_x86.msi' systematically complains that it needs to update files which are opened by 'Microsoft Window
https://bugs.documentfoundation.org/show_bug.cgi?id=69043 --- Comment #19 from QA Administrators --- Dear Etienne URBAH, 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 57373] FILEOPEN: Old Word 95 DOC list input fields not imported since LO 3.5 (OK if saved in MSO as DOC)
https://bugs.documentfoundation.org/show_bug.cgi?id=57373 --- Comment #13 from QA Administrators --- Dear Urmas, 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 56949] FILEOPEN: Connectors lose their connections with the shapes
https://bugs.documentfoundation.org/show_bug.cgi?id=56949 --- Comment #11 from QA Administrators --- Dear chjacob, 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 56105] FILEOPEN Column width shown wrong, if observed before selecting whole column and column includes merged cells (see comment 7)
https://bugs.documentfoundation.org/show_bug.cgi?id=56105 --- Comment #17 from QA Administrators --- Dear Guillermo Mario Narvaja, 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 55160] Fileopen: docx layout not imported correctly - support for nested floating tables
https://bugs.documentfoundation.org/show_bug.cgi?id=55160 --- Comment #14 from QA Administrators --- Dear Gabor Kelemen, 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 140821] Button links to a not-existing webpage in Dutch.
https://bugs.documentfoundation.org/show_bug.cgi?id=140821 --- Comment #3 from QA Administrators --- Dear e.vandyken, 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 140810] border around text range has gap where object is
https://bugs.documentfoundation.org/show_bug.cgi?id=140810 --- Comment #3 from QA Administrators --- Dear Regina Henschel, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140500] TABLE: Arrow changes position in a cell across two pages
https://bugs.documentfoundation.org/show_bug.cgi?id=140500 --- Comment #2 from QA Administrators --- Dear Gerald, 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 123441] Comment box arrow detaches itself from corresponding cell when dragging around (fine after release)
https://bugs.documentfoundation.org/show_bug.cgi?id=123441 --- Comment #8 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 115615] Export to HTML generates wrong ImageMap if page margins are not zero
https://bugs.documentfoundation.org/show_bug.cgi?id=115615 --- Comment #4 from QA Administrators --- Dear ace_dent, 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 115546] Mirrored Page Headers do not respect "Same Content on Both Sides" setting wrt spacing
https://bugs.documentfoundation.org/show_bug.cgi?id=115546 --- Comment #5 from QA Administrators --- Dear Paul, 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 115048] Changing cell font size changes only upper line font if cell contains several lines of text
https://bugs.documentfoundation.org/show_bug.cgi?id=115048 --- Comment #12 from QA Administrators --- Dear Timofeus, 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 113084] FILEOPEN: RTF - Font table not imported/applied correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=113084 --- Comment #6 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 106963] Print Dialog: PPD conflicts may lead to valid printer options being unavailable
https://bugs.documentfoundation.org/show_bug.cgi?id=106963 --- Comment #17 from QA Administrators --- Dear Stephane Peter, 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 101379] UI - (on high resolution screens) text cursor is too thin and so nearly invisible
https://bugs.documentfoundation.org/show_bug.cgi?id=101379 --- Comment #17 from QA Administrators --- Dear bordfeldt, 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 101155] FILEOPEN PDF text overlaps because text is split to many boxes which don't fit
https://bugs.documentfoundation.org/show_bug.cgi?id=101155 --- Comment #7 from QA Administrators --- Dear E.Mi, 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 153993] FORMATTING: Calc alters custom number format on save
https://bugs.documentfoundation.org/show_bug.cgi?id=153993 --- Comment #2 from Matt Keveney --- > A_ Have you tried testing with a dev. release or testing version? > B_ Have you tried the same steps using other software > (e.g. AOO and/or Excel for MacOS or any other) to see how the > behavior is there? I just tried google sheets, since that was easiest. It does not accept format I reported above. Instead it says 'invalid format' right in the format editor, which would be a great thing to add to LibreOffice. I _could_ however enter the equivalent format: ###.000 e-0 This behaves as expected: https://docs.google.com/spreadsheets/d/1ecDo2_sJ_ag33H7Yf4VhVSoR60u6d24Z7XsgraPgaDc The format with the added '-' does not help in LibreOffice; again, it's replaced with ###.000E0" " on save/reopen. Aside: this format is just a stopgap. What I _really_ want is support for SI prefixes (k,M,G,T,P,m,µ,n,p,f) and so forth. I'll make an entry at https://ask.libreoffice.org/tag/feature-request... just thought I'd put a bug in your ear _here_, while I have your attention :-). Very useful for electronics calculations. Thanks! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153998] New: Donated. Stopped working. Now won't reinstall.
https://bugs.documentfoundation.org/show_bug.cgi?id=153998 Bug ID: 153998 Summary: Donated. Stopped working. Now won't reinstall. Product: LibreOffice Version: 7.2.7.2 release Hardware: Other OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: dumpjunkh...@comcast.net Description: 7.3.7 was working for a few days on win 11 pro. Then no files would open.All my files said corrupted. Repair did not work. So Uninstalled. Now won't install. Steps to Reproduce: 1. Tried repair 2.uninstalled 3.tried reinstalling multiple times Actual Results: Won't install in win 11 pro. Downloads but file won't open. Expected Results: I expected it to work forever like it did on my last laptop. Not for only a few days. Reproducible: Always User Profile Reset: No Additional Info: Kept working. Installed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148747] Formula and apostrophe behavior changed on Czech UI (see comment 35 and up)
https://bugs.documentfoundation.org/show_bug.cgi?id=148747 ady changed: What|Removed |Added Summary|Bad use of the date in |Formula and apostrophe |formulas|behavior changed on Czech ||UI (see comment 35 and up) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153993] FORMATTING: Calc alters custom number format on save
https://bugs.documentfoundation.org/show_bug.cgi?id=153993 ady changed: What|Removed |Added CC||jumbo4...@yahoo.fr --- Comment #1 from ady --- (In reply to Matt Keveney from comment #0) > Bugs 146404 and 152724 seem very similar, though this reporter can't be sure > it's the same underlying issue. CC'ing Laurent Balland, who has been reviewing several of these number format issues recently. Bug 146404 is about the custom [COLORnn] format. Bug 152724 is about the "_X" custom format, to leave a space equal to the width of that "X" character. There are other several bug reports related to supporting custom number format codes that are supported by other spreadsheet software. In this case, this seems to be related to space character(s) before the "E" (and/or "e") in the scientific number format. I am not sure whether this is also specific to the right-side of the number, or the decimal side of the number, or... The precise "definition" of the problem might depend on how exactly the code understands the use of the E/e for scientific notation, and whether this is allowed or supported in ODF. Two questions: A_ Have you tried testing with a dev. release or testing version? B_ Have you tried the same steps using other software (e.g. AOO and/or Excel for MacOS or any other) to see how the behavior is there? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153997] New: PRINTING - FOOTERS
https://bugs.documentfoundation.org/show_bug.cgi?id=153997 Bug ID: 153997 Summary: PRINTING - FOOTERS Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: skingsl...@gmail.com Created attachment 185778 --> https://bugs.documentfoundation.org/attachment.cgi?id=185778&action=edit 2-Pg document; footers not printing correctly on page 2 WITH NEW VERSION (7.5.1.2) FOOTERS ARE PRINTING AS DEFINED IN PAGE LAYOUT ON FIRST PAGE ONLY; SUBSEQUENT PAGES DISPLAY ONLY THE DEFAULT. E.G. PAGE # OF # , DATE / TIME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153769] error playing animations and transitions in libreoffice impress
https://bugs.documentfoundation.org/show_bug.cgi?id=153769 Michael FA changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105957] [META] Scrollbar-related bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=105957 Bug 105957 depends on bug 148601, which changed state. Bug 148601 Summary: Missing scrollbars in menus (interface bug since 7.0) https://bugs.documentfoundation.org/show_bug.cgi?id=148601 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148601] Missing scrollbars in menus (interface bug since 7.0)
https://bugs.documentfoundation.org/show_bug.cgi?id=148601 Michael FA changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153660] Single Undo should remove all diagonal borders created with Toolbar>Borders
https://bugs.documentfoundation.org/show_bug.cgi?id=153660 --- Comment #2 from ady --- (In reply to Stéphane Guillou (stragu) from comment #1) > With criss-cross, sometimes even two undo actions are not enough and some > diagonal "borders" remain with no undo action left. > > With "diagonal up" and "diagonal down", only one undo action is available, > and sometimes it removes everything, sometimes only a part, sometimes > nothing. As noted in bug 153644 comment 3, the behavior varies, depending on: * how many adjacent cells are selected, and on * whether you perform the action by using the toolbar icon or instead by using the full cell format dialog, and on * which exact of diagonals are initially applied (i.e. both vs. "one" only vs "the second" only). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153972] Calc autofilter can't choose background colour when cell has no content
https://bugs.documentfoundation.org/show_bug.cgi?id=153972 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #1 from m.a.riosv --- Reproducible Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 687b950702c49c90cff9a43655ea97a0343799a0 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 Jumbo Please review the title, don't sound too accurate for me. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153542] Libreoffice calc 7.5 very slow and unresponsive when zooming in out (wheel mouse) on large spreadsheet unde Debian
https://bugs.documentfoundation.org/show_bug.cgi?id=153542 ady changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3985 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153399] [UI] Vertical scrolling becomes unresponsive when hide columns option is used such that the background is visible
https://bugs.documentfoundation.org/show_bug.cgi?id=153399 ady changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3985 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153985] Horrible performance scrolling up with PgUp
https://bugs.documentfoundation.org/show_bug.cgi?id=153985 ady changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3399, ||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3542 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153537] A field should have its own character style
https://bugs.documentfoundation.org/show_bug.cgi?id=153537 --- Comment #3 from tor...@yahoo.com --- (In reply to Dieter from comment #2) > It's already possible to > add a character style to a certain field (by choosing a character style from > character styles list in sidebar). ** From the EditFields window, the character styles list in sidebar is not available. > Your idea is to assign a certain character style to a field while creating > it, correct? **Yes. In the EditFields window, the Format column is active only with Modified_Date/Time. It is inactive if Type is text: Custom, Keywords or Modified/Author; if the Format column is inwere active with text fields, each text field could have its own style —font, fontEffect. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153984] Deleting format doesn't preserve cursor position in the list of formats
https://bugs.documentfoundation.org/show_bug.cgi?id=153984 ady changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3495 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153495] Make an easier workflow for Calc cell user-defined formats cleanup
https://bugs.documentfoundation.org/show_bug.cgi?id=153495 ady changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3984 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148747] Bad use of the date in formulas
https://bugs.documentfoundation.org/show_bug.cgi?id=148747 m.a.riosv changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|NOTABUG |--- Ever confirmed|1 |0 --- Comment #38 from m.a.riosv --- Changed to unconfirmed. Who think it is a bug, change it to 'new' -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148747] Bad use of the date in formulas
https://bugs.documentfoundation.org/show_bug.cgi?id=148747 --- Comment #37 from ady --- > If I change the local setting to English, the apostrophe suddenly appears in > the D1:O1 cells, but when I change to Czech it disappears again. Finally we can see one important factor that makes the difference in our reported experiences. The real question to solve all this is _what_ exactly made older version in Czech to behave as they did whereas newer versions behave differently, making this file fail when they worked before. The change in behavior might be intentional, or might be a bug, but we don't know yet what provoked this change. We also have a locale factor here, when LO in English behaves one way, whereas in Czech it behaves differently. The results of formulas shouldn't be different just because of LO language. These two factors are the reason for me to think that this should not be set as NAB at the moment. Something happened; and the fact that the formulas are not ideal are not relevant in this case, IMO. And @raal thought this too, according to his comments here and in ask.libreoffice.org. > When I switch Locale settings to English, the "Date acceptance patterns" is > set to "M/D/Y;M/D" and this changes the display of dates in the statement, > so then the "calculation" sheet cannot calculate anything. If I set the > English pattern to "D.M.Y;D.M.;D. M.;D. M. Y;D. M.;D. M. Y" , it stays in > the settings, but the date display does not change. "D.M.Y;D.M.;D. M.;D. M. > Y;D. M.;D. M. Y" will only stay there until I switch to another language and > put it back. Then it's back to the original "M/D/Y;M/D". Please don't mix these features. One thing is what Calc will automatically interpret as a date when introducing a value in a cell. Another thing is the cell's format, which can be changed in several ways. If I have a date in a cell that is displayed as "01.2023" (without quotation marks) and it is displayed as "MM.", I could change the cell format to something else, such as "MMM " for example. As I tried to express before, we need to focus on the changed behavior(s), whether they are about the locale in cells, UI language, OS's settings, or some change in some version of LO. Things that seem to be not relevant in this specific bug report, such as how the formulas are built, or how to display a date (e.g. with or without leading zero) should not be a factor to set this report to NEW. > If I overwrite the values with an apostrophe to "01.2022", it switches to > "1.2022", it doesn't stay there "01.2022", but that wouldn't help me anyway, > because the dates in the listing have changed to "D/M/" because of the > Locale setting, which can't be changed. > > > So I can't replicate the fact that when I overwrite the cell with the > apostrophe to the same value, it suddenly starts counting correctly > (non-zero values appear). I can also simply delete the apostrophe, leaving the "1.2022", and the resulting formulas change to non-zero. It is certainly intriguing why you are not able to see the apostrophe when the UI is set to Czech. This is independent of the formulas. Another clue that this must be investigated, instead of setting to NAB. I can only hope that either raal comes with some explanation, and/or Miguel changes his mind, and/or someone else can replicate this with some kind of relevant logical explanation as to why this changed for Czech UI in version 7.2, whereas in English the behavior is a fail with older and with newer versions. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153996] New: Protect Sheet Structure Enhancement
https://bugs.documentfoundation.org/show_bug.cgi?id=153996 Bug ID: 153996 Summary: Protect Sheet Structure Enhancement Product: LibreOffice Version: 7.5.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: gords...@shaw.ca Created attachment 185777 --> https://bugs.documentfoundation.org/attachment.cgi?id=185777&action=edit test file to show validity on an unprotected cell can be changed with sheet protection on In version 7.5.0.3 when the sheet and spreadsheet structure has protection on, the validation rules for unprotected cells can still be changed. Validation rules should not be able to be changed when sheet structure is on, in my opinion. In Excel with workbook protection on, unprotected cells cannot have their validation rules changed. Attached is a test file. Password is test -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153995] No UI for flipping the column order of a table
https://bugs.documentfoundation.org/show_bug.cgi?id=153995 Eyal Rozenberg changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org --- Comment #1 from Eyal Rozenberg --- Should I file a separate bug for the same issue for Writer? As... Writer and Impress/Draw tables are not quite the same. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153995] No UI for flipping the column order of a table
https://bugs.documentfoundation.org/show_bug.cgi?id=153995 Eyal Rozenberg changed: What|Removed |Added Blocks||100366 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=100366 [Bug 100366] [META] Impress/Draw table bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100366] [META] Impress/Draw table bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=100366 Eyal Rozenberg changed: What|Removed |Added Depends on||153995 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153995 [Bug 153995] No UI for flipping the column order of a table -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103100] [META] Writer table bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=103100 Eyal Rozenberg changed: What|Removed |Added Depends on|153995 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153995 [Bug 153995] No UI for flipping the column order of a table -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153995] No UI for flipping the column order of a table
https://bugs.documentfoundation.org/show_bug.cgi?id=153995 Eyal Rozenberg changed: What|Removed |Added Blocks|103100 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103100 [Bug 103100] [META] Writer table bugs -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129661] [META] Right-To-Left (RTL) user interface issues
https://bugs.documentfoundation.org/show_bug.cgi?id=129661 Eyal Rozenberg changed: What|Removed |Added Depends on||153995 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153995 [Bug 153995] No UI for flipping the column order of a table -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103100] [META] Writer table bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=103100 Eyal Rozenberg changed: What|Removed |Added Depends on||153995 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153995 [Bug 153995] No UI for flipping the column order of a table -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153995] No UI for flipping the column order of a table
https://bugs.documentfoundation.org/show_bug.cgi?id=153995 Eyal Rozenberg changed: What|Removed |Added Blocks||129661, 103100 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103100 [Bug 103100] [META] Writer table bugs https://bugs.documentfoundation.org/show_bug.cgi?id=129661 [Bug 129661] [META] Right-To-Left (RTL) user interface issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153995] New: No UI for flipping the column order of a table
https://bugs.documentfoundation.org/show_bug.cgi?id=153995 Bug ID: 153995 Summary: No UI for flipping the column order of a table Product: LibreOffice Version: Inherited From OOo Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com Sometimes, you want to flip the order of columns in a table: Replace columns 1...N with N...1 respectively, with each column keeping its width and formatting - just with their orders reversed. (Possibly you also want the Left and Right border formatting flipped for each column - but maybe not; let's ignore that for now.) There is no UI for doing that, and probably no code either. There should be! When we want to switch the direct of a paragraph, we can do that; so - why not also that of a table? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153975] Win11 BSOD when I click LibreOfc "Help"
https://bugs.documentfoundation.org/show_bug.cgi?id=153975 --- Comment #4 from Frank Moore --- Furthermore, now, in 7.5.1.2, when I open a document, I get the error message: Error loading BASIC of document file:///C:/Users/Franklin%20Moore/AppData/Roaming/LibreOffice/4/user/ basic/Standard/dialog.xlb/: General Error. General input/output error. When I "OK" the error away, the document seems to edit, save, etc normally. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103341] [META] AutoCorrect and Word Completion bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103341 Eyal Rozenberg changed: What|Removed |Added Depends on||153994 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153994 [Bug 153994] Sidebar character deck/tab shows Western font with no excuse -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 43808] [META] Right-To-Left and Complex Text Layout language issues (RTL/CTL)
https://bugs.documentfoundation.org/show_bug.cgi?id=43808 Eyal Rozenberg changed: What|Removed |Added Depends on||153994 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153994 [Bug 153994] Sidebar character deck/tab shows Western font with no excuse -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153994] Sidebar character deck/tab shows Western font with no excuse
https://bugs.documentfoundation.org/show_bug.cgi?id=153994 Eyal Rozenberg changed: What|Removed |Added Blocks||43808, 103341 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=43808 [Bug 43808] [META] Right-To-Left and Complex Text Layout language issues (RTL/CTL) https://bugs.documentfoundation.org/show_bug.cgi?id=103341 [Bug 103341] [META] AutoCorrect and Word Completion bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153994] New: Sidebar character deck/tab shows Western font with no excuse
https://bugs.documentfoundation.org/show_bug.cgi?id=153994 Bug ID: 153994 Summary: Sidebar character deck/tab shows Western font with no excuse Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com If you have a textbox with RTL direction and only RTL text inside, and you select it - but not go into edit mode, the character deck/tab of the sidebar will show you the Western language group font family, size, bold Y/N and italic Y/N - instead of showing you these properties for the RTL language group font. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153975] Win11 BSOD when I click LibreOfc "Help"
https://bugs.documentfoundation.org/show_bug.cgi?id=153975 --- Comment #3 from Frank Moore --- Stéphane: Yes, I still see the issue. I renamed my user profile, then installed 7.5.1.2 on top of the previous install. After loading LibreOffice, I clicked "Help", and after perhaps one or two seconds of the Help page loading, Win11 went instantly to BSOD. Thanks for the suggestion. Frank -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108728] [META] Dictionaries bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108728 Bug 108728 depends on bug 153736, which changed state. Bug 153736 Summary: British English Dictionary contains Americanisms https://bugs.documentfoundation.org/show_bug.cgi?id=153736 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153736] British English Dictionary contains Americanisms
https://bugs.documentfoundation.org/show_bug.cgi?id=153736 Marco A.G.Pinto changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153993] New: FORMATTING: Calc alters custom number format on save
https://bugs.documentfoundation.org/show_bug.cgi?id=153993 Bug ID: 153993 Summary: FORMATTING: Calc alters custom number format on save Product: LibreOffice Version: 7.5.1.2 release Hardware: x86-64 (AMD64) OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: m...@keveney.com -- Tested on MacOS Ventura 13.2.1 Libreoffice 7.5.1.2, build: fcbaee479e84c6cd81291587d2ee68cba099e129 -- To reproduce: Launch LibreOffice Click "Create/Calc Spreadsheet" Enter the following in cells A1-A3: 123.456 1234.56 12345.6 Select these three cells Click "Format/Cells..." In the "Category" list, click "User-defined" In Format code enter: "###.000 e0" ..but without the quotes Click the 'add' button (bearing the green checkmark) Note that: the "Category" switches to "Scientific" the new format appears as expected the example is formatted as desired (with a lowercase 'e' preceeded by a space) Under category, click "User-defined" Verify that the new format appears here as well. Click OK Verify that the three cells are formatted as desired: 123.456 e0 1.235 e3 12.346 e3 Click "File/Save," give the document a name, and click "Save" Close the file, then close Libreoffice Reopen the file. Note that the cells are now formatted as: 123.456E0 1.235E3 12.346E3 Click "Format/Cells" Note that the format has been altered to: ###.000E0" " Note that this altered format appears in both categories: "User-defined" and "Scientific" -- Expected result: Format should be saved as entered. Or, if the format is erroneous, it should be corrected _immediately_, rather than waiting until the document is saved/reopened. -- Documentation The documentation is not entirely clear on whether a space is acceptable before the "e" in this style format. (Though this reporter would appreciate it!) The documentation _does_ say that a lowercase "e" should be OK, but LibreOffice does not preserve it. -- similar bug? Bugs 146404 and 152724 seem very similar, though this reporter can't be sure it's the same underlying issue. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153736] British English Dictionary contains Americanisms
https://bugs.documentfoundation.org/show_bug.cgi?id=153736 --- Comment #8 from Stéphane Guillou (stragu) --- Fabulous, thank you Marco for the update! Please go ahead and mark this report as "resolved - fixed". -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 59284] [META] Cell border related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=59284 Bug 59284 depends on bug 124496, which changed state. Bug 124496 Summary: Adding diagonal borders to cells while EDITING calc file messes the file https://bugs.documentfoundation.org/show_bug.cgi?id=124496 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124496] Adding diagonal borders to cells while EDITING calc file messes the file
https://bugs.documentfoundation.org/show_bug.cgi?id=124496 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|--- |WORKSFORME CC||stephane.guillou@libreoffic ||e.org Status|NEW |RESOLVED OS|Windows (All) |All --- Comment #18 from Stéphane Guillou (stragu) --- This seems to have been fixed since 7.3. I can't reproduce in: Version: 7.3.7.2 / LibreOffice Community Build ID: e114eadc50a9ff8d8c8a0567d6da8f454beeb84f CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded But I could in: Version: 7.2.7.2 / LibreOffice Community Build ID: 8d71d29d553c0f7dcbfa38fbfda25ee34cce99a2 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153660] Single Undo should remove all diagonal borders created with Toolbar>Borders
https://bugs.documentfoundation.org/show_bug.cgi?id=153660 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Blocks||59284 Whiteboard| QA:needsComment| CC||stephane.guillou@libreoffic ||e.org --- Comment #1 from Stéphane Guillou (stragu) --- Thanks Timur. With criss-cross, sometimes even two undo actions are not enough and some diagonal "borders" remain with no undo action left. With "diagonal up" and "diagonal down", only one undo action is available, and sometimes it removes everything, sometimes only a part, sometimes nothing. Tested with both the toolbar and the sidebar. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: feda414f8b70f50a9f6745d2ce8828316d4711cd CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=59284 [Bug 59284] [META] Cell border related issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 59284] [META] Cell border related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=59284 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||153660 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153660 [Bug 153660] Single Undo should remove all diagonal borders created with Toolbar>Borders -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153736] British English Dictionary contains Americanisms
https://bugs.documentfoundation.org/show_bug.cgi?id=153736 --- Comment #7 from Marco A.G.Pinto --- A… sorry… I forgot to say that I added the words, you can find them in the latest GB dictionary. See the wordlist here: https://proofingtoolgui.org https://proofingtoolgui.org/wordlist_marcoagpinto_20230301_270569w.txt The “cyberorganisation” wasn't added because it doesn't appear in the dictionaries. I spoke with a person from England who suggests words for the dictionary, and he said that in the UK it is written with a hyphen: “cyber-organisation”. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153402] English (en-us) Spellcheck overactive (acceptable spelling "briar" flagged as incorrect)
https://bugs.documentfoundation.org/show_bug.cgi?id=153402 --- Comment #3 from Marco A.G.Pinto --- Heya, I was checking the British wordlist, and it already has: briar briars briar's briary brier briers brier's If it is missing in the US dictionary, that is a task for Kevin Atkinson: https://github.com/en-wl/wordlist He maintains the US. Anyway, to check if a British (Common Wealth) word is in the latest GB dictionary, click on the wordlist link in the table at the top right of my website: https://proofingtoolgui.org As I write this, the link points to: https://proofingtoolgui.org/wordlist_marcoagpinto_20230301_270569w.txt Thanks! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 86066] [META] Bugs and improvements to the status bar
https://bugs.documentfoundation.org/show_bug.cgi?id=86066 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||153731 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153731 [Bug 153731] Two problems with clicking on [List Level] section in the Status bar -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153731] Two problems with clicking on [List Level] section in the Status bar
https://bugs.documentfoundation.org/show_bug.cgi?id=153731 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||86066 Version|7.6.0.0 alpha0+ Master |Inherited From OOo CC||stephane.guillou@libreoffic ||e.org Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from Stéphane Guillou (stragu) --- Thanks Seth. I agree with everything, this can be greatly improved and made more useful and consistent. One note though: for issue 2, although the Chapter Numbering dialog would be a better fit, one can still modify the chapter numbering using the Bullets and Numbering dialog. It is functional, but not ideal nor expected. Tested with: Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded and: OpenOffice.org 3.3.0 OOO330m20 (Build:9567) (at least the issue with the Heading/Outline was inherited) Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=86066 [Bug 86066] [META] Bugs and improvements to the status bar -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141773] Autocorrection for all languages doesn't work anymore
https://bugs.documentfoundation.org/show_bug.cgi?id=141773 László Németh changed: What|Removed |Added Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153991] Sidebar panel character deck/tab doesn't allow switching language groups
https://bugs.documentfoundation.org/show_bug.cgi?id=153991 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3992 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129661] [META] Right-To-Left (RTL) user interface issues
https://bugs.documentfoundation.org/show_bug.cgi?id=129661 Eyal Rozenberg changed: What|Removed |Added Depends on||153992 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153992 [Bug 153992] Sidebar character deck/tab doesn't indicate the current language/language group -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153992] Sidebar character deck/tab doesn't indicate the current language/language group
https://bugs.documentfoundation.org/show_bug.cgi?id=153992 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3991 Blocks||112629, 129661 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=112629 [Bug 112629] [META] Character content panel of the Properties deck/tab of the sidebar https://bugs.documentfoundation.org/show_bug.cgi?id=129661 [Bug 129661] [META] Right-To-Left (RTL) user interface issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112629] [META] Character content panel of the Properties deck/tab of the sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=112629 Eyal Rozenberg changed: What|Removed |Added Depends on||153992 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153992 [Bug 153992] Sidebar character deck/tab doesn't indicate the current language/language group -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153992] New: Sidebar character deck/tab doesn't indicate the current language/language group
https://bugs.documentfoundation.org/show_bug.cgi?id=153992 Bug ID: 153992 Summary: Sidebar character deck/tab doesn't indicate the current language/language group Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com The character tab/deck of the sidebar shows all sorts of information about your font: Family, size, bold Y/N, Italic Y/N and others. Many of these - specifically, the ones I mentioned - are actually defined separately for each language group: Western, RTL-CTL and CJK. But the tab/deck does not tell us _which_ language group it's currently showing controls for. This can be quite confusing when working on text with mixed language groups - and when the same font family may be used for multiple language groups. Of course, if LO only has one language group enabled (i.e. Asian/CJK scripts and RTL/CTL scripts are disabled via options) - then indicating the language group is not necessary. Now, as for _how_ to indicate the language group... that's not entirely obvious. Some possibilities: * If a control for the language is added, that might be a sufficient surrogate * If a control for switching language groups is added (see bug 153991), then hovering over it could tell us what it would do, in a tooltip, e.g. the tooltip could say "Western -> RTL", then when you click it, "RTL -> CJK", then again "CJK -> Western" - and you would know that the group on the starting side is the active one. * If a control for switching language groups is added (see bug 153991), and its big enough, it could say "CJK", "RTL" or "Wes". Or something more graphic instead. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108728] [META] Dictionaries bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108728 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||153736 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153736 [Bug 153736] British English Dictionary contains Americanisms -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153736] British English Dictionary contains Americanisms
https://bugs.documentfoundation.org/show_bug.cgi?id=153736 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||108728 URL||https://github.com/marcoagp ||into/aoo-mozilla-en-dict/is ||sues/55 Ever confirmed|0 |1 CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |NEW --- Comment #6 from Stéphane Guillou (stragu) --- Marking as new according to comments. Marco, please feel free to assign yourself to this bug. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108728 [Bug 108728] [META] Dictionaries bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107733] [META] Hyperlink bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107733 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||153740 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153740 [Bug 153740] In Writer, there should be 3 types of hyperlinks -- You are receiving this mail because: You are the assignee for the bug.
