[Libreoffice-bugs] [Bug 58521] Endnotes always start on a new page, no option to have it directly at the end (unless using sections)
https://bugs.documentfoundation.org/show_bug.cgi?id=58521 raal changed: What|Removed |Added CC||aarush0...@gmail.com --- Comment #42 from raal --- *** Bug 156086 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156086] Does Libreoffice support Endnote separator in docx file?
https://bugs.documentfoundation.org/show_bug.cgi?id=156086 raal changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from raal --- Hello, Thank you for submitting the bug. The bug has previously been reported, so this bug will be added as a duplicate of it. You will automatically be CCed to updates made to the other bug. *** This bug has been marked as a duplicate of bug 58521 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156120] The content is displaying distortion in the resulting image file when I export my odt file to an image.
https://bugs.documentfoundation.org/show_bug.cgi?id=156120 --- Comment #1 from wib...@qq.com --- Created attachment 188155 --> https://bugs.documentfoundation.org/attachment.cgi?id=188155=edit must use this file to reproduce the bug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156121] New: Autocorrect -> Apply and Edit Changes misbehaves
https://bugs.documentfoundation.org/show_bug.cgi?id=156121 Bug ID: 156121 Summary: Autocorrect -> Apply and Edit Changes misbehaves Product: LibreOffice Version: unspecified Hardware: All URL: https://ask.libreoffice.org/t/autocorrect-doesnt-repla ce-with-m-dash/93097 OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mikekagan...@hotmail.com In a text document, *paste* (not type) the following text: :---: foo :---: Execute Tools->Autocorrect->Apply and Edit Changes Expected: — foo — Actual: :---: foo :---: (Indeed, there is also a dialog, and the tracking changes; I only show the result of replacement, as suggested by the dialog.) = Now start over, and instead of the previous line, paste :---: foo bar :---: and execute Tools->Autocorrect->Apply and Edit Changes Expected: — foo bar — Actual: :---: foo bar — In general, an expectation is that the result or autocorrection is the same as if one types the text interactively. Ref: https://ask.libreoffice.org/t/autocorrect-doesnt-replace-with-m-dash/93097 Code pointer (not an easyhack IMO): SwAutoFormat::SwAutoFormat in sw/source/core/edit/autofmt.cxx -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156120] New: The content is displaying distortion in the resulting image file when I export my odt file to an image.
https://bugs.documentfoundation.org/show_bug.cgi?id=156120 Bug ID: 156120 Summary: The content is displaying distortion in the resulting image file when I export my odt file to an image. Product: LibreOffice Version: 7.5.4.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: wib...@qq.com Description: As summarized, I opened my odt file and selected [Export] from the [File] menu. Then I selected JPEG or PNG from the [Save as type] option and saved it to a local drive path as a jpg or png file. However, the resulting file displayed distortion when opened. Steps to Reproduce: 1. open my odt file and select [Export] from the [File] menu. 2. select JPEG or PNG from the [Save as type] option and saved it to a local drive path as a jpg or png file. 3. open the resulting file. Actual Results: displayed distortion Expected Results: displayed normal as it was shown in the original odt file Reproducible: Always User Profile Reset: No Additional Info: with specified file I would upload -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156112] Footnotes and endnotes can be hyperlinked by drag-and-drop from Navigator, but link is not functional
https://bugs.documentfoundation.org/show_bug.cgi?id=156112 Jim Raykowski changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #1 from Jim Raykowski --- Patch to not allow footnote and endnote dnd: https://gerrit.libreoffice.org/c/core/+/153855 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155890] Changing page direction misplaces end-of-paragraph pilcrow
https://bugs.documentfoundation.org/show_bug.cgi?id=155890 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 156102] Ctrl+brackets (ctrl+[ and ctrl+]) does not work on Windows with different keyboard layouts
https://bugs.documentfoundation.org/show_bug.cgi?id=156102 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 156102] Ctrl+brackets (ctrl+[ and ctrl+]) does not work on Windows with different keyboard layouts
https://bugs.documentfoundation.org/show_bug.cgi?id=156102 --- 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 155900] Font color in pdf, created from impress ppt/odp file, is reduced to black for bold text.
https://bugs.documentfoundation.org/show_bug.cgi?id=155900 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 155895] general protection fault when try to destroy LibreOfficeKit
https://bugs.documentfoundation.org/show_bug.cgi?id=155895 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 156086] Does Libreoffice support Endnote separator in docx file?
https://bugs.documentfoundation.org/show_bug.cgi?id=156086 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 107787] Gradients steps don't save
https://bugs.documentfoundation.org/show_bug.cgi?id=107787 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 156086] Does Libreoffice support Endnote separator in docx file?
https://bugs.documentfoundation.org/show_bug.cgi?id=156086 --- 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 107787] Gradients steps don't save
https://bugs.documentfoundation.org/show_bug.cgi?id=107787 --- Comment #38 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146067] MA trend lines are displayed with inconsistent X offset, depending on the label values
https://bugs.documentfoundation.org/show_bug.cgi?id=146067 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 146067] MA trend lines are displayed with inconsistent X offset, depending on the label values
https://bugs.documentfoundation.org/show_bug.cgi?id=146067 --- Comment #14 from QA Administrators --- Dear Hernan, 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 111443] [META] Unsupported formats in LibreOffice Viewer
https://bugs.documentfoundation.org/show_bug.cgi?id=111443 Bug 111443 depends on bug 111721, which changed state. Bug 111721 Summary: Add support for Tagged Image File Format ( .tiff ) https://bugs.documentfoundation.org/show_bug.cgi?id=111721 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 111721] Add support for Tagged Image File Format ( .tiff )
https://bugs.documentfoundation.org/show_bug.cgi?id=111721 --- Comment #3 from QA Administrators --- Dear vihsa, 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 111721] Add support for Tagged Image File Format ( .tiff )
https://bugs.documentfoundation.org/show_bug.cgi?id=111721 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 152787] EDITING: Base Crashes When Selecting “Sorting and Grouping” in Reports
https://bugs.documentfoundation.org/show_bug.cgi?id=152787 --- Comment #10 from QA Administrators --- Dear DougL, 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 148412] TexMath does not install on version 7.2.6
https://bugs.documentfoundation.org/show_bug.cgi?id=148412 --- Comment #3 from QA Administrators --- Dear Ntamu, 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 148280] Calc, Autofill erases existing data when aborted
https://bugs.documentfoundation.org/show_bug.cgi?id=148280 --- Comment #3 from QA Administrators --- Dear Oby, 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 148106] Setting a line in a chart to "ignore blanks" does not get saved.
https://bugs.documentfoundation.org/show_bug.cgi?id=148106 --- Comment #2 from QA Administrators --- Dear Brian Quarterman, 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 95150] Border of tablecontrol doesn't show color
https://bugs.documentfoundation.org/show_bug.cgi?id=95150 --- Comment #12 from QA Administrators --- Dear Robert Großkopf, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143137] FORMNAVIGATION: When switching from Form to "Data source as Table" last changes won't be saved
https://bugs.documentfoundation.org/show_bug.cgi?id=143137 --- Comment #3 from QA Administrators --- Dear Robert Großkopf, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142887] EXPORT HTML: exported shape (gif) is slightly cropped on the bottom and right side (round becomes flat)
https://bugs.documentfoundation.org/show_bug.cgi?id=142887 --- Comment #3 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 142725] Page numbers not removed from ToC when saved to HTML
https://bugs.documentfoundation.org/show_bug.cgi?id=142725 --- Comment #6 from QA Administrators --- Dear Chris Y., 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 65200] FORMATTING: Autofit width not behave properly if cell(s) contain text wrapping
https://bugs.documentfoundation.org/show_bug.cgi?id=65200 --- Comment #11 from QA Administrators --- Dear ign_christian, 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 125430] Very minor UI glitch: some select boxes have smaller issues
https://bugs.documentfoundation.org/show_bug.cgi?id=125430 --- Comment #5 from QA Administrators --- Dear Nicolas Christener, 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 120241] Chapter numbering not saved as ordered list when saving or exporting to HTML (see comment 5)
https://bugs.documentfoundation.org/show_bug.cgi?id=120241 --- Comment #11 from QA Administrators --- Dear Bernard TREMBLAY, 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 115467] Unticking "Master background" in slide properties makes formatted background go away
https://bugs.documentfoundation.org/show_bug.cgi?id=115467 --- Comment #11 from QA Administrators --- Dear David F Smith, 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 108372] Inserting references using Zotero and Writer results in single line spacing
https://bugs.documentfoundation.org/show_bug.cgi?id=108372 --- Comment #6 from QA Administrators --- Dear Andreas, 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 153721] Rename "Move Chapter Up/Down" to "Move Heading+Text Up/Down" in Navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=153721 --- Comment #32 from Jim Raykowski --- (In reply to sdc.blanco from comment #22) > Is there any reason why this feature cannot be active in the other mode of > Navigator? > (which would then make the move up/down commands irrelevant in the context > menu). Here is a patch that makes this feature active in the other mode of the Navigator: https://gerrit.libreoffice.org/c/core/+/153854 In addition to making the feature active in all content navigation view mode effort to improve a few other things Navigator related are include. Please see the patch commit message for details. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102593] [META] Paste bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102593 Bug 102593 depends on bug 155452, which changed state. Bug 155452 Summary: When pasting image from Firefox in Calc, pasted image is not visible (only paste frame) https://bugs.documentfoundation.org/show_bug.cgi?id=155452 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105584] [META] Calc image bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=105584 Bug 105584 depends on bug 155452, which changed state. Bug 155452 Summary: When pasting image from Firefox in Calc, pasted image is not visible (only paste frame) https://bugs.documentfoundation.org/show_bug.cgi?id=155452 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155452] When pasting image from Firefox in Calc, pasted image is not visible (only paste frame)
https://bugs.documentfoundation.org/show_bug.cgi?id=155452 Aron Budea changed: What|Removed |Added Status|NEW |RESOLVED Whiteboard||target:24.2.0 target:7.6.0 Resolution|--- |FIXED --- Comment #15 from Aron Budea --- Should be fixed by the following commits in 24.02 and 7.6.0: https://cgit.freedesktop.org/libreoffice/core/commit/?id=46fa17b70db0d543518dde52908f46c85838ac12 author Luigi Iucci 2023-06-21 10:16:16 +0200 committer Henry Castro 2023-06-26 16:40:14 +0200 "problem pasting to calc an image copied from firefox (windows)" https://cgit.freedesktop.org/libreoffice/core/commit/?id=adaae622b67f525e0fb58af848a7cece8ac65f45 author Luigi Iucci 2023-06-21 10:16:16 +0200 committer Xisco Fauli 2023-06-28 13:10:52 +0200 "problem pasting to calc an image copied from firefox (windows)" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156102] Ctrl+brackets (ctrl+[ and ctrl+]) does not work on Windows with different keyboard layouts
https://bugs.documentfoundation.org/show_bug.cgi?id=156102 --- Comment #3 from Hossein --- (In reply to Stéphane Guillou (stragu) from comment #2) > Hossein, does Ctrl + Shift + [ or ] work? > Does this match your layout? https://i.stack.imgur.com/rTueJ.png The above picture of the Persian keyboard layout is correct. But, Ctrl + Shift + [ or ] also do not work for me. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156119] New: When scrolling, the image of the page disappears.
https://bugs.documentfoundation.org/show_bug.cgi?id=156119 Bug ID: 156119 Summary: When scrolling, the image of the page disappears. Product: LibreOffice Version: 7.4.4.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: hegyitom...@gmail.com Description: When scrolling, the image of the page disappears. After I adjusted the frame on the first and second pages, the phenomenon disappeared. (The document was previously created with Microsoft Word) I also made a video about the phenomenon, here is the link: https://drive.google.com/file/d/13mFg-HdH0fd9pFMztDcQ6rDvDR_e2hnC/view?usp=sharing Actual Results: https://drive.google.com/file/d/13mFg-HdH0fd9pFMztDcQ6rDvDR_e2hnC/view?usp=sharing Expected Results: the error is gone Reproducible: Always User Profile Reset: No Additional Info: Always show page content -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156118] Calc displays multiline entries on one line
https://bugs.documentfoundation.org/show_bug.cgi?id=156118 --- Comment #4 from bugzilla00c6...@engineduster.com --- Created attachment 188154 --> https://bugs.documentfoundation.org/attachment.cgi?id=188154=edit screenshot of multiline overlay -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156118] Calc displays multiline entries on one line
https://bugs.documentfoundation.org/show_bug.cgi?id=156118 bugzilla00c6...@engineduster.com changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #3 from bugzilla00c6...@engineduster.com --- (In reply to m.a.riosv from comment #1) > I can't reproduce. > Version: 7.5.4.2 (X86_64) / LibreOffice Community > Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 > CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: default; VCL: win > Locale: es-ES (es_ES); UI: en-US Calc: CL threaded > > Please, can you attach a sample file. > > Test clearing the direct format in the cell [Ctrl+M] > or Please test with a clean profile, Menu/Help/Restart in Safe Mode As stated in the bug report, I did use a clean profile. I created a new file for you (and also tested clearing formatting which didn't help). This happens with new files as well as with every saved file I have. I bet if someone else sent me one it would open with overlaid text as well. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156118] Calc displays multiline entries on one line
https://bugs.documentfoundation.org/show_bug.cgi?id=156118 --- Comment #2 from bugzilla00c6...@engineduster.com --- Created attachment 188153 --> https://bugs.documentfoundation.org/attachment.cgi?id=188153=edit multiline overlay sample -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156118] Calc displays multiline entries on one line
https://bugs.documentfoundation.org/show_bug.cgi?id=156118 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #1 from m.a.riosv --- I can't reproduce. Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: default; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Please, can you attach a sample file. Test clearing the direct format in the cell [Ctrl+M] or Please test with a clean profile, Menu/Help/Restart in Safe Mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156117] FORMATTING: 'Find and Replace' Style Errors ('Replace All' and 'Replace')
https://bugs.documentfoundation.org/show_bug.cgi?id=156117 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |NEW --- Comment #5 from m.a.riosv --- Maybe the same issue as in https://bugs.documentfoundation.org/show_bug.cgi?id=144299 Reproducible Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e836e69eb6f2f01a475c5679fb338dda7936643f CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156118] New: Calc displays multiline entries on one line
https://bugs.documentfoundation.org/show_bug.cgi?id=156118 Bug ID: 156118 Summary: Calc displays multiline entries on one line Product: LibreOffice Version: 7.5.4.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: bugzilla00c6...@engineduster.com Description: Cacl no longer respects ctrl-enter. It displays multi-lines on top of one another instead of on separate lines. Steps to Reproduce: 1. type text into cell 2. hit ctrl-enter 3. type more text Actual Results: the two lines of text are displayed overlaid Expected Results: two separate lines of text Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156113] Calc, Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=156113 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #1 from m.a.riosv --- Please test updating to 7.5, some work was development in it. https://www.libreoffice.org/download/download-libreoffice/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107805] [META] Writer master document issues
https://bugs.documentfoundation.org/show_bug.cgi?id=107805 Bug 107805 depends on bug 155740, which changed state. Bug 155740 Summary: Support distinction rather than override of conflicting subdocument styles https://bugs.documentfoundation.org/show_bug.cgi?id=155740 What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|NOTABUG |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155740] Support distinction rather than override of conflicting subdocument styles
https://bugs.documentfoundation.org/show_bug.cgi?id=155740 Eyal Rozenberg changed: What|Removed |Added Resolution|NOTABUG |--- Status|RESOLVED|UNCONFIRMED --- Comment #7 from Eyal Rozenberg --- (In reply to Mike Kaganski from comment #6) > Definitely not a bug I explicitly said in comment #0 that this is not a bug - it's an enhancement request. > and a WONTFIX. It is impolite to mark an issue WONTFIX based on UX considerations when you're not, say, Heiko, without first waiting for a reply to your claim. If you had made a development consideration (e.g. "impelementing this introduces exponential time complexity for rendering") - then maybe it would be legitimate. Or if the reporter were a known crank. etc. > The most important idea behind the master documents is exactly being able to > centrally configure styles. 1. That is not the most important idea. The most important idea is having a document composed of individual, existing documents "by reference" rather than "by value", i.e. not by concatenating copies of the existing documents. 2. "Centrally configure" does not necessarily being with "delete non-central configurations". > The premise that styles in sub-documents are > "discarded" is wrong, and they are "overridden" *temporarily*, i.e. when you > open a sub-document by itself, they will keep the original properties. They are discarded in the context of the larger document. And I explained and gave an example of when the user may want them kept rather than discarded. > Among > other things, this allows a kind of "css", when different master documents > override same styles in different ways. I never said the user _never_ wants to override sub-document styles. I'm saying the user _sometimes_ wants to override, and sometimes - to keep. > If one wants some distinction in their *part* of a multi=part document, they > need to create new styles (or use ad-hoc formatting, if it's a single-use > case). No, they don't. They created a self-contained, perfectly valid document - as well they should have. In fact, they probably need to _not_ create new artificial styles; documents should definitely use styles with the common names (e.g. Footnote, Emphasis, Internet Link etc. etc.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156089] When setting the Heading/Outline Numbering for a level to "None", still getting separators
https://bugs.documentfoundation.org/show_bug.cgi?id=156089 --- Comment #4 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #3) > ODF allows this and I see no harm in this flexibility. "None" just doesn't > mean no numbering but no (automatic) numbers/chars. Agree with Justin on NAB. I did not suggest that the user not be able to insist on these, i.e. I did not suggest the separator textboxes be cleared _and disabled_. I'm just saying that the assumption regarding the common case is wrong, so that the textboxes should be _cleared_. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156101] Thesaurus supposedly enabled, but grayed out in UI
https://bugs.documentfoundation.org/show_bug.cgi?id=156101 --- Comment #10 from Eyal Rozenberg --- (In reply to Caolán McNamara from comment #8) > yeah, likely this new en-IL need to be added to > https://cgit.freedesktop.org/libreoffice/dictionaries/tree/en/dictionaries. > xcu > in the various sections. > > We have only one thesarus so the ThesDic_en-US section is simple. > > For the others the spelling variant GB vs US matters. From: > https://www.guyrutenberg.com/2016/04/16/en_il-english-locale-for-israel/ > I imagine en-IL should slot into HyphDic_en-US and HunSpellDic_en-US But why is there no per-language fallback, for when the locale is missing? Tomorrow someone will complain about en-JO or en-PA or en-EG etc. Of course, you could ask me to open a separate bug about that. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156101] Thesaurus supposedly enabled, but grayed out in UI
https://bugs.documentfoundation.org/show_bug.cgi?id=156101 Caolán McNamara changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #9 from Caolán McNamara --- lets try https://gerrit.libreoffice.org/c/dictionaries/+/153852 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156101] Thesaurus supposedly enabled, but grayed out in UI
https://bugs.documentfoundation.org/show_bug.cgi?id=156101 --- Comment #8 from Caolán McNamara --- yeah, likely this new en-IL need to be added to https://cgit.freedesktop.org/libreoffice/dictionaries/tree/en/dictionaries.xcu in the various sections. We have only one thesarus so the ThesDic_en-US section is simple. For the others the spelling variant GB vs US matters. From: https://www.guyrutenberg.com/2016/04/16/en_il-english-locale-for-israel/ I imagine en-IL should slot into HyphDic_en-US and HunSpellDic_en-US -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156117] FORMATTING: 'Find and Replace' Style Errors ('Replace All' and 'Replace')
https://bugs.documentfoundation.org/show_bug.cgi?id=156117 --- Comment #4 from Jeffrey Alan Klute --- Created attachment 188152 --> https://bugs.documentfoundation.org/attachment.cgi?id=188152=edit This shows the Search Results for 'Header1' after 'Replace All' (510 results, there should be 291) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156117] FORMATTING: 'Find and Replace' Style Errors ('Replace All' and 'Replace')
https://bugs.documentfoundation.org/show_bug.cgi?id=156117 --- Comment #3 from Jeffrey Alan Klute --- Created attachment 188151 --> https://bugs.documentfoundation.org/attachment.cgi?id=188151=edit This shows the Search Results for style 'ToBeDeleted' after 'Replace All' (284 results, there should be zero) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156117] FORMATTING: 'Find and Replace' Style Errors ('Replace All' and 'Replace')
https://bugs.documentfoundation.org/show_bug.cgi?id=156117 --- Comment #2 from Jeffrey Alan Klute --- Created attachment 188150 --> https://bugs.documentfoundation.org/attachment.cgi?id=188150=edit This is how Find and Replace s/b configured before 'Replace All' -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156117] FORMATTING: 'Find and Replace' Style Errors ('Replace All' and 'Replace')
https://bugs.documentfoundation.org/show_bug.cgi?id=156117 --- Comment #1 from Jeffrey Alan Klute --- Created attachment 188149 --> https://bugs.documentfoundation.org/attachment.cgi?id=188149=edit In the initial bug report I refer to this as *Test.ods *Test.ods contains a style named 'ToBeDeleted' (applied in 291 cells) and another style named 'Header1' (not yet applied to any cells) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156117] New: FORMATTING: 'Find and Replace' Style Errors ('Replace All' and 'Replace')
https://bugs.documentfoundation.org/show_bug.cgi?id=156117
Bug ID: 156117
Summary: FORMATTING: 'Find and Replace' Style Errors ('Replace
All' and 'Replace')
Product: LibreOffice
Version: 7.4.7.2 release
Hardware: x86 (IA32)
OS: Windows (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Calc
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: j...@datavisionservices.com
Description:
In the provided *Test.ods 'Replace All' replaces many cell styles that weren't
searched for. On my system the bug happens very frequently, it's repeatable,
and on a very stable/clean installation of windows and LibreOffice. The bug
involves a major component that would affect many users who manage Style
changes using Find and Replace.
Steps to Reproduce:
1. Open '20230701 Find and Replace Style Test.ods'
2. Open the Find and Replace dialog (Ctl+H)
Select 'All sheets'; Select 'Cell Styles' (Other options)
In 'Find:' select style 'ToBeDeleted'; In 'Replace:' select style 'Header1'
Click on 'Find All' and see the Search Results showing "291 results found"
['20230701.1 Screenshot.png' shows how every thing should look at this point]
3. Click on 'Replace All' and see the Search Results showing "291 results
found"
4. Click again on 'Find All' and see the Search Results now shows there are yet
"284 results found" (there should be zero results after replacing them all)
[see '20230701.2 Screenshot.png']
5. In 'Find:' select style 'Header1'
Click on 'Find All' and see the Search Results now shows there are "510 results
found" (there should be 291)
[see '20230701.3 Screenshot.png']
Actual Results:
'Replace All' replaces many cell styles that are not being searched for, and
does not replace many cell styles it was searching for that should have been
replaced
Expected Results:
'Replace All' should replace 291 cells containing the style 'ToBeDeleted' with
the style 'Header1'
After 'Replace All' there should be zero cells with style 'ToBeDeleted' and 291
cells with style 'Header1'
Reproducible: Always
User Profile Reset: Yes
Additional Info:
Version: 7.4.7.2 (x86) / LibreOffice Community
Build ID: 723314e595e8007d3cf785c16538505a1c878ca5
CPU threads: 2; OS: Windows 6.1 Service Pack 1 Build 7601; UI render:
Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded
Final Notes
It can be seen when playing with the (virgin) *Test.ods that a single 'Replace'
replaces the next style occurrence found (and not the currently focused cell
that should be replaced). In other words, each single replacement is not for
the cell found, but the next occurrence of a cell found with the style to be
replaced.
The *Test.ods is a copy of a spreadsheet in critical and regular use in my
small business: The workaround I had to employ to get past this bug in the test
case was to not use 'Replace All' but instead click 'Replace' 291 times. This
avoids the corruption of cells not searched for that is introduced if using
'Replace All'.
Thank you for your time in looking into this: There's a lot more work to be
done with Styles on this spreadsheet, so I hope we can come up with answers.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153142] IsMissing needs a note about use in conditions (no boolean short-circuit evaluation in Basic)
https://bugs.documentfoundation.org/show_bug.cgi?id=153142 --- Comment #10 from Jordi --- Has this change to disable short-circuiting already been implemented? Because this bug report still says NEW, but when I moved my code from 7.0.5.x to 7.4.7.2 (stable release) it failed in a couple of places. PS: I was scratching my head why my code was failing all of a sudden and went looking into the release notes but google couldn't find anything there. Should it be there? Seems like a major change. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155211] Dashed lines become solid when breaking/converting SVG imported image in Draw (regression introduced from LO 7.1)
https://bugs.documentfoundation.org/show_bug.cgi?id=155211 Stéphane Guillou (stragu) changed: What|Removed |Added Priority|medium |high CC||xiscofa...@libreoffice.org --- Comment #7 from Stéphane Guillou (stragu) --- Increasing the priority as it's a regression that affects a long-standing, currently maintained extension. Xisco, with Roland's pointers, do you know who might be able to help? Or are you interested yourself? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 31480] Find/replace non-printing characters easily
https://bugs.documentfoundation.org/show_bug.cgi?id=31480 --- Comment #104 from Naga Petir --- These are some informative site that you can visit and gain much more knowledge. http://whl.sttbkpalu.ac.id/ https://ssh.hch24.com/ -- 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 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||155407 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=155407 [Bug 155407] Incorrect autocorrection of double dashes in a specific situation -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156046] Autocorrect replaces " - " with " – " instead of " — " (en-dash instead of em-dash)
https://bugs.documentfoundation.org/show_bug.cgi?id=156046 --- Comment #7 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #5) also... > EM by three. I think we do a good job with converting it. Actually, we don't quite, please have a look at bug 147681. But again, unrelated to what happens to text with a single hyphen where the user did not explicitly indicate what dashes they want. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147681] Autotext replacement not willing to ignore parenthesis before shortcut "---"
https://bugs.documentfoundation.org/show_bug.cgi?id=147681 Stéphane Guillou (stragu) changed: What|Removed |Added Version|7.4.0.0 alpha0+ |Inherited From OOo See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||6589 CC||stephane.guillou@libreoffic ||e.org --- Comment #6 from Stéphane Guillou (stragu) --- Confirmed that AutoText will use the closest string of non-space characters that's only composed of either alphanumeric characters _or_ special characters. Note that using Ctrl + Shift + Left arrow will also select the full ")---". OOo 3.3 would also catch the full ")---", so marking as inherited. Mike, after your work on bug 126589, what are your thoughts? Deciding what constitute a boundary or not in a series of non-alphanum will always be debatable[1], so the only way out as I understand it is to: (a) keep adding characters to the string and checking if it matches a shortcut until it does or it reaches a space or alphanum character. Sounds like a pretty bad hack, but could work? Alternatively: (b) Stop accepting some boundary characters in new shortcuts (which ones? and would break existing shortcuts, so not workable.) (c) Won't fix. [1] What happens if I want my shortcut to be ")))" ? It's currently accepted in the shortcut field. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149306] Problem with decimal number selection using double click
https://bugs.documentfoundation.org/show_bug.cgi?id=149306 Tammy changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #5 from Tammy --- I was able to reproduce the issue on the following: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: c1fe534ae49e7e97b5965a5d1fbf910598215102 CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-MX (en_US); UI: en-US Calc: threaded I did further testing by separating 123, 45 and it picks up by double clicking on the 45 or 123 it highlights only that portion. However, verified that selecting 123.45 highlights either 45 or 123 when double-clicking. It appears to be related to bug 149254. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156085] LibreOffice hangs at start, frequent crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=156085 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO CC||stephane.guillou@libreoffic ||e.org Ever confirmed|0 |1 --- Comment #3 from Stéphane Guillou (stragu) --- Do you see a crash reporter dialog when restarting LO? If so, please share the crash report link. Please also share the detailed version info copied from Help > About LibreOffice. If you don't get a crash report, it would be helpful to get a backtrace for that crash. If you have the time, please follow these steps: https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107237] [META] Notebookbar Tabbed
https://bugs.documentfoundation.org/show_bug.cgi?id=107237 Bug 107237 depends on bug 126006, which changed state. Bug 126006 Summary: Calc with Tabbed UI used to crash after File>>Reload; many toolbar items aren't working including save https://bugs.documentfoundation.org/show_bug.cgi?id=126006 What|Removed |Added Status|RESOLVED|NEW Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 126006] Calc with Tabbed UI used to crash after File>>Reload; many toolbar items aren't working including save
https://bugs.documentfoundation.org/show_bug.cgi?id=126006 Justin L changed: What|Removed |Added Assignee|jl...@mail.com |libreoffice-b...@lists.free ||desktop.org Status|RESOLVED|NEW Whiteboard|target:24.2.0 | Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103512] [META] AutoFilter-related bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103512 Bug 103512 depends on bug 126006, which changed state. Bug 126006 Summary: Calc with Tabbed UI used to crash after File>>Reload; many toolbar items aren't working including save https://bugs.documentfoundation.org/show_bug.cgi?id=126006 What|Removed |Added Status|RESOLVED|NEW Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 75825] Other: "Send Document as E-Mail" not working -- (while sending as attachment works)
https://bugs.documentfoundation.org/show_bug.cgi?id=75825 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||6211 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154755] [META] Thunderbird interoperability and integration
https://bugs.documentfoundation.org/show_bug.cgi?id=154755 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||116211 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=116211 [Bug 116211] LO Send by email fails from claws-mail -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 116211] LO Send by email fails from claws-mail
https://bugs.documentfoundation.org/show_bug.cgi?id=116211 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||154755 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=75 ||825, ||https://launchpad.net/bugs/ ||1217191, ||https://launchpad.net/bugs/ ||1909941 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #38 from Stéphane Guillou (stragu) --- Clearly issues to solve, including in link to Thunderbird as in duplicate but 154479. Thanks Bernard for continuously looking into it, and please don't hesitate submitting a patch on gerrit if you think it can improve the situation. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154755 [Bug 154755] [META] Thunderbird interoperability and integration -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 111591] [META] File sending bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=111591 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on|154479 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154479 [Bug 154479] Writer don't attach the document when using the attach at email button -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154755] [META] Thunderbird interoperability and integration
https://bugs.documentfoundation.org/show_bug.cgi?id=154755 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on|154479 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154479 [Bug 154479] Writer don't attach the document when using the attach at email button -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154479] Writer don't attach the document when using the attach at email button
https://bugs.documentfoundation.org/show_bug.cgi?id=154479 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED URL||https://forum.openoffice.or ||g/en/forum/viewtopic.php?f= ||7=103792 Resolution|--- |DUPLICATE Blocks|111591, 154755 | --- Comment #15 from Stéphane Guillou (stragu) --- Thanks for the info. This makes it sound like an xdg-utils issue, related to a security fix: https://forums.linuxmint.com/viewtopic.php?t=336053 So check that you have all your Mint packages updated, and let us know which version of the xdg-utils you have installed. Similar issue in bug 75825, also on https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1217191 You can put "sensible-lomua" back into the settings field, given that it worked for finding the email client (i.e. opening the email composer). You can also try "/usr/bin/thunderbird" in that field just in case, but I'm not too hopeful. I'm marking as a duplicate of bug 116211, because the issue is a lot better covered there, and various people have reported it for Thunderbird too. *** This bug has been marked as a duplicate of bug 116211 *** Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=111591 [Bug 111591] [META] File sending bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=154755 [Bug 154755] [META] Thunderbird interoperability and integration -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 116211] LO Send by email fails from claws-mail
https://bugs.documentfoundation.org/show_bug.cgi?id=116211 Stéphane Guillou (stragu) changed: What|Removed |Added CC||firefox.unders...@aleeas.co ||m --- Comment #37 from Stéphane Guillou (stragu) --- *** Bug 154479 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156102] Ctrl+brackets (ctrl+[ and ctrl+]) does not work on Windows with different keyboard layouts
https://bugs.documentfoundation.org/show_bug.cgi?id=156102 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO CC||stephane.guillou@libreoffic ||e.org Ever confirmed|0 |1 --- Comment #2 from Stéphane Guillou (stragu) --- Hossein, does Ctrl + Shift + [ or ] work? Does this match your layout? https://i.stack.imgur.com/rTueJ.png -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156116] New: when renamed, object name does not update in accessibility check sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=156116 Bug ID: 156116 Summary: when renamed, object name does not update in accessibility check sidebar Product: LibreOffice Version: 24.2.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Keywords: accessibility Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: stephane.guil...@libreoffice.org Blocks: 154929 Created attachment 188148 --> https://bugs.documentfoundation.org/attachment.cgi?id=188148=edit sample ODT Steps to reproduce: 1. Open attachment in Writer 2. Rename Image3 in Navigator 3. Switch to Accessibility Check sidebar deck Results: name of object isn't updated. A save and reload is necessary to see the change. Expected: name updated directly. Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: c5bd661dc032ed8f664b0eac47f246d4d51b4d2c 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=154929 [Bug 154929] [META] Accessibility Check sidebar deck, Automatic Accessibility Checking -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154929] [META] Accessibility Check sidebar deck, Automatic Accessibility Checking
https://bugs.documentfoundation.org/show_bug.cgi?id=154929 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||156116 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156116 [Bug 156116] when renamed, object name does not update in accessibility check sidebar -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156095] Warnings in the "other" category of the Accessibility Check are duplicated
https://bugs.documentfoundation.org/show_bug.cgi?id=156095 --- Comment #5 from Stéphane Guillou (stragu) --- (In reply to Balázs Varga (allotropia) from comment #3) > I think this issue will be also fixed with this commit? > https://gerrit.libreoffice.org/c/core/+/153724 Yes, that fixed it. Thanks! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156101] Thesaurus supposedly enabled, but grayed out in UI
https://bugs.documentfoundation.org/show_bug.cgi?id=156101 Stéphane Guillou (stragu) changed: What|Removed |Added CC||caolan.mcnamara@collabora.c ||om, nem...@numbertext.org --- Comment #7 from Stéphane Guillou (stragu) --- Maybe this is just a matter of listing en-IL somewhere so the Hunspell MyThes also works for that language? Caolán, László, any idea? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155630] Deduplicate copy/paste code (reboot with a new tool)
https://bugs.documentfoundation.org/show_bug.cgi?id=155630 --- Comment #7 from Dave Gilbert --- I've played a bit with pmd, and it's reasonably nice, but hmm; some notes: a) Throwing the whole LO source at it makes it run out of Java stack space; passing a subset works; but then you do want to pass a subset where you're likely to find commonality between them (as well as internally to one dir) b) It seems to get quite confused on big chunks of data c) You've got to be really careful not to miss subtle differences after the bit it spots - e.g. it spots that two functions start the same, so you decide to merge them, but you really need to check that there's not some small, crazy difference. d) There's some art to trying to decide where a merged piece of code will live. See my set at: https://gerrit.libreoffice.org/c/core/+/153826 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 101216] [META] Calc comment bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=101216 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on|155642 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=155642 [Bug 155642] Problems with comment baloon in Calc -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 68695] EDITING: Comments cannot be resized while editing - missing squares around the comment/note
https://bugs.documentfoundation.org/show_bug.cgi?id=68695 Stéphane Guillou (stragu) changed: What|Removed |Added CC||lucioirfons...@gmail.com --- Comment #82 from Stéphane Guillou (stragu) --- *** Bug 155642 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155642] Problems with comment baloon in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=155642 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||stephane.guillou@libreoffic ||e.org Blocks|101216 | --- Comment #6 from Stéphane Guillou (stragu) --- Closing as duplicate of bug 68695, hope you all agree. *** This bug has been marked as a duplicate of bug 68695 *** Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=101216 [Bug 101216] [META] Calc comment bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150545] Incorrect handling of "Automatic" increment in gradient fill
https://bugs.documentfoundation.org/show_bug.cgi?id=150545 Regina Henschel 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 36766] [META] Impress Gradient and Transparency issues
https://bugs.documentfoundation.org/show_bug.cgi?id=36766 Bug 36766 depends on bug 150545, which changed state. Bug 150545 Summary: Incorrect handling of "Automatic" increment in gradient fill https://bugs.documentfoundation.org/show_bug.cgi?id=150545 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107787] Gradients steps don't save
https://bugs.documentfoundation.org/show_bug.cgi?id=107787 --- Comment #37 from Leandro Martín Drudi --- I did not understand very well what you are talking about but I will expose my position as a user and what I expect to happen when I use the tool: When I apply 2 or more steps, it is because the effect obtained is the one I want. In fact, this complaint arises because I cannot recover that expected configuration. Forcing the user to stay in Automatic when the desired effect is obtained with few steps is disrespectful to the user. As an user, I expect what was presented when configuring it to happen. Otherwise, as an user, I consider it a malfunction and it leads me not to use the software until it is resolved. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107787] Gradients steps don't save
https://bugs.documentfoundation.org/show_bug.cgi?id=107787 --- Comment #36 from Regina Henschel --- Created attachment 188147 --> https://bugs.documentfoundation.org/attachment.cgi?id=188147=edit Increment 3 in MCGR (In reply to Heiko Tietze from comment #35) > (In reply to Regina Henschel from comment #33) > > Or should the design of the dialog be changed (with is needed for multicolor > > gradients anyway) to make clear, that the Increment value does not belong to > > a gradient definition but is an attribute of the individual object? > > This. I suggest to check (=Automatic) and disable the steps spinbox if more > than two colors are used aka MCGR. So you suggest to always use "automatic" in case the gradient has more than two color stops? The current behavior is, that in case there are more than two color stops and the user has set an Increment value, the stepped rendering is applied individually to each part between two adjacent stops. Example attached: [1] offset 0.2 red, [2] offset 0.5 yellow, [3] offset 0.95 green and Increment=3. Current behavior: 0 to 0.2 red (automatic extending of the first color), 0.2 to 0.3 red (first step) 0.3 to 0.4 orange (second step) 0.4 to 0.5 yellow (third step) 0.5 to 0.65 yellow (first step) 0.65 to 0.8 yellow+green mix (second step) 0.8 to 0.95 green (third step) 0.95 to 1 green (automatic extending of the last color) For me it looks ugly and I would support to use always 'automatic' in case of more than two colors. The user can still create steps by setting two stops to same offset. Having always 'automatic' in this case brings no restriction to the OOXML filter, because OOXML has no setting for stepped rendering at all. Because MCGR is not yet in ODF, we could include such restriction into the proposal to the ODF TC. > > (In reply to Regina Henschel from comment #33) > > Heiko, do you really want, that the XML of our palette is > > changed to be able to carry the Increment value in addition? > > Ultimately being able to have 5 steps for red to blue followed by a smooth > transition from blue to green, as an example? Hopefully I never suggested > this (keep it simple). I do not mean a mix but this: Users currently do not understand, why a preset gradient cannot have a stepped rendering, although the shape from which the preset is created had an Increment=4, for example. The current solution of the Gradient-dialog has no indication that it is not possible. This problem exists independent from MCGR and is not solved by forcing 'automatic' in case of more than two colors. I see the following solutions. Which would do you prefer? (A) The current css.awt.Gradient struct from the API contains the Increment as StepCount component, whereas the gradient definition in the in ODF has no corresponding attribute. Currently the XML of the palette uses the ODF definition directly. Because the XML of the palette is our own format we could change it without impacts to ODF. Of course, this is not to be had for free; it requires a developer to donate his free time to it. (B) The dialog could show a warning, that the Increment-value is not included in the added gradient, in case an Increment-value is set and the user adds this gradient to the palette. (C) Separate the Increment setting visually from the others in the dialog and include a hint/warning in its label. (B) and (C) affects only the dialog and could be done, when the dialog is adapted to MCGR. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156086] Does Libreoffice support Endnote separator in docx file?
https://bugs.documentfoundation.org/show_bug.cgi?id=156086 --- Comment #3 from aarush0...@gmail.com --- I have attached file, in this file, line(endnote separator) is not visible in LibreOffice. Also the content is going to the next page. Can you explain it? at least line should be visible. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156086] Does Libreoffice support Endnote separator in docx file?
https://bugs.documentfoundation.org/show_bug.cgi?id=156086 --- Comment #2 from aarush0...@gmail.com --- Created attachment 188146 --> https://bugs.documentfoundation.org/attachment.cgi?id=188146=edit File has missing line issue. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117022] [META] Style-focused formatting toolbar
https://bugs.documentfoundation.org/show_bug.cgi?id=117022 Bug 117022 depends on bug 156110, which changed state. Bug 156110 Summary: When typing in expanded font family combo box, don't collapse the list https://bugs.documentfoundation.org/show_bug.cgi?id=156110 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113438] [META] Font name combobox bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=113438 Bug 113438 depends on bug 156110, which changed state. Bug 156110 Summary: When typing in expanded font family combo box, don't collapse the list https://bugs.documentfoundation.org/show_bug.cgi?id=156110 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156110] When typing in expanded font family combo box, don't collapse the list
https://bugs.documentfoundation.org/show_bug.cgi?id=156110 Caolán McNamara changed: What|Removed |Added Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED --- Comment #1 from Caolán McNamara --- If you use something like gtk3-demo to explore how gtk widgets work and launch the "Combo Boxes" example, then the GtkComboBoxText example there works (unsurprisingly) like it does in LibreOffice in that a click in the text area dismisses an active popup. Popups are often quite gruesome on many platforms and it can be quite technically challenging to do anything else given the complexity of grabs and how events are managed when there is a popup active. It's fairly strongly baked in that clicks outside a popup dismiss active popups. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156046] Autocorrect replaces " - " with " – " instead of " — " (en-dash instead of em-dash)
https://bugs.documentfoundation.org/show_bug.cgi?id=156046 --- Comment #6 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #5) > En-dash can be expressed by two hyphen, EM by three. I think we do a good > job with converting it. This bug is not about that. Please re-read the title and comment #2. Remember, we are talking about the case of a user who is not indicating "explicitly" what they want using multiple-dashes or other sequences of characters intended for replacement. > And wonder if other languages than English have > different punctuation guides. That's a completely different issue; we currently have a uniform-across-languages behavior and nobody has challenged it, so this objection sounds TBH like a deflection. The question is very simple: What's the better choice for replacing the hyphen in a " - " sequence: Should it be an En-dash or an Em-dash. Since there is no bug suggesting that we should redo this whole logic, this question stands. So, unless we have a good reason to prefer an En-dash - which nobody has presented AFAICT - we should choose an Em-dash. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107805] [META] Writer master document issues
https://bugs.documentfoundation.org/show_bug.cgi?id=107805 Bug 107805 depends on bug 155740, which changed state. Bug 155740 Summary: Support distinction rather than override of conflicting subdocument styles https://bugs.documentfoundation.org/show_bug.cgi?id=155740 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155740] Support distinction rather than override of conflicting subdocument styles
https://bugs.documentfoundation.org/show_bug.cgi?id=155740 Mike Kaganski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG --- Comment #6 from Mike Kaganski --- Definitely not a bug, and a WONTFIX. The most important idea behind the master documents is exactly being able to centrally configure styles. The premise that styles in sub-documents are "discarded" is wrong, and they are "overridden" *temporarily*, i.e. when you open a sub-document by itself, they will keep the original properties. Among other things, this allows a kind of "css", when different master documents override same styles in different ways. If one wants some distinction in their *part* of a multi=part document, they need to create new styles (or use ad-hoc formatting, if it's a single-use case). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156046] Autocorrect replaces " - " with " – " instead of " — " (en-dash instead of em-dash)
https://bugs.documentfoundation.org/show_bug.cgi?id=156046 --- Comment #5 from Heiko Tietze --- En-dash can be expressed by two hyphen, EM by three. I think we do a good job with converting it. And wonder if other languages than English have different punctuation guides. My take: NAB. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156115] New: .pdf convertion to Libre Office
https://bugs.documentfoundation.org/show_bug.cgi?id=156115 Bug ID: 156115 Summary: .pdf convertion to Libre Office Product: LibreOffice Version: 7.5.0.0 alpha0+ Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: alainfrench...@gmail.com Good morning to all developpers When I receive a document under .pdf format with "1er janvier" in the text (checked OK with Acrobat)and open it with Libre Office, this mention come as "e1r janvier" - e & r being in a little police size. There is probably a PB with editing .pdf in .Libre Office It is not a big PB but it is annoying and cannot have faith to work on these documents. Congratulations for all your good work Alain PS : Original confidential documents available on request -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156089] When setting the Heading/Outline Numbering for a level to "None", still getting separators
https://bugs.documentfoundation.org/show_bug.cgi?id=156089 --- Comment #3 from Heiko Tietze --- ODF allows this and I see no harm in this flexibility. "None" just doesn't mean no numbering but no (automatic) numbers/chars. Agree with Justin on NAB. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107237] [META] Notebookbar Tabbed
https://bugs.documentfoundation.org/show_bug.cgi?id=107237 Bug 107237 depends on bug 126006, which changed state. Bug 126006 Summary: Calc with Tabbed UI used to crash after File>>Reload; many toolbar items aren't working including save https://bugs.documentfoundation.org/show_bug.cgi?id=126006 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
