[Libreoffice-bugs] [Bug 155905] New: Has been crashing on and off for 2 weeks. Randomized, no trigger as far as I can tell. It freezes up, then closes all libre office windows compeltely
https://bugs.documentfoundation.org/show_bug.cgi?id=155905 Bug ID: 155905 Summary: Has been crashing on and off for 2 weeks. Randomized, no trigger as far as I can tell. It freezes up, then closes all libre office windows compeltely Product: LibreOffice Version: 7.5.4.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: imj3jenni...@gmail.com Description: The program has been crashing on and off for two weeks. Has been worse this week. There is no trigger as far as I can tell, it is not consistent, it is random. Nothing i do seems to trigger it. The window works fine, then, freezes up. Then all open Libre Office Documents close down suddenly. There is no spinning circle, no option of, this program has frozen up do you want to force stop, or wait. It froze up before last software update, and after the last software update. I set the settings to auto save work every minute, so if it crashes before I can click save i don't lose much work, but it has been very frustrating. I'm sorry I don't have more details for you than that. I am writing a book, so I have libreOffice Open for long periods of time, I frequently manually save, I'm not sure if it's the fact that the program is open for a long period of time? Steps to Reproduce: 1.Open Libre Office 2.Use for a long time, Save work, continue happily along way, 3.Save work final time, close down, go to bed. Actual Results: Use libre office, usually for a longer period of time. The program freezes up, the mouse moves, but it won't recognize buttons, or any clicks, whether I click anything or not, it shuts down regardless. So I know I'm not overloading the program... Expected Results: Not frozen up and then promptly shut down after about a minute of frozen time thus being stupid. Expected results? Idk, Worked correctly? Reproducible: Sometimes User Profile Reset: No Additional Info: I'm sorry. I don't have good information for a software bug, I am just having issues and have had issues for a few weeks now, and it seems to be getting worse. I updated the software, that didn't help. And, don't know what else to do but file a bug report. It's not consistent, I can't get it to reproduce the problem at will, it's not something that I can figure out if there's a trigger or not. I'm hoping there's something that can be done to fix it. I also, have not reset my user profile, I have no idea how to do that... I googled it to see if it was something I could do, and I can't figure it out. So, I'm just gonna send it. I'm sorry. have a good day. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155812] Open file with many page numbers spend too much time
https://bugs.documentfoundation.org/show_bug.cgi?id=155812 --- Comment #5 from Xiaoc <3118049...@qq.com> --- Anyone who can help? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155656] Quattro Pro files show textual & column rendering problems, slanted, and overrunning text
https://bugs.documentfoundation.org/show_bug.cgi?id=155656 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 155634] Announcement by Orca screen reader 'Contains formula' disappeared in calc 7.5.3 on a cell including a formula.
https://bugs.documentfoundation.org/show_bug.cgi?id=155634 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 151616] Text tearing in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=151616 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 151616] Text tearing in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=151616 --- Comment #12 from QA Administrators --- Dear Carole Rousseaux, 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 145598] The display of sublevels of chapters in LibreOffice Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=145598 --- Comment #5 from QA Administrators --- Dear delbouys, 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 145699] UI: Expanding effects deck puts a the vertical scrollbar above spinboxes and such in draw
https://bugs.documentfoundation.org/show_bug.cgi?id=145699 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145699] UI: Expanding effects deck puts a the vertical scrollbar above spinboxes and such in draw
https://bugs.documentfoundation.org/show_bug.cgi?id=145699 --- Comment #6 from QA Administrators --- Dear Telesto, 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 145390] Calc - Planilha não está ordenando por data(Date) corretamente
https://bugs.documentfoundation.org/show_bug.cgi?id=145390 --- Comment #5 from QA Administrators --- Dear Jacó da Silva, 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 145373] LibreOffice locks up when loading a spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=145373 --- Comment #3 from QA Administrators --- Dear Earl Dingman, 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 145962] [META] Bugs related to kerning/font spacing (cramped/to width/wiggling)
https://bugs.documentfoundation.org/show_bug.cgi?id=145962 Bug 145962 depends on bug 141749, which changed state. Bug 141749 Summary: Text Tearing, Font Shrinkage, and Line Shifting bug related to use of Sidebar https://bugs.documentfoundation.org/show_bug.cgi?id=141749 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141749] Text Tearing, Font Shrinkage, and Line Shifting bug related to use of Sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=141749 --- Comment #9 from QA Administrators --- Dear Eek! A Bug. Kill it!, 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 145962] [META] Bugs related to kerning/font spacing (cramped/to width/wiggling)
https://bugs.documentfoundation.org/show_bug.cgi?id=145962 Bug 145962 depends on bug 139296, which changed state. Bug 139296 Summary: scrolling document canvas down & up can cause a line of text to "tear" with loss of registration, it clears when the line moves out of view far enough or view passes to a new page https://bugs.documentfoundation.org/show_bug.cgi?id=139296 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139296] scrolling document canvas down & up can cause a line of text to "tear" with loss of registration, it clears when the line moves out of view far enough or view passes to
https://bugs.documentfoundation.org/show_bug.cgi?id=139296 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 139296] scrolling document canvas down & up can cause a line of text to "tear" with loss of registration, it clears when the line moves out of view far enough or view passes to
https://bugs.documentfoundation.org/show_bug.cgi?id=139296 --- Comment #62 from QA Administrators --- Dear Bob, 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 147743] Crash on start
https://bugs.documentfoundation.org/show_bug.cgi?id=147743 --- Comment #4 from QA Administrators --- Dear GB, 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 152348] LibreOffice Writer crash after installing Help on 4GB memory RAM
https://bugs.documentfoundation.org/show_bug.cgi?id=152348 --- Comment #2 from QA Administrators --- Dear sberube, 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 151747] Libreoffice crashes when selecting menu option
https://bugs.documentfoundation.org/show_bug.cgi?id=151747 --- Comment #9 from QA Administrators --- Dear Alex, 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 145325] Weird behaviour when using custom cell height
https://bugs.documentfoundation.org/show_bug.cgi?id=145325 --- Comment #10 from QA Administrators --- Dear Perico Palotes, 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 92064] LO unusable with Tibetan super long paragraphs
https://bugs.documentfoundation.org/show_bug.cgi?id=92064 --- Comment #14 from QA Administrators --- Dear Elie Roux, 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 89773] Text Boxes based on cells with formulas do not update after pasting new data in cells the formula uses (hard recalc needed)
https://bugs.documentfoundation.org/show_bug.cgi?id=89773 --- Comment #12 from QA Administrators --- Dear ematchmail, 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 147554] Changing fonts within an app makes cursor disappear and app won't accept input
https://bugs.documentfoundation.org/show_bug.cgi?id=147554 --- Comment #2 from QA Administrators --- Dear dentar, 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 89621] DOCX margin or paragraph width with tab and space (and with Verdana font?) isn't the same in Word and in Writer (comment 14)
https://bugs.documentfoundation.org/show_bug.cgi?id=89621 --- Comment #16 from QA Administrators --- Dear Tom Williams, 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 72079] Adding Fonts for Lao, Thai, and Khmer
https://bugs.documentfoundation.org/show_bug.cgi?id=72079 --- Comment #11 from QA Administrators --- Dear Robert M Campbell, 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 142604] FILESAVE DOCX Writer line callouts customization points are incorrect
https://bugs.documentfoundation.org/show_bug.cgi?id=142604 --- Comment #4 from QA Administrators --- Dear NISZ LibreOffice Team, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 34538] Writer wraps words wrong on banner size paper
https://bugs.documentfoundation.org/show_bug.cgi?id=34538 --- Comment #16 from QA Administrators --- Dear rknasc, 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 142898] Roundtrip DOCX: file size increase from 430 KB to 5500 because of font embedding
https://bugs.documentfoundation.org/show_bug.cgi?id=142898 --- Comment #5 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 142238] VIEWING Presentation range influences slideshow playback incorrectly
https://bugs.documentfoundation.org/show_bug.cgi?id=142238 --- Comment #2 from QA Administrators --- Dear NISZ LibreOffice Team, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135444] FILEOPEN: DOCX: altName from fontTable.xml not applied so font wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=135444 --- Comment #6 from QA Administrators --- Dear Rhys Young, 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 107476] FILEOPEN: DOC: DOCX: TAB_OVER_MARGIN paragraphs should never wrap
https://bugs.documentfoundation.org/show_bug.cgi?id=107476 --- Comment #13 from QA Administrators --- Dear Xisco Faulí, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155904] docx file is not available in file open?
https://bugs.documentfoundation.org/show_bug.cgi?id=155904 --- Comment #2 from jindam, vani --- Created attachment 187970 --> https://bugs.documentfoundation.org/attachment.cgi?id=187970=edit screenshot libreoffice viewer android docx file is listed file open option -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155904] docx file is not available in file open?
https://bugs.documentfoundation.org/show_bug.cgi?id=155904 jindam, vani changed: What|Removed |Added CC||jindam.v...@disroot.org --- Comment #1 from jindam, vani --- Created attachment 187969 --> https://bugs.documentfoundation.org/attachment.cgi?id=187969=edit screenshot mc [ midnightcommander ] linux docx file is listed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155904] New: docx file is not available in file open?
https://bugs.documentfoundation.org/show_bug.cgi?id=155904 Bug ID: 155904 Summary: docx file is not available in file open? Product: LibreOffice Version: 7.5.4.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jindam.v...@disroot.org Created attachment 187968 --> https://bugs.documentfoundation.org/attachment.cgi?id=187968=edit screenshot libreoffice linux docx file is not listed file open option * .docx filename: =_UTF-8_Q_=D8=A2=D8=AF=D8=A7=D8=A8_=D8=B1=D8=A7=D8=B2_=D9=88=D9=86=D9=8A_= =_UTF-8_Q_=D8=A7=D8=B2_=D8=A8=D9=87_=D8=AF=D8=B1.docx * File is not listed libreoffice [ linux ] _file open * File is listed ** libreoffice viewer [ android ]_ select file to open ** mc [ linux ] * Completly lost about how to write this issue, please find attached screenshots * repro libreoffice: Version: 7.5.4.2 (ARM_EABI) / LibreOffice Community Build ID: 50(Build:2) CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: x11 Locale: en-US (C); UI: en-US Calc: threaded OS: NAME="openSUSE Tumbleweed", VERSION_ID="20230604" * no repro libreoffice: f-droid: Version: 7.6.0.0.alpha1+, Build ID: 5c1c768e128d OS: Android -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-22.05' - filter/source
filter/source/svg/svgexport.cxx |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
New commits:
commit d208e9062e5d1bd6a382995e12437aa5ad39a14d
Author: Caolán McNamara
AuthorDate: Mon Jun 12 15:25:32 2023 +0100
Commit: Aron Budea
CommitDate: Sun Jun 18 03:04:09 2023 +0200
Resolves: tdf#155791 export of default impress slide master to svg failed
Change-Id: Ie4ec64fef6d8c2c2844a01d06109ad9022714c11
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/152913
Tested-by: Jenkins CollaboraOffice
Reviewed-by: Miklos Vajna
(cherry picked from commit 366a9cdd1a0b03c1abe7ffc7515a34a8abd27754)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/153149
Reviewed-by: Caolán McNamara
Reviewed-by: Aron Budea
diff --git a/filter/source/svg/svgexport.cxx b/filter/source/svg/svgexport.cxx
index ae74a6e2fbc6..d6b154a67212 100644
--- a/filter/source/svg/svgexport.cxx
+++ b/filter/source/svg/svgexport.cxx
@@ -668,7 +668,7 @@ bool SVGFilter::implExportImpressOrDraw( const Reference<
XOutputStream >& rxOSt
if( rxOStm.is() )
{
-if( !mSelectedPages.empty() && !mMasterPageTargets.empty() )
+if (!mSelectedPages.empty())
{
Reference< XDocumentHandler > xDocHandler =
implCreateExportDocumentHandler( rxOStm );
@@ -985,7 +985,7 @@ bool SVGFilter::implExportDocument()
mpSVGWriter->SetPreviewMode();
// #i124608# export a given object selection, so no MasterPage
export at all
-if (!mbExportShapeSelection)
+if (!mbExportShapeSelection && !mMasterPageTargets.empty())
implExportMasterPages( mMasterPageTargets, 0,
mMasterPageTargets.size() - 1 );
implExportDrawPages( mSelectedPages, 0, nLastPage );
[Libreoffice-bugs] [Bug 155634] Announcement by Orca screen reader 'Contains formula' disappeared in calc 7.5.3 on a cell including a formula.
https://bugs.documentfoundation.org/show_bug.cgi?id=155634 ady changed: What|Removed |Added Whiteboard||QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155881] Saving causes consolidate dialog to fill up with garbage ranges
https://bugs.documentfoundation.org/show_bug.cgi?id=155881 ady changed: What|Removed |Added Blocks||115775 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=115775 [Bug 115775] [META] Database Range and Consolidate bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 115775] [META] Database Range and Consolidate bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=115775 ady changed: What|Removed |Added Depends on||155881 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=155881 [Bug 155881] Saving causes consolidate dialog to fill up with garbage ranges -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155881] Saving causes consolidate dialog to fill up with garbage ranges
https://bugs.documentfoundation.org/show_bug.cgi?id=155881 --- Comment #6 from ady --- Using a recent Dev version and a file from scratch (taking data from attachment 187945 from comment 2), I am still able to replicate the behavior reported in this bug 155881. The difference in this case is that, when re-opening the already-saved file, the additional lines are not 4 but 3 (i.e. offset of -1). The next times (after each save and reload) the values are similar: 11 lines instead of 12, 27 lines instead of 28... In the Consolidate dialog, there are other features that are not working correctly: * The field info for Source data cannot be deleted; meaning that after deletion, closing the dialog and reopening it, the source data lines remain as before deletion. * Trying to select an area for Source Data, I cannot use typical keyboard shortcuts to select an area (e.g. [CTRL]+[HOME], [SHIFT]+[CTRL]+[END], [SHIFT]+[CTRL]+[arrow keys]); the focus of the cursor remains in the field of the dialog, so the area can be selected by using the mouse and scrolling). * Not all the (Row) Head Labels are actually used/seen in the resulting consolidation area (i.e. "Copy results to:" field). (In reply to m.a.riosv from comment #5) > bug 45862 I tried using attachment 56839 from bug 45862, but it doesn't make sense when I open it: the dialog is set up in order to consolidate data by a SUM of _text_ values. Starting from such situation, I decided not to use it for testing the Data Consolidation feature. -- You are receiving this mail because: You are the assignee for the bug.
Building failed with --enable-lto on Debian, but succeeded on Ubuntu/Rocky Linux
Hi, I was trying to build latest LibreOffice core on Debian Bullseye and failed, while the other one could build successfully on Rocky Linux 8. So I tried to dig a bit deeper to find out why. Then I found that if I enable link-time optimization while running autogen.sh, it would fail : https://pastebin.com/Pt0zfEF2 Start from line 27641, while linking something with libharfbuzz.a, some symbols in libgraphite2.a were missing. libgraphite2.a was there, but all the makefiles didn't include them. If I use --disable-lto or simply comment out or remove the --enable-lto when running autogen.sh, it would succeed, but I'm still not sure if it linked libgraphite2 or not. https://pastebin.com/1FdeMsXr Then I tried to build it on Ubuntu Jammy. It succeeded even with --enable-lto. Well, problem solved since I could build it, but I'm still curious why it would fail only on Debian. I run all the compiling works in "pure" environment created by docker. The Dockerfiles for Debian and Ubuntu are simple like this: |FROM debian:bullseye || ||### Install system || ||COPY sources.list /etc/apt/sources.list || ||RUN mkdir /opt/git || ||RUN apt update || ||RUN apt install -y --no-install-recommends vim vim-runtime \ || || bash \ || || docker.io \ || || locales locales-all \ || || libkrb5-dev \ || || curl \ || || ssh \ || || git || ||RUN locale-gen zh_TW.UTF-8 || ||RUN locale-gen en_US.UTF-8 || ||RUN apt build-dep -y libreoffice| Any clue or possible reason why I would only fail on Debian with lto enabled? Or why it would not link with libgraphite.a which was indeed presented under workdir/LinkTarget/StaticLibrary/libgraphite.a? Thanks, Franklin -- Franklin Weng Member, Certification Committee The Document Foundation, Kurfürstendamm 188, 10707 Berlin, DE Gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts Legal details:https://www.documentfoundation.org/imprint OpenPGP_signature Description: OpenPGP digital signature
[Libreoffice-commits] core.git: sc/source
sc/source/ui/view/tabvwsha.cxx |6 ++
1 file changed, 6 insertions(+)
New commits:
commit 8a0a4a4e1fa63edaa5ef923e0db56df7d08eb73c
Author: Maxim Monastirsky
AuthorDate: Fri Jun 16 11:53:37 2023 +0300
Commit: Maxim Monastirsky
CommitDate: Sun Jun 18 02:02:41 2023 +0200
sc drawstyles: Restore text selection after applying a style
Change-Id: I0a9bb39d8a7a9e770b3593eaa0a97867cbe86913
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/153171
Tested-by: Jenkins
Reviewed-by: Maxim Monastirsky
diff --git a/sc/source/ui/view/tabvwsha.cxx b/sc/source/ui/view/tabvwsha.cxx
index 231630a4e5d3..c07a070e08ef 100644
--- a/sc/source/ui/view/tabvwsha.cxx
+++ b/sc/source/ui/view/tabvwsha.cxx
@@ -936,6 +936,8 @@ void ScTabViewShell::ExecStyle( SfxRequest& rReq )
ScMarkData& rMark = GetViewData().GetMarkData();
ScModule* pScMod = SC_MOD();
SdrObject* pEditObject = GetDrawView()->GetTextEditObject();
+OutlinerView* pOLV= GetDrawView()->GetTextEditOutlinerView();
+ESelection aSelection = pOLV ? pOLV->GetSelection() :
ESelection();
OUStringaRefName;
boolbUndo = rDoc.IsUndoEnabled();
@@ -1686,7 +1688,11 @@ void ScTabViewShell::ExecStyle( SfxRequest& rReq )
// reactivate text editing instead:
auto pFuText = dynamic_cast(GetDrawFuncPtr());
if (pFuText && pEditObject != GetDrawView()->GetTextEditObject())
+{
pFuText->SetInEditMode(pEditObject);
+if (GetDrawView()->GetTextEditOutlinerView())
+GetDrawView()->GetTextEditOutlinerView()->SetSelection(aSelection);
+}
}
void ScTabViewShell::GetStyleState( SfxItemSet& rSet )
[Libreoffice-commits] core.git: Branch 'libreoffice-7-6' - helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit d24e2e06b5f2383f8e2e24fe8e6a5db5d04772d9 Author: Olivier Hallot AuthorDate: Sat Jun 17 20:20:30 2023 -0300 Commit: Gerrit Code Review CommitDate: Sun Jun 18 01:20:30 2023 +0200 Update git submodules * Update helpcontent2 from branch 'libreoffice-7-6' to 927781bcb0e808e6d5e6f4205f3c0b3f617833a9 - Do not overcapitalize nouns that are not commands Change-Id: Ic5d2d6775d170b26fa9e9964da5c461e1c53098e Reviewed-on: https://gerrit.libreoffice.org/c/help/+/152858 Tested-by: Jenkins Reviewed-by: Adolfo Jayme Barrientos (cherry picked from commit 0137de5673170eac325fc503cf10550d65ebe0c4) Reviewed-on: https://gerrit.libreoffice.org/c/help/+/153220 diff --git a/helpcontent2 b/helpcontent2 index 08967f8b0b97..927781bcb0e8 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit 08967f8b0b97fe797b89f373fa62c71f056aa9cf +Subproject commit 927781bcb0e808e6d5e6f4205f3c0b3f617833a9
[Libreoffice-commits] help.git: Branch 'libreoffice-7-6' - source/text
source/text/shared/00/0004.xhp | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) New commits: commit 927781bcb0e808e6d5e6f4205f3c0b3f617833a9 Author: Olivier Hallot AuthorDate: Sun Jun 11 11:36:47 2023 -0300 Commit: Adolfo Jayme Barrientos CommitDate: Sun Jun 18 01:20:30 2023 +0200 Do not overcapitalize nouns that are not commands Change-Id: Ic5d2d6775d170b26fa9e9964da5c461e1c53098e Reviewed-on: https://gerrit.libreoffice.org/c/help/+/152858 Tested-by: Jenkins Reviewed-by: Adolfo Jayme Barrientos (cherry picked from commit 0137de5673170eac325fc503cf10550d65ebe0c4) Reviewed-on: https://gerrit.libreoffice.org/c/help/+/153220 diff --git a/source/text/shared/00/0004.xhp b/source/text/shared/00/0004.xhp index 382856c784..515149a081 100644 --- a/source/text/shared/00/0004.xhp +++ b/source/text/shared/00/0004.xhp @@ -29,14 +29,14 @@ To access this command... -From the Menu bar: -From the Context menu: -From the Sheet Navigation bar: -From the Tabbed interface: -From Toolbars: +From the menu bar: +From the context menu: +From the sheet navigation bar: +From the tabbed interface: +From toolbars: From the keyboard: -From the Start Center: -From the Status bar: +From the start center: +From the status bar: Related Topics
[Libreoffice-commits] core.git: Branch 'libreoffice-7-6' - helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit cd70d18959f8d8b530a5ebca9d4bee8504961637 Author: Olivier Hallot AuthorDate: Sat Jun 17 20:19:03 2023 -0300 Commit: Gerrit Code Review CommitDate: Sun Jun 18 01:19:03 2023 +0200 Update git submodules * Update helpcontent2 from branch 'libreoffice-7-6' to 08967f8b0b97fe797b89f373fa62c71f056aa9cf - Improve wording in accessing commands Change-Id: I5e3220f33a00fd30a42de465b495802abc6e0462 Reviewed-on: https://gerrit.libreoffice.org/c/help/+/152796 Tested-by: Jenkins Reviewed-by: Olivier Hallot (cherry picked from commit 9ff981baf27f13da4245b41e3bed652925657f4d) Reviewed-on: https://gerrit.libreoffice.org/c/help/+/153212 Reviewed-by: Adolfo Jayme Barrientos diff --git a/helpcontent2 b/helpcontent2 index dc45fbe8e459..08967f8b0b97 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit dc45fbe8e459de068be8370757affb486b4aafad +Subproject commit 08967f8b0b97fe797b89f373fa62c71f056aa9cf
[Libreoffice-commits] help.git: Branch 'libreoffice-7-6' - source/text
source/text/shared/00/0004.xhp |6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) New commits: commit 08967f8b0b97fe797b89f373fa62c71f056aa9cf Author: Olivier Hallot AuthorDate: Fri Jun 9 09:37:07 2023 -0300 Commit: Adolfo Jayme Barrientos CommitDate: Sun Jun 18 01:19:03 2023 +0200 Improve wording in accessing commands Change-Id: I5e3220f33a00fd30a42de465b495802abc6e0462 Reviewed-on: https://gerrit.libreoffice.org/c/help/+/152796 Tested-by: Jenkins Reviewed-by: Olivier Hallot (cherry picked from commit 9ff981baf27f13da4245b41e3bed652925657f4d) Reviewed-on: https://gerrit.libreoffice.org/c/help/+/153212 Reviewed-by: Adolfo Jayme Barrientos diff --git a/source/text/shared/00/0004.xhp b/source/text/shared/00/0004.xhp index c51f3a63f3..382856c784 100644 --- a/source/text/shared/00/0004.xhp +++ b/source/text/shared/00/0004.xhp @@ -33,9 +33,9 @@ From the Context menu: From the Sheet Navigation bar: From the Tabbed interface: -From toolbars: -From the keyboard, press -From the Start Center, click +From Toolbars: +From the keyboard: +From the Start Center: From the Status bar:
[Libreoffice-bugs] [Bug 154933] Rename "Text body" to "Body text"
https://bugs.documentfoundation.org/show_bug.cgi?id=154933 --- Comment #13 from Commit Notification --- Seth Chaiklin committed a patch related to this issue. It has been pushed to "libreoffice-7-6": https://git.libreoffice.org/help/commit/dc45fbe8e459de068be8370757affb486b4aafad Related tdf#154933 update "Text Body" -> "Body Text" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'libreoffice-7-6' - helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit f417f48aaabe69e130b97fbc99800f6f457eff55 Author: Seth Chaiklin AuthorDate: Sun Jun 18 01:18:33 2023 +0200 Commit: Gerrit Code Review CommitDate: Sun Jun 18 01:18:33 2023 +0200 Update git submodules * Update helpcontent2 from branch 'libreoffice-7-6' to dc45fbe8e459de068be8370757affb486b4aafad - Related tdf#154933 update "Text Body" -> "Body Text" Change-Id: Ib0844b47d6320fe9b543141f811002ccc3ca4e94 Reviewed-on: https://gerrit.libreoffice.org/c/help/+/152659 Tested-by: Jenkins Reviewed-by: Seth Chaiklin (cherry picked from commit 430c011fc24671011cbdd5f6310e7681ecdaf17d) Reviewed-on: https://gerrit.libreoffice.org/c/help/+/153211 Reviewed-by: Adolfo Jayme Barrientos diff --git a/helpcontent2 b/helpcontent2 index dd07ccc40937..dc45fbe8e459 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit dd07ccc409372d1ed2b6fb473928cf8319984d81 +Subproject commit dc45fbe8e459de068be8370757affb486b4aafad
[Libreoffice-commits] help.git: Branch 'libreoffice-7-6' - source/text
source/text/swriter/00/0405.xhp |2 +- source/text/swriter/01/05130100.xhp |2 +- source/text/swriter/01/0514.xhp |6 +++--- source/text/swriter/01/05150200.xhp |4 ++-- source/text/swriter/04/0102.xhp |2 +- source/text/swriter/guide/auto_numbering.xhp |7 ++- 6 files changed, 10 insertions(+), 13 deletions(-) New commits: commit dc45fbe8e459de068be8370757affb486b4aafad Author: Seth Chaiklin AuthorDate: Wed Jun 7 11:24:03 2023 +0200 Commit: Adolfo Jayme Barrientos CommitDate: Sun Jun 18 01:18:33 2023 +0200 Related tdf#154933 update "Text Body" -> "Body Text" Change-Id: Ib0844b47d6320fe9b543141f811002ccc3ca4e94 Reviewed-on: https://gerrit.libreoffice.org/c/help/+/152659 Tested-by: Jenkins Reviewed-by: Seth Chaiklin (cherry picked from commit 430c011fc24671011cbdd5f6310e7681ecdaf17d) Reviewed-on: https://gerrit.libreoffice.org/c/help/+/153211 Reviewed-by: Adolfo Jayme Barrientos diff --git a/source/text/swriter/00/0405.xhp b/source/text/swriter/00/0405.xhp index a4bd11e6a6..12cad5c291 100644 --- a/source/text/swriter/00/0405.xhp +++ b/source/text/swriter/00/0405.xhp @@ -36,7 +36,7 @@ Choose Edit - Find Replace - Format - Text Flow tab. - Right-click a paragraph with style Text body. Choose Paragraph - Edit Style - Condition tab. + Right-click a paragraph with style Body Text. Choose Paragraph - Edit Style - Condition tab. Choose View - Styles (Command+TF11). Right-click any paragraph style. Choose New - Condition tab. diff --git a/source/text/swriter/01/05130100.xhp b/source/text/swriter/01/05130100.xhp index 76fe2d3b4f..6eb43de752 100644 --- a/source/text/swriter/01/05130100.xhp +++ b/source/text/swriter/01/05130100.xhp @@ -60,7 +60,7 @@ The header text now has the attributes you specified in the Header Paragraph Style, while the other parts of the document have the attributes defined in the business letter conditional Paragraph Style. -The "Text Body" Style was created as a conditional style. Therefore, any styles you derive from it can be used as conditional styles. +The Body Text style was created as a conditional style. Therefore, any styles you derive from it can be used as conditional styles. The Paragraph Style applied to the context is used when exporting to other formats (RTF, HTML, and so on). Conditional style diff --git a/source/text/swriter/01/0514.xhp b/source/text/swriter/01/0514.xhp index f580cb8e83..d02bd63763 100644 --- a/source/text/swriter/01/0514.xhp +++ b/source/text/swriter/01/0514.xhp @@ -201,15 +201,15 @@ You can assign shortcut keys to Styles from the Tools - Customize - Keyboard tab. Some shortcuts are predefined. Command+0 Ctrl+0 - (zero) applies the Text Body paragraph style. Heading 1 through Heading 5 paragraph styles can be applied by using the + (zero) applies the Body Text paragraph style. Heading 1 through Heading 5 paragraph styles can be applied by using the Command Ctrl key and the heading number. For example Command+2Ctrl+2 applies the Heading 2 paragraph style. -The Formatting (Styles) toolbar contains icons for applying and modifying styles. +The Formatting (Styles) toolbar contains icons for applying and modifying styles. -More information about styles. +More information about styles. diff --git a/source/text/swriter/01/05150200.xhp b/source/text/swriter/01/05150200.xhp index db13c209c7..83df12a166 100644 --- a/source/text/swriter/01/05150200.xhp +++ b/source/text/swriter/01/05150200.xhp @@ -37,11 +37,11 @@ - + AutoCorrect for Bullets / Numbering To create a bulleted list, type a hyphen (-), star (*), or plus sign (+), followed by a space or tab at the beginning of a paragraph. To create a numbered list, type a number followed by a period (.), followed by a space or tab at the beginning of a paragraph. - Automatic numbering is only applied to paragraphs formatted with the Default Paragraph Style, Text Body or Text Body Indent paragraph styles. + Automatic numbering is only applied to paragraphs formatted with the “Default Paragraph Style”, “Body Text”, or “Body Text, Indented” paragraph styles. diff --git a/source/text/swriter/04/0102.xhp b/source/text/swriter/04/0102.xhp index e43a33682b..b016e22ac0 100644 --- a/source/text/swriter/04/0102.xhp +++ b/source/text/swriter/04/0102.xhp @@ -388,7 +388,7 @@ Ctrl+0 (zero) - Apply Text Body paragraph style + Apply Body Text paragraph style diff --git a/source/text/swriter/guide/auto_numbering.xhp b/source/text/swriter/guide/auto_numbering.xhp index 06aac3e49e..0f8ec5e374 100644 ---
[Libreoffice-commits] core.git: Branch 'libreoffice-7-6' - helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 6cb3f6dc81ad696da9c86f6716c1505f24596927 Author: Andrea Gelmini AuthorDate: Sun Jun 18 01:17:52 2023 +0200 Commit: Gerrit Code Review CommitDate: Sun Jun 18 01:17:52 2023 +0200 Update git submodules * Update helpcontent2 from branch 'libreoffice-7-6' to dd07ccc409372d1ed2b6fb473928cf8319984d81 - Fix typo Change-Id: Id2a262225d6f9029dc706c309ddcf308fa55ee62 Reviewed-on: https://gerrit.libreoffice.org/c/help/+/153000 Tested-by: Jenkins Reviewed-by: Julien Nabet (cherry picked from commit f252a686b4231cfcd3e00756b1a59509aa3ae407) Reviewed-on: https://gerrit.libreoffice.org/c/help/+/153216 Reviewed-by: Adolfo Jayme Barrientos diff --git a/helpcontent2 b/helpcontent2 index ef0e2a4bf333..dd07ccc40937 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit ef0e2a4bf333ba01d2e3fd81ad9e4b14fb205e4d +Subproject commit dd07ccc409372d1ed2b6fb473928cf8319984d81
[Libreoffice-ux-advise] [Bug 122970] Direct cursor leaves screen trail with mouse pointer movement and no text
https://bugs.documentfoundation.org/show_bug.cgi?id=122970 Hossein changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |hoss...@libreoffice.org |desktop.org | -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 122970] Direct cursor leaves screen trail with mouse pointer movement and no text
https://bugs.documentfoundation.org/show_bug.cgi?id=122970 Hossein changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |hoss...@libreoffice.org |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] help.git: Branch 'libreoffice-7-6' - source/text
source/text/shared/00/0208.xhp |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit dd07ccc409372d1ed2b6fb473928cf8319984d81 Author: Andrea Gelmini AuthorDate: Tue Jun 13 20:47:15 2023 +0200 Commit: Adolfo Jayme Barrientos CommitDate: Sun Jun 18 01:17:52 2023 +0200 Fix typo Change-Id: Id2a262225d6f9029dc706c309ddcf308fa55ee62 Reviewed-on: https://gerrit.libreoffice.org/c/help/+/153000 Tested-by: Jenkins Reviewed-by: Julien Nabet (cherry picked from commit f252a686b4231cfcd3e00756b1a59509aa3ae407) Reviewed-on: https://gerrit.libreoffice.org/c/help/+/153216 Reviewed-by: Adolfo Jayme Barrientos diff --git a/source/text/shared/00/0208.xhp b/source/text/shared/00/0208.xhp index 38cdfd518b..9621d543a1 100644 --- a/source/text/shared/00/0208.xhp +++ b/source/text/shared/00/0208.xhp @@ -116,7 +116,7 @@ Detect scientific notation When this option is enabled, Calc will automatically detect numbers with scientific notation, like 5E2 for 500. The selected language influences how scientific notation is detected, since different languages and regions many have different decimal separator. -This option can be be disabled only if Detect special numbers option is previously disabled. +This option can be disabled only if Detect special numbers option is previously disabled. When this option is disabled, Calc will detect and convert only numbers in decimal notation. The rest will be imported as text. A decimal number string can have digits 0-9, thousands separators, and a decimal separator. Thousands separators and decimal separators may vary with the selected language and region.
[Libreoffice-bugs] [Bug 155902] writer crashes regularly after updating to dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=155902 --- Comment #2 from jim hamilton --- My OS is Windows 10 - basically always updated. Note: I get the crash unexpectedly. It might be two days before it crashes. I've updated to LibreOffice_7.5.4_Win_x86-64 since filing this bug report and will see if there is any change.. PS I run a pretty strong computer i7 with 32gb of memory, etc. but I run it pretty hard :) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146976] Writer Crashes After Opening A Large File of 2000 text pages
https://bugs.documentfoundation.org/show_bug.cgi?id=146976 Caolán McNamara changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #15 from Caolán McNamara --- sounds like the same problem them, running out of windows resource handles -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Bug 133092 depends on bug 146976, which changed state. Bug 146976 Summary: Writer Crashes After Opening A Large File of 2000 text pages https://bugs.documentfoundation.org/show_bug.cgi?id=146976 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155903] Writer: Error opening a .docx file containing audio inserted files
https://bugs.documentfoundation.org/show_bug.cgi?id=155903 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #3 from m.a.riosv --- Created attachment 187967 --> https://bugs.documentfoundation.org/attachment.cgi?id=187967=edit Screenshot error with word. The file shows an error window opening with word. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155894] column sum problem left below
https://bugs.documentfoundation.org/show_bug.cgi?id=155894 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |NEEDINFO --- Comment #1 from m.a.riosv --- Maybe a more detailed information, and a step by step with a sample file could help. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155881] Saving causes consolidate dialog to fill up with garbage ranges
https://bugs.documentfoundation.org/show_bug.cgi?id=155881 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #5 from m.a.riosv --- But it doesn't happen to me with a file from scratch. In that case, second ranges are lost. https://bugs.documentfoundation.org/show_bug.cgi?id=45862 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155903] Writer: Error opening a .docx file containing audio inserted files
https://bugs.documentfoundation.org/show_bug.cgi?id=155903 --- Comment #2 from FLS --- The same file saved in the native ODF fprmat is OK. It has NO PROBLEM AT ALL. That means the problem arises when converting the file to the .docx format. The bug is inside the converter. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155903] Writer: Error opening a .docx file containing audio inserted files
https://bugs.documentfoundation.org/show_bug.cgi?id=155903 --- Comment #1 from FLS --- Created attachment 187966 --> https://bugs.documentfoundation.org/attachment.cgi?id=187966=edit Sample of a corrupted file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155903] New: Writer: Error opening a .docx file containing audio inserted files
https://bugs.documentfoundation.org/show_bug.cgi?id=155903 Bug ID: 155903 Summary: Writer: Error opening a .docx file containing audio inserted files 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: francois.sal...@laposte.net Description: When creating a doc file and saving it in the .docx format, there is no reported problem to save it. BUT, after closing the file normally, an error occcurs when attempting to open it again. The following error message appears: Detalles del error: SAXException: [word/document.xml line 2]: Namespace prefix p14 on media is not defined Si continúa con la importación, podrían producirse pérdidas o daños de datos y la aplicación podría volverse inestable o cerrarse inesperadamente. Going ahead, it imports only the data previous to the first audio embedded file. The rest is lost. Steps to Reproduce: 1.Open the file submitted in the attachment 2. Observe the error report 3. Actual Results: Always the same error when aopening the file occurs. Expected Results: To be able to save doc documents with audio embedded files in the .docx format. Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: es Module: TextDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: no -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155902] writer crashes regularly after updating to dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=155902 --- Comment #1 from IvoErMejo --- What's your OS? I tested your bug and inside Linux openSUSE KDE Plasma and Writer 7.5.4.1. I have no bug. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155902] New: writer crashes regularly after updating to dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=155902 Bug ID: 155902 Summary: writer crashes regularly after updating to dark mode Product: LibreOffice Version: 7.5.3.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jhamil...@coreresonance.com Description: I was very excited to update to 7.5.3.2 to access what I believed was a robust version of Libre Writer so that I could use dark mode.. but find that Libre Writer crashes regularly. It can crash more than once a day but just today, it crashed after I went back to the latest article I am writing and crashed shortly after I started editing. Seems it might crash early in the day of first using Writer.. Not familiar with any of the other products in Office.. Otherwise, love the software! Steps to Reproduce: 1.seems it happens after I start my day with Writer.. but likely happens most any time... More than once a day? Yes. 2. Screen freezes and then Writer crashes 3. restore brings back all documents with a 1min save feature Actual Results: This crash has been occurring regularly since updating to 7.5.3.2. I've looked at release notes for this and later versions and see nothing about crashes assumedly associated with dark mode.. PS Love dark mode.. Hope you find a solution soon! Expected Results: ? Reproducible: Always User Profile Reset: No Additional Info: did not try resetting my user profile.. Not willing to go into safe mode, etc.. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: oox/source
oox/source/drawingml/table/predefined-table-styles.cxx |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
New commits:
commit 48af1ee603149f09236f980c7b323997696bd946
Author: Andrea Gelmini
AuthorDate: Sat Jun 17 15:12:07 2023 +0200
Commit: Julien Nabet
CommitDate: Sat Jun 17 20:53:48 2023 +0200
Fix typo in code
Change-Id: I8f7e3b11b952b1882ca8e67619145c0dca71820a
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/153205
Tested-by: Jenkins
Reviewed-by: Julien Nabet
diff --git a/oox/source/drawingml/table/predefined-table-styles.cxx
b/oox/source/drawingml/table/predefined-table-styles.cxx
index 513637e3c7ee..451759036835 100644
--- a/oox/source/drawingml/table/predefined-table-styles.cxx
+++ b/oox/source/drawingml/table/predefined-table-styles.cxx
@@ -204,9 +204,9 @@ constexpr frozen::unordered_map tokens{
sal_Int32 resolveToken(OUString const& rString)
{
-auto interator = tokens.find(rString);
-if (interator != tokens.end())
-return interator->second;
+auto iterator = tokens.find(rString);
+if (iterator != tokens.end())
+return iterator->second;
return XML_dk1;
}
[Libreoffice-commits] core.git: tools/source
tools/source/datetime/duration.cxx |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit c041b5a3bc3301f137b141e1731b711178d536d2 Author: Andrea Gelmini AuthorDate: Sat Jun 17 18:09:17 2023 +0200 Commit: Julien Nabet CommitDate: Sat Jun 17 20:50:14 2023 +0200 Fix typo Change-Id: I1d7b271eed63dd0272bd92431eaac3e2dfbfe2b5 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/153206 Tested-by: Jenkins Reviewed-by: Julien Nabet diff --git a/tools/source/datetime/duration.cxx b/tools/source/datetime/duration.cxx index 07f79929177f..c8cb4616eb08 100644 --- a/tools/source/datetime/duration.cxx +++ b/tools/source/datetime/duration.cxx @@ -67,7 +67,7 @@ Duration::Duration(double fTimeInDays) fFrac = ::rtl::math::approxFloor(fFrac); sal_Int64 nNS = static_cast(fFrac); // Round by 1 nanosecond if it's just 1 off to a second, i.e. -// 09 or 01. This could be losened to rounding by 2 or +// 09 or 01. This could be loosened to rounding by 2 or // such if necessary. const sal_Int64 nN = nNS % Time::nanoSecPerSec; if (std::abs(nN) == 1)
[Libreoffice-bugs] [Bug 155901] New: MCGR: Adding gradient to user palette or setting a border changes last stop offset to 1
https://bugs.documentfoundation.org/show_bug.cgi?id=155901 Bug ID: 155901 Summary: MCGR: Adding gradient to user palette or setting a border changes last stop offset to 1 Product: LibreOffice Version: 24.2.0.0 alpha0+ Master Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rb.hensc...@t-online.de CC: armin.le.gr...@me.com Created attachment 187965 --> https://bugs.documentfoundation.org/attachment.cgi?id=187965=edit Gradient with last stop at offset 0.69 (1) Open attached document. Select the shape and open Area-dialog from the context menu of the shape. Click 'Add' button to add the gradient to the user gradient palette. Enter a name. OK. Notice that the offset of the last color stop has changed. Or (2) Open attached document. Select the shape and open Area-dialog from the context menu of the shape. Change the value of the 'Transition start' field to a different value. Click into any other field to update the setting. Notice that the offset of the last color stop has changed. The changed offset is already visible in the preview in the dialog. Hi Armin, do you have a code pointer for me, where this change might happen? -- You are receiving this mail because: You are the assignee for the bug.
GSoC Week 2 Report: Improving PGP/GPG Encryption Support
Dear everyone, I hope this email finds you well. I'm excited to share my progress in GSoC. You can find the complete report on my blog at the following link: https://tokiesan.github.io/blogposts/gsoc/week_2_report.html *TL;DR: *Finished working on remembering digital signatures features, started working on caching certificates session-wise. I would like to express my gratitude to Thorsten Behrens, Heiko Tietze, and Hossein Nourikhah for their invaluable guidance and support throughout this journey. Stay tuned for more updates on my progress! If you have any suggestions, questions, or just want to chat, please feel free to reach out to me. Best regards, Tokhy
[Libreoffice-bugs] [Bug 155900] New: 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 Bug ID: 155900 Summary: Font color in pdf, created from impress ppt/odp file, is reduced to black for bold text. Product: LibreOffice Version: 7.5.3.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ki...@freenet.de Description: Exporting Impress slide-show to PDF changes color of bold text from any color to black (and only for bold text). Steps to Reproduce: 1. Start Impress 2. Select "Freshes" from Templates 3. Change font color of BOLD text (e.g. the first heading) to a color other than black via right click → 'Character' → Tab 'Font Effects', e.g. to blue (or keep the inital white version) 4. Press button "Export directly to PDF" 5. Check font color of the PDF file Actual Results: The font color changes to black in the PDF (happens ONLY for BOLD text) Expected Results: The PDF should adopt the font color from the impress file Reproducible: Always User Profile Reset: No Additional Info: Version 7.5.3.2 (X86_64) CPU threads: 4; OS: Linux 6.3 UI render: default; VCL: gtk3 en-US (en_US.UTF-8); UI:en-US Calc_threaded Fedora 38, happens with rpm and Flatpak version -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155898] table in footer is missing on .doc file
https://bugs.documentfoundation.org/show_bug.cgi?id=155898 Eike Rathke changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155898] table in footer is missing on .doc file
https://bugs.documentfoundation.org/show_bug.cgi?id=155898 Eike Rathke changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Eike Rathke --- *** This bug has been marked as a duplicate of bug 155899 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155899] only table in footer is missing on .doc file
https://bugs.documentfoundation.org/show_bug.cgi?id=155899 --- Comment #4 from Eike Rathke --- *** Bug 155898 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 155896] Libre Calc does not do the PEMDAS functions correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=155896 Eike Rathke changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #2 from Eike Rathke --- 2(7-2) is *NOT* a valid spreadsheet formula expression because it lacks an operator between 2 and (7-2). Specifically, 20/2(7-2) would never be evaluated as 20/(2*(7-2)) or 20/2/(7-2) what you seem to expect, not even by a TI calculator. Even WolframAlpha agrees that 20/2(7-2) is evaluated as 20/2*(7-2) https://www.wolframalpha.com/input?i=20%2F2%287-2%29 -- You are receiving this mail because: You are the assignee for the bug.
macOS Intel nightly builds
Hi everyone, I noticed that there have been no new macOS Intel nightly builds since June 7. Are there build failures on macOS Intel? I ask because I committed the following change about 12 hours after the last posted macOS Intel nightly build: https://gerrit.libreoffice.org/c/core/+/152655 I developed this on macOS Silicon so if you are seeing errors from the codesign command (even though nightly builds aren't codesigned), then it is most likely due to the above patch. Regardless of the cause, if you are having build failures on macOS Intel, I would be happy to look at the build logs if you can post a link. Regards, Patrick
[Libreoffice-bugs] [Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Bug 133092 depends on bug 146626, which changed state. Bug 146626 Summary: Crash in macOS Calc on font size operation on multi-monitor setup https://bugs.documentfoundation.org/show_bug.cgi?id=146626 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104160] [META] Bugs and features related to multiple monitor setups
https://bugs.documentfoundation.org/show_bug.cgi?id=104160 Bug 104160 depends on bug 146626, which changed state. Bug 146626 Summary: Crash in macOS Calc on font size operation on multi-monitor setup https://bugs.documentfoundation.org/show_bug.cgi?id=146626 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
Re: Frozen library - 0-cost initialisation, immutable, fixed-size containers
Am 17.06.23 um 12:31 schrieb Tomaž Vajngerl: Any thoughts appreciated. I hope this will not cause problems and make the code in the long run better readable, and also faster. You at least should have added the standard option to use the library from the system. (yes, even if it's header-only. And yes, even if not packaged for distros, then this needs to be packaged, as I just did and submitted https://gerrit.libreoffice.org/c/core/+/153208) Regadrs, Rene
[Libreoffice-bugs] [Bug 155886] Hash marks that indicate "cell too narrow" should expand according to the cell width
https://bugs.documentfoundation.org/show_bug.cgi?id=155886 ady changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Severity|normal |enhancement --- Comment #1 from ady --- > Hash marks should expand fill the cell width. FWIW, I agree... but with a minimum of three # marks, even when the width of the cell is not enough for all three marks. If the width of the cell is not enough for all three # marks, then the behavior should not be modified in comparison to the current one (unless and until tdf#129847 is implemented, if implemented). If the width of the cell is enough for more than 3 # marks, then additional # marks should be displayed in the cell, until the width of the cell is full of # marks, but not over it. I am setting this as NEW ENHANCEMENT request, even when there is still needsUXEval. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 155886] Hash marks that indicate "cell too narrow" should expand according to the cell width
https://bugs.documentfoundation.org/show_bug.cgi?id=155886 ady changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Severity|normal |enhancement --- Comment #1 from ady --- > Hash marks should expand fill the cell width. FWIW, I agree... but with a minimum of three # marks, even when the width of the cell is not enough for all three marks. If the width of the cell is not enough for all three # marks, then the behavior should not be modified in comparison to the current one (unless and until tdf#129847 is implemented, if implemented). If the width of the cell is enough for more than 3 # marks, then additional # marks should be displayed in the cell, until the width of the cell is full of # marks, but not over it. I am setting this as NEW ENHANCEMENT request, even when there is still needsUXEval. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-commits] core.git: Branch 'libreoffice-7-6' - 2 commits - include/tools sc/inc sc/source tools/CppunitTest_tools_test.mk tools/Library_tl.mk tools/qa tools/source
include/tools/datetime.hxx |9 +
include/tools/duration.hxx | 72 +
sc/inc/table.hxx |8 -
sc/source/core/data/documen3.cxx |3
sc/source/core/data/table4.cxx | 117 +--
tools/CppunitTest_tools_test.mk|1
tools/Library_tl.mk|1
tools/qa/cppunit/test_duration.cxx | 278 +
tools/source/datetime/datetime.cxx | 38 ++---
tools/source/datetime/duration.cxx | 256 ++
10 files changed, 717 insertions(+), 66 deletions(-)
New commits:
commit 0770c99928fa0c4af23b06cbf694ee77ee78b836
Author: Eike Rathke
AuthorDate: Sat Jun 17 01:05:48 2023 +0200
Commit: Eike Rathke
CommitDate: Sat Jun 17 18:04:56 2023 +0200
Resolves: tdf#153517 Use tools::Duration for FillSeries with (date+)time
Change-Id: I18567fdac512ee786ce4b0785b01b2ae6da7450e
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/153203
Tested-by: Jenkins
Reviewed-by: Eike Rathke
(cherry picked from commit 45bee6b9a0e620758d0d4079d832d80095164b0a)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/153219
diff --git a/sc/inc/table.hxx b/sc/inc/table.hxx
index a2cc60f9d70e..0662053cb89c 100644
--- a/sc/inc/table.hxx
+++ b/sc/inc/table.hxx
@@ -715,7 +715,8 @@ public:
sc::UpdatedRangeNames& rIndexes) const;
voidFill( SCCOL nCol1, SCROW nRow1, SCCOL nCol2, SCROW nRow2,
sal_uInt64 nFillCount, FillDir eFillDir, FillCmd
eFillCmd, FillDateCmd eFillDateCmd,
-double nStepValue, double nMaxValue, ScProgress*
pProgress);
+double nStepValue, const tools::Duration&
rDurationStep,
+double nMaxValue, ScProgress* pProgress);
OUStringGetAutoFillPreview( const ScRange& rSource, SCCOL nEndX, SCROW
nEndY );
void UpdateSelectionFunction( ScFunctionData& rData, const ScMarkData&
rMark );
@@ -1191,13 +1192,14 @@ private:
voidFillSeries( SCCOL nCol1, SCROW nRow1, SCCOL nCol2, SCROW nRow2,
sal_uInt64 nFillCount, FillDir eFillDir,
FillCmd eFillCmd,
FillDateCmd eFillDateCmd,
-double nStepValue, double nMaxValue,
sal_uInt16 nMinDigits,
+double nStepValue, const tools::Duration&
rDurationStep,
+double nMaxValue, sal_uInt16 nMinDigits,
bool bAttribs, ScProgress* pProgress,
bool bSkipOverlappedCells = false,
std::vector* pNonOverlappedCellIdx
= nullptr);
voidFillAnalyse( SCCOL nCol1, SCROW nRow1, SCCOL nCol2, SCROW
nRow2,
FillCmd& rCmd, FillDateCmd& rDateCmd,
-double& rInc, sal_uInt16& rMinDigits,
+double& rInc, tools::Duration& rDuration,
sal_uInt16& rMinDigits,
ScUserListData*& rListData, sal_uInt16&
rListIndex,
bool bHasFiltered, bool& rSkipOverlappedCells,
std::vector& rNonOverlappedCellIdx
);
diff --git a/sc/source/core/data/documen3.cxx b/sc/source/core/data/documen3.cxx
index b1cf5fe81b8c..8d0d2ba9a665 100644
--- a/sc/source/core/data/documen3.cxx
+++ b/sc/source/core/data/documen3.cxx
@@ -29,6 +29,7 @@
#include
#include
#include
+#include
#include
#include
#include
@@ -1171,7 +1172,7 @@ void ScDocument::Fill(SCCOL nCol1, SCROW nRow1, SCCOL
nCol2, SCROW nRow2, ScProg
{
maTabs[rTab]->Fill(nCol1, nRow1, nCol2, nRow2,
nFillCount, eFillDir, eFillCmd, eFillDateCmd,
-nStepValue, nMaxValue, pProgress);
+nStepValue, tools::Duration(), nMaxValue,
pProgress);
RefreshAutoFilter(aRange.aStart.Col(), aRange.aStart.Row(),
aRange.aEnd.Col(), aRange.aEnd.Row(), rTab);
}
}
diff --git a/sc/source/core/data/table4.cxx b/sc/source/core/data/table4.cxx
index 10c27f8d2c84..9c6852990efe 100644
--- a/sc/source/core/data/table4.cxx
+++ b/sc/source/core/data/table4.cxx
@@ -28,6 +28,7 @@
#include
#include
#include
+#include
#include
#include
@@ -215,32 +216,20 @@ double approxDiff( double a, double b )
return rtl::math::round(c, -std::max(nExp, nExpArg));
}
-double approxTimeDiff( double a, double b )
+double approxTypedDiff( double a, double b, bool bTime, tools::Duration&
rDuration )
{
-// Scale to hours, round to "nanohours" (multiple nanoseconds), scale back.
-// Get back 0.0417 instead of 0.04166700621136 or
-// 0.0414241347 (raw a-b) for one hour, or worse the approxDiff()
-// 0.0416665997 value. Though there is no such
[Libreoffice-bugs] [Bug 152370] MariaDB direct connection: Access through socket to separate instance of MariaDB impossible
https://bugs.documentfoundation.org/show_bug.cgi?id=152370 --- Comment #4 from László Károlyi --- Hey, this is a long standing bug, I can confirm this for ages now. I get the same error when trying to connect to a local mariadb instance via a unix socket (non-tcp). The same error shows: "Can't connect to server on 'localhost' (111) at /usr/src/debug/libreoffice-fresh/libreoffice-7.5.3.2/connectivity/source/drivers/mysqlc/mysqlc_general.cxx:120" It seems to me that using the unix socket is totally ignored, it always wants to connect via TCP, which my mariadb instance has disabled. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155896] Libre Calc does not do the PEMDAS functions correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=155896 ady changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG --- Comment #1 from ady --- A formula such as: =20/2(7-2) ...would return Err:509, Operator missing (between the 2 and the parenthesis). In Calc, the multiplication operator has to be there. Additionally, there are priorities that are assumed by Calc, which can be changed by using additional parentheses; for example: =20/(2*(7-2)) Please search for info in the online help, the user mailing lists, or use https://ask.libreoffice.org next time before posting a bug report. Closing as NOTABUG. -- 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 Bug 103341 depends on bug 90507, which changed state. Bug 90507 Summary: Tools - AutoCorrect - Apply converts non-empty "Default Paragraph Style" paragraphs to "Text Body" PS --even when no [M] options are selected https://bugs.documentfoundation.org/show_bug.cgi?id=90507 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108253] [META] Calc cell formula bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108253 Bug 108253 depends on bug 132026, which changed state. Bug 132026 Summary: Entering "-" in a cell formatted as text puts Calc into formula-entering mode https://bugs.documentfoundation.org/show_bug.cgi?id=132026 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155891] Allow blocking cell edit mode unless explicitly allowed (ie. pressing F2) to prevent accidental data manipulation
https://bugs.documentfoundation.org/show_bug.cgi?id=155891 --- Comment #1 from freew...@poczta.fm --- tl;dr I request an option to make it so pressing F2 or ENTER (if enabled in the general options) is REQUIRED to enter the cell edit mode to enter/modify the content. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155891] Allow blocking cell edit mode unless explicitly allowed (ie. pressing F2) to prevent accidental data manipulation
https://bugs.documentfoundation.org/show_bug.cgi?id=155891 freew...@poczta.fm changed: What|Removed |Added Summary|Add an option to Block data |Allow blocking cell edit |entry unless allowed|mode unless explicitly |explicitly by pressing F2 |allowed (ie. pressing F2) |to prevent accidental data |to prevent accidental data |manipulation|manipulation -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155891] Add an option to Block data entry unless allowed explicitly by pressing F2 to prevent accidental data manipulation
https://bugs.documentfoundation.org/show_bug.cgi?id=155891 freew...@poczta.fm changed: What|Removed |Added Summary|Add an option to DISABLE|Add an option to Block data |direct data entry to|entry unless allowed |prevent accidental data |explicitly by pressing F2 |modification|to prevent accidental data ||manipulation -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155898] table in footer is missing on .doc file
https://bugs.documentfoundation.org/show_bug.cgi?id=155898 jindam, vani changed: What|Removed |Added CC||jindam.v...@disroot.org --- Comment #1 from jindam, vani --- there was some error. i did not bothered to check if this issue was created. unnecassarily created another issue https://bugs.documentfoundation.org/show_bug.cgi?id=155899 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 37259] FORMATTING Define Print Range across filtered rows fails
https://bugs.documentfoundation.org/show_bug.cgi?id=37259 --- Comment #21 from ady --- Still present in current Dev build 24.2. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155899] only table in footer is missing on .doc file
https://bugs.documentfoundation.org/show_bug.cgi?id=155899 --- Comment #3 from jindam, vani --- Created attachment 187964 --> https://bugs.documentfoundation.org/attachment.cgi?id=187964=edit screenshot libreoffice linux only table in footer is missing -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155899] only table in footer is missing on .doc file
https://bugs.documentfoundation.org/show_bug.cgi?id=155899 --- Comment #2 from jindam, vani --- Created attachment 187963 --> https://bugs.documentfoundation.org/attachment.cgi?id=187963=edit screenshot libreoffice viewer android only table in footer is missing -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155899] only table in footer is missing on .doc file
https://bugs.documentfoundation.org/show_bug.cgi?id=155899 jindam, vani changed: What|Removed |Added CC||jindam.v...@disroot.org --- Comment #1 from jindam, vani --- Created attachment 187962 --> https://bugs.documentfoundation.org/attachment.cgi?id=187962=edit screenshot word text & table are visible on footer -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155899] New: only table in footer is missing on .doc file
https://bugs.documentfoundation.org/show_bug.cgi?id=155899 Bug ID: 155899 Summary: only table in footer is missing on .doc file Product: LibreOffice Version: 7.6.0.0 alpha1+ Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jindam.v...@disroot.org Created attachment 187961 --> https://bugs.documentfoundation.org/attachment.cgi?id=187961=edit bug doc text & table are visible on footer * open attachment bugdoc17062023.doc * on libreoffice viewer & writer, only text is visible, table is missing * on word, both text and table are visible * repro libreoffice: f-droid: Version: 7.6.0.0.alpha1+, Build ID: 5c1c768e128d OS: Android libreoffice: Version: 7.5.4.2 (ARM_EABI) / LibreOffice Community Build ID: 50(Build:2) CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: x11 Locale: en-US (C); UI: en-US Calc: threaded OS: NAME="openSUSE Tumbleweed", VERSION_ID="20230604" * no repro Word: Version: 1.0.1 (16.0.1.16501.20160) OS: Android -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155898] New: table in footer is missing on .doc file
https://bugs.documentfoundation.org/show_bug.cgi?id=155898 Bug ID: 155898 Summary: table in footer is missing on .doc file Product: LibreOffice Version: 7.6.0.0 alpha1+ Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jindam.v...@disroot.org Created attachment 187960 --> https://bugs.documentfoundation.org/attachment.cgi?id=187960=edit bug doc text & table are visible on footer * open attachment bugdoc17062023.doc * on libreoffice viewer & writer, only text is visible, table is missing * on word, both text and table are visible * repro libreoffice: f-droid: Version: 7.6.0.0.alpha1+, Build ID: 5c1c768e128d OS: Android libreoffice: Version: 7.5.4.2 (ARM_EABI) / LibreOffice Community Build ID: 50(Build:2) CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: x11 Locale: en-US (C); UI: en-US Calc: threaded OS: NAME="openSUSE Tumbleweed", VERSION_ID="20230604" * no repro Word: Version: 1.0.1 (16.0.1.16501.20160) OS: Android -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108827] [META] Calc functions bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108827 Bug 108827 depends on bug 155402, which changed state. Bug 155402 Summary: FILEOPEN XLSX CELL() function gives different value compared to Excel with filename parameter https://bugs.documentfoundation.org/show_bug.cgi?id=155402 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113499] [META] AutoFill bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=113499 Bug 113499 depends on bug 153517, which changed state. Bug 153517 Summary: CALC - wrong time value when using the autofill function and minutes are entered (not for 00 min) https://bugs.documentfoundation.org/show_bug.cgi?id=153517 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155873] Column not Shown Centered
https://bugs.documentfoundation.org/show_bug.cgi?id=155873 jindam, vani changed: What|Removed |Added CC||jindam.v...@disroot.org --- Comment #2 from jindam, vani --- when i open .odt file: * left align: r1,c1; r3,c3; r4,c4; r11,c11 * centered align: r2,c2; r5-10,c5-10 format —> align text: result * left_ all column1 cells are aligned left * centered_ except: r1,c1; r3,c3; r4,c4; r11,c11 * right_ except: r1,c1; r3,c3; r4,c4; r11,c11 * justified_ all column1 cells are aligned left version & os: libreoffice: Version: 7.5.4.2 (ARM_EABI) / LibreOffice Community Build ID: 50(Build:2) CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: x11 Locale: en-US (C); UI: en-US Calc: threaded OS: NAME="openSUSE Tumbleweed", VERSION_ID="20230604" -- You are receiving this mail because: You are the assignee for the bug.
Re: GSoC'23 - Week 2 Report
Please don't send attachments. Copying the text: Commit feature extraction Commit feature extraction is finished with multiprocessing. The commits come from the csv table. Features are based on the patch (what changes in the commit), code features, author features and so on. The output is saved in data/commits.json. Unit test feature extraction Unit test feature extraction is finished with single thread with speed up. It computes features of unit tests from data/commits.json
[Libreoffice-commits] core.git: sc/inc sc/source
sc/inc/table.hxx |8 +-
sc/source/core/data/documen3.cxx |3 -
sc/source/core/data/table4.cxx | 117 ---
3 files changed, 81 insertions(+), 47 deletions(-)
New commits:
commit 30c48379c7b791edc615e7691691e344baa455a3
Author: Eike Rathke
AuthorDate: Sat Jun 17 01:05:48 2023 +0200
Commit: Eike Rathke
CommitDate: Sat Jun 17 16:10:08 2023 +0200
Resolves: tdf#153517 Use tools::Duration for FillSeries with (date+)time
Change-Id: I18567fdac512ee786ce4b0785b01b2ae6da7450e
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/153203
Tested-by: Jenkins
Reviewed-by: Eike Rathke
diff --git a/sc/inc/table.hxx b/sc/inc/table.hxx
index a2cc60f9d70e..0662053cb89c 100644
--- a/sc/inc/table.hxx
+++ b/sc/inc/table.hxx
@@ -715,7 +715,8 @@ public:
sc::UpdatedRangeNames& rIndexes) const;
voidFill( SCCOL nCol1, SCROW nRow1, SCCOL nCol2, SCROW nRow2,
sal_uInt64 nFillCount, FillDir eFillDir, FillCmd
eFillCmd, FillDateCmd eFillDateCmd,
-double nStepValue, double nMaxValue, ScProgress*
pProgress);
+double nStepValue, const tools::Duration&
rDurationStep,
+double nMaxValue, ScProgress* pProgress);
OUStringGetAutoFillPreview( const ScRange& rSource, SCCOL nEndX, SCROW
nEndY );
void UpdateSelectionFunction( ScFunctionData& rData, const ScMarkData&
rMark );
@@ -1191,13 +1192,14 @@ private:
voidFillSeries( SCCOL nCol1, SCROW nRow1, SCCOL nCol2, SCROW nRow2,
sal_uInt64 nFillCount, FillDir eFillDir,
FillCmd eFillCmd,
FillDateCmd eFillDateCmd,
-double nStepValue, double nMaxValue,
sal_uInt16 nMinDigits,
+double nStepValue, const tools::Duration&
rDurationStep,
+double nMaxValue, sal_uInt16 nMinDigits,
bool bAttribs, ScProgress* pProgress,
bool bSkipOverlappedCells = false,
std::vector* pNonOverlappedCellIdx
= nullptr);
voidFillAnalyse( SCCOL nCol1, SCROW nRow1, SCCOL nCol2, SCROW
nRow2,
FillCmd& rCmd, FillDateCmd& rDateCmd,
-double& rInc, sal_uInt16& rMinDigits,
+double& rInc, tools::Duration& rDuration,
sal_uInt16& rMinDigits,
ScUserListData*& rListData, sal_uInt16&
rListIndex,
bool bHasFiltered, bool& rSkipOverlappedCells,
std::vector& rNonOverlappedCellIdx
);
diff --git a/sc/source/core/data/documen3.cxx b/sc/source/core/data/documen3.cxx
index b1cf5fe81b8c..8d0d2ba9a665 100644
--- a/sc/source/core/data/documen3.cxx
+++ b/sc/source/core/data/documen3.cxx
@@ -29,6 +29,7 @@
#include
#include
#include
+#include
#include
#include
#include
@@ -1171,7 +1172,7 @@ void ScDocument::Fill(SCCOL nCol1, SCROW nRow1, SCCOL
nCol2, SCROW nRow2, ScProg
{
maTabs[rTab]->Fill(nCol1, nRow1, nCol2, nRow2,
nFillCount, eFillDir, eFillCmd, eFillDateCmd,
-nStepValue, nMaxValue, pProgress);
+nStepValue, tools::Duration(), nMaxValue,
pProgress);
RefreshAutoFilter(aRange.aStart.Col(), aRange.aStart.Row(),
aRange.aEnd.Col(), aRange.aEnd.Row(), rTab);
}
}
diff --git a/sc/source/core/data/table4.cxx b/sc/source/core/data/table4.cxx
index 10c27f8d2c84..9c6852990efe 100644
--- a/sc/source/core/data/table4.cxx
+++ b/sc/source/core/data/table4.cxx
@@ -28,6 +28,7 @@
#include
#include
#include
+#include
#include
#include
@@ -215,32 +216,20 @@ double approxDiff( double a, double b )
return rtl::math::round(c, -std::max(nExp, nExpArg));
}
-double approxTimeDiff( double a, double b )
+double approxTypedDiff( double a, double b, bool bTime, tools::Duration&
rDuration )
{
-// Scale to hours, round to "nanohours" (multiple nanoseconds), scale back.
-// Get back 0.0417 instead of 0.04166700621136 or
-// 0.0414241347 (raw a-b) for one hour, or worse the approxDiff()
-// 0.0416665997 value. Though there is no such correct value,
-// IEEE-754 nearest values are
-// 0.041664353702032030923874117434024810791015625
-// (0x3FA5) and
-// 0.04167129259593593815225176513195037841796875
-// (0x3FA6).
-// This works also for a diff of seconds, unless corner cases would be
-// discovered, which would make it necessary to ditch the floating point
-// and convert to/from time structure values instead.
-return rtl::math::round((a - b) * 24, 9) / 24;
-}
-
GSoC'23 - Week 2 Report
2023-06-07-week2.md Description: application/md
[Libreoffice-bugs] [Bug 155897] New: Inconsistency concerning the deletion of single empty paragraph below TextTable
https://bugs.documentfoundation.org/show_bug.cgi?id=155897 Bug ID: 155897 Summary: Inconsistency concerning the deletion of single empty paragraph below TextTable Product: LibreOffice Version: 3.6.5.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: j...@psilosoph.de Created attachment 187959 --> https://bugs.documentfoundation.org/attachment.cgi?id=187959=edit the little demo announced in the report Having placed the hair cursor at the end of the last paragraph inside the last (bottom right) call of a TextTable with empty paragraphs below, Ctrl+Shift+Del (default shortcut) deletes the next empty paragraph. This is also the case if the TextTable is content of the text object of a frame. Since V 3.6.5 this does no longer work if the next empty paragraph is the last one of the main text of the Writer document. It still works for the case of frame text objects. Till V 3.5.2 the removal worked, but the new state (without a paragraph below the table) did not persist a Save/Reload cycle. IMO this is only annoying if the undeletable or automatically recreated empty paragraph causes an automatic page break. But obviously this occurs - if even rarely. BTW: With the help of user code the final empty paragraph can still be removed. It will then also be automatically recreated on Reload. Concerning my statements about the working of user code you may want to test/play with the attached example. (Concerning the text objects of TextTable cells containing nested tables there are additional inconsistencies. At what time and by whom was the related part of the "architecture" specified?) -- You are receiving this mail because: You are the assignee for the bug.
