[Libreoffice-bugs] [Bug 102495] [META] KDE VCL backend bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102495 Bug 102495 depends on bug 147833, which changed state. Bug 147833 Summary: Clone Formatting added to clicked row +1 row using KDE wayland https://bugs.documentfoundation.org/show_bug.cgi?id=147833 What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100156] [META] Wayland-related bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=100156 Bug 100156 depends on bug 147833, which changed state. Bug 147833 Summary: Clone Formatting added to clicked row +1 row using KDE wayland https://bugs.documentfoundation.org/show_bug.cgi?id=147833 What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147833] Clone Formatting added to clicked row +1 row using KDE wayland
https://bugs.documentfoundation.org/show_bug.cgi?id=147833 Michael Weghorn changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REOPENED|RESOLVED --- Comment #6 from Michael Weghorn --- (In reply to robby.engelmann from comment #5) > The offset during clone formating may be solved. > However, it is hard to evaluate, because the cursor is invisible during > using the tool. This is a Qt bug, but there's a solution in LO that avoids the issue, s. tdf#15. Can you please retest with a version that includes the corresponding change? There are e.g. daily development builds available at [1]. [2] describes how to install them in parallel to an existing LO version. (Alternatively, you can wait until 7.5.2 is released.) [1] https://dev-builds.libreoffice.org/daily/master/current.html [2] https://wiki.documentfoundation.org/Installing_in_parallel/Linux -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153648] fresh past content in dark bacground CALC spreadsheet not invisible in grid
https://bugs.documentfoundation.org/show_bug.cgi?id=153648 --- Comment #2 from Lesline --- Hello. Thank you for reporting the bug. Following your instructions, I copied some text from a webpage and pasted into the spreadsheet with dark background. The pasted content appeared as white text and was readable. I was unable to reproduce the bug. The versions tested are: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: a834bbad8295cba0ca88a91a524aad48640271ec CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Kind Regards -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153648] fresh past content in dark bacground CALC spreadsheet not invisible in grid
https://bugs.documentfoundation.org/show_bug.cgi?id=153648 Lesline changed: What|Removed |Added CC||leslinetest...@gmail.com --- Comment #1 from Lesline --- Hello. Thank you for reporting the bug. Following your instructions, I copied some text from a webpage and pasted into the spreadsheet with dark background. The pasted content was displayed as white text and was readable. So I was not able to reproduce the bug. The versions tested were: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: a834bbad8295cba0ca88a91a524aad48640271ec CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Kind Regards -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: icon-themes/elementary icon-themes/elementary_svg
icon-themes/elementary/cmd/32/showbookview.png |binary icon-themes/elementary/cmd/lc_showbookview.png |binary icon-themes/elementary/cmd/sc_showbookview.png |binary icon-themes/elementary_svg/cmd/32/showbookview.svg |2 +- icon-themes/elementary_svg/cmd/lc_showbookview.svg |2 +- icon-themes/elementary_svg/cmd/sc_showbookview.svg |2 +- 6 files changed, 3 insertions(+), 3 deletions(-) New commits: commit 982b550541cc68670cad222e921fd62a4c1f232c Author: Rizal Muttaqin AuthorDate: Mon Mar 13 11:59:21 2023 +0700 Commit: Rizal Muttaqin CommitDate: Mon Mar 13 05:44:31 2023 + elementary: tdf#153609 Update Book Preview in Page Preview Change-Id: Idc5710c576b6edcea21cfad715507df1e38267c0 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/148746 Tested-by: Jenkins Reviewed-by: Rizal Muttaqin diff --git a/icon-themes/elementary/cmd/32/showbookview.png b/icon-themes/elementary/cmd/32/showbookview.png index f3170bcd4c9c..bb64b1470b7a 100644 Binary files a/icon-themes/elementary/cmd/32/showbookview.png and b/icon-themes/elementary/cmd/32/showbookview.png differ diff --git a/icon-themes/elementary/cmd/lc_showbookview.png b/icon-themes/elementary/cmd/lc_showbookview.png index aad4079901de..796b5ca20d50 100644 Binary files a/icon-themes/elementary/cmd/lc_showbookview.png and b/icon-themes/elementary/cmd/lc_showbookview.png differ diff --git a/icon-themes/elementary/cmd/sc_showbookview.png b/icon-themes/elementary/cmd/sc_showbookview.png index 9957351d4bc4..c58a9c258667 100644 Binary files a/icon-themes/elementary/cmd/sc_showbookview.png and b/icon-themes/elementary/cmd/sc_showbookview.png differ diff --git a/icon-themes/elementary_svg/cmd/32/showbookview.svg b/icon-themes/elementary_svg/cmd/32/showbookview.svg index e402f2c5119c..41e8889356e3 100644 --- a/icon-themes/elementary_svg/cmd/32/showbookview.svg +++ b/icon-themes/elementary_svg/cmd/32/showbookview.svg @@ -1 +1 @@ -http://www.w3.org/2000/svg; xmlns:xlink="http://www.w3.org/1999/xlink;> \ No newline at end of file +http://www.w3.org/2000/svg; xmlns:xlink="http://www.w3.org/1999/xlink;> \ No newline at end of file diff --git a/icon-themes/elementary_svg/cmd/lc_showbookview.svg b/icon-themes/elementary_svg/cmd/lc_showbookview.svg index 257ee4a47ddf..b80056d62384 100644 --- a/icon-themes/elementary_svg/cmd/lc_showbookview.svg +++ b/icon-themes/elementary_svg/cmd/lc_showbookview.svg @@ -1 +1 @@ -http://www.w3.org/2000/svg; xmlns:xlink="http://www.w3.org/1999/xlink;> \ No newline at end of file +http://www.w3.org/2000/svg; xmlns:xlink="http://www.w3.org/1999/xlink;> \ No newline at end of file diff --git a/icon-themes/elementary_svg/cmd/sc_showbookview.svg b/icon-themes/elementary_svg/cmd/sc_showbookview.svg index f2cecd6d1ad7..6e0ac00dcdfc 100644 --- a/icon-themes/elementary_svg/cmd/sc_showbookview.svg +++ b/icon-themes/elementary_svg/cmd/sc_showbookview.svg @@ -1 +1 @@ -http://www.w3.org/2000/svg; xmlns:xlink="http://www.w3.org/1999/xlink;> \ No newline at end of file +http://www.w3.org/2000/svg; xmlns:xlink="http://www.w3.org/1999/xlink;> \ No newline at end of file
[Libreoffice-bugs] [Bug 153108] Request for new Help page for Calc, regarding its zoom feature, usage and shortcuts
https://bugs.documentfoundation.org/show_bug.cgi?id=153108 Adolfo Jayme Barrientos changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED Whiteboard||target:7.6.0 --- Comment #1 from Adolfo Jayme Barrientos --- https://git.libreoffice.org/help/+/b6d4faa7e677a53d4bd36c44778d87e51bd206c8%5E%21 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 80430] [META] Documentation gap for new features
https://bugs.documentfoundation.org/show_bug.cgi?id=80430 Bug 80430 depends on bug 153108, which changed state. Bug 153108 Summary: Request for new Help page for Calc, regarding its zoom feature, usage and shortcuts https://bugs.documentfoundation.org/show_bug.cgi?id=153108 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154152] Paste-Special of plain text as Text, Number or Formula does nothing
https://bugs.documentfoundation.org/show_bug.cgi?id=154152 Lesline changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||leslinetest...@gmail.com Ever confirmed|0 |1 --- Comment #1 from Lesline --- Hello Eval. Thank you for reporting the bug. I can confirm that I was able to reproduce the bug using the steps you provided. The versions tested are as follows: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: a834bbad8295cba0ca88a91a524aad48640271ec CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Kind Regards -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153609] Elementary's Book Preview icon not distinct enough to Two Pages Preview
https://bugs.documentfoundation.org/show_bug.cgi?id=153609 Rizal Muttaqin changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |riz...@libreoffice.org |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97354] formula is hidden when conditional format dialogue box is opened
https://bugs.documentfoundation.org/show_bug.cgi?id=97354 --- Comment #11 from lvm --- repro in Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-GB (en_GB.UTF-8); UI: en-GB Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153591] Spellchecking can not be disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=153591 Lesline changed: What|Removed |Added CC||leslinetest...@gmail.com --- Comment #1 from Lesline --- Hello Victor. Thank you for reporting the bug. I followed your steps and added some foreign text which the spellchecker marked as erroneous [as expected]. I was however, able to disable the spellchecker by following the instructions at the link below which I found after a search. Once I disabled the spellchecker, the foreign text was no longer marked as erroneous.The steps are: Tools > Language > For All Text > None(Do Not Check Spelling) https://ask.libreoffice.org/t/turn-off-spell-check/65490 Versions used to test are as follows: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: a834bbad8295cba0ca88a91a524aad48640271ec CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Kind Regards -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150785] Color pickers reset to defaults on User Interface change
https://bugs.documentfoundation.org/show_bug.cgi?id=150785 Joe T changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150785] Color pickers reset to defaults on User Interface change
https://bugs.documentfoundation.org/show_bug.cgi?id=150785 Joe T changed: What|Removed |Added CC||thooke...@gmail.com --- Comment #4 from Joe T --- Created attachment 185920 --> https://bugs.documentfoundation.org/attachment.cgi?id=185920=edit Screen recording of described bug Apologies for letting the info request sit for so long. I didn't receive any update emails. I've added myself to the CC list (again?) to be sure. Attached is a screen recording of the bug. Notes: * I updated to version 7.5.1 * The default seems to have changed from Yellow to Dark Red 2, which is the selection the color picker starts and ends with. * It doesn't matter if I leave the colored text selected or not, the picker resets. I can record that as well if necessary. * It doesn't matter which UI layout change is selected, the picker resets. I'll record that if necessary. As shown in the video, the steps are as I previously described: 1. Put some text into a document. 2. Select some text. 3. Open the text color picker, choose something other than the default - to show distinctly that the picker selection has changed. 4. Open View > User Interface... 5. Select a different UI layout. 6. Apply changes * It's in this transition that the picker resets 7. Close the UI dialog. I know this can be easily and consistently reproduced because it took several attempts to get the recording right. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154001] Checking for extension updates crashes LO
https://bugs.documentfoundation.org/show_bug.cgi?id=154001 --- Comment #9 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153975] Win11 BSOD when I click LibreOffice "Help" (PAGE_FAULT_IN_NONPAGED_AREA)
https://bugs.documentfoundation.org/show_bug.cgi?id=153975 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154001] Checking for extension updates crashes LO
https://bugs.documentfoundation.org/show_bug.cgi?id=154001 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148547] FILESAVE Saving CSV file(s) corrupt randomly
https://bugs.documentfoundation.org/show_bug.cgi?id=148547 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 153975] Win11 BSOD when I click LibreOffice "Help" (PAGE_FAULT_IN_NONPAGED_AREA)
https://bugs.documentfoundation.org/show_bug.cgi?id=153975 --- Comment #22 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 40176] Show special paste options when needed
https://bugs.documentfoundation.org/show_bug.cgi?id=40176 --- Comment #29 from QA Administrators --- Dear mrkazoodle, 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 109237] [META] CSV export bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109237 Bug 109237 depends on bug 148547, which changed state. Bug 148547 Summary: FILESAVE Saving CSV file(s) corrupt randomly https://bugs.documentfoundation.org/show_bug.cgi?id=148547 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148547] FILESAVE Saving CSV file(s) corrupt randomly
https://bugs.documentfoundation.org/show_bug.cgi?id=148547 --- Comment #5 from QA Administrators --- Dear Kiki, 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 150911] Copying png pictures to libre office presentaion (.odp) on Mac M1 Max makes crash
https://bugs.documentfoundation.org/show_bug.cgi?id=150911 --- Comment #3 from QA Administrators --- Dear Stefan Noll, 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 150400] File menu is missing some items
https://bugs.documentfoundation.org/show_bug.cgi?id=150400 --- Comment #9 from QA Administrators --- Dear tomsaine, 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 150785] Color pickers reset to defaults on User Interface change
https://bugs.documentfoundation.org/show_bug.cgi?id=150785 --- Comment #3 from QA Administrators --- Dear Joe T, 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 97354] formula is hidden when conditional format dialogue box is opened
https://bugs.documentfoundation.org/show_bug.cgi?id=97354 --- Comment #10 from QA Administrators --- Dear lvm, 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 90852] TOOLBAR: 'Area Style / Filing' drop down control doesnt update 'Fill Color' drop down
https://bugs.documentfoundation.org/show_bug.cgi?id=90852 --- Comment #7 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140963] SVG in Writer leads to huge and slow-rendering PDF export
https://bugs.documentfoundation.org/show_bug.cgi?id=140963 --- Comment #5 from QA Administrators --- Dear Robert, 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 140468] Cursor position changes after insertion of image
https://bugs.documentfoundation.org/show_bug.cgi?id=140468 --- Comment #8 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139769] LO Draw - Export png with lines
https://bugs.documentfoundation.org/show_bug.cgi?id=139769 --- Comment #5 from QA Administrators --- Dear karl-heinz.b...@nway.de, 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 140415] Table properties (some) are not saved when saved as .pptx (might be related to bug 89806)
https://bugs.documentfoundation.org/show_bug.cgi?id=140415 --- Comment #3 from QA Administrators --- Dear lal, 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 113281] Use default icon theme after uninstalling an extension
https://bugs.documentfoundation.org/show_bug.cgi?id=113281 --- Comment #7 from QA Administrators --- Dear Heiko Tietze, 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 106201] Centered text in inserted SVG is not centered
https://bugs.documentfoundation.org/show_bug.cgi?id=106201 --- Comment #14 from QA Administrators --- Dear menturi, 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 153560] Rename "chapter" to "heading" in Insert Field (Document tab)
https://bugs.documentfoundation.org/show_bug.cgi?id=153560 --- Comment #14 from Commit Notification --- Seth Chaiklin committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/help/commit/e87fd6170e4836d6fb426470a97d78c87659970a tdf#153560 corrections to "up to level" and "Format" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 98f35cf85ee66e995610fec92ea5224fbf28dff3 Author: Seth Chaiklin AuthorDate: Mon Mar 13 01:43:07 2023 + Commit: Gerrit Code Review CommitDate: Mon Mar 13 01:43:07 2023 + Update git submodules * Update helpcontent2 from branch 'master' to e87fd6170e4836d6fb426470a97d78c87659970a - tdf#153560 corrections to "up to level" and "Format" * Following decision in tdf#147004, comment 20, the actual rule used by "Up to level" is included in the documentation. Also needed to modify description, because level is not only referring to heading numbers. * Simplify "Format" description for type "Heading". Change-Id: I95a53b58b048a68df11706b5d5641746b5929e26 Reviewed-on: https://gerrit.libreoffice.org/c/help/+/148760 Tested-by: Jenkins Reviewed-by: Seth Chaiklin diff --git a/helpcontent2 b/helpcontent2 index 4dd6c878412f..e87fd6170e48 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit 4dd6c878412fd650ab8db543ca45006b101933ca +Subproject commit e87fd6170e4836d6fb426470a97d78c87659970a
[Libreoffice-commits] help.git: source/text
source/text/swriter/01/04090001.xhp | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) New commits: commit e87fd6170e4836d6fb426470a97d78c87659970a Author: Seth Chaiklin AuthorDate: Mon Mar 13 00:58:52 2023 + Commit: Seth Chaiklin CommitDate: Mon Mar 13 01:43:07 2023 + tdf#153560 corrections to "up to level" and "Format" * Following decision in tdf#147004, comment 20, the actual rule used by "Up to level" is included in the documentation. Also needed to modify description, because level is not only referring to heading numbers. * Simplify "Format" description for type "Heading". Change-Id: I95a53b58b048a68df11706b5d5641746b5929e26 Reviewed-on: https://gerrit.libreoffice.org/c/help/+/148760 Tested-by: Jenkins Reviewed-by: Seth Chaiklin diff --git a/source/text/swriter/01/04090001.xhp b/source/text/swriter/01/04090001.xhp index 199c7a7bcb..5b774e45a3 100644 --- a/source/text/swriter/01/04090001.xhp +++ b/source/text/swriter/01/04090001.xhp @@ -158,17 +158,17 @@ If a field is displaying a date, time or number, then Format is used to customize the appearance of the date, time, or number. Common formats are shown in the Format window, or click "Additional formats" to define a custom format. When you click "Additional formats", the Number Format dialog opens, where you can define a custom format. -If you choose “Heading number” as the Format for type Heading, then only the number of the heading is displayed in the field. If the paragraph style for the heading is not numbered, then the field is left blank. -If you choose “Heading number without separator” for the field format, then separators specified for heading numbers in Tools - Heading Numbering are not displayed. - +For type Heading, choose the format Heading number to display the heading number with the separator specified in Tools - Heading Numbering. +Choose Heading number without separator to display the heading number alone without the separator. +If the selected heading is not numbered, then the field is left blank. Inserts the field as static content, that is, the field cannot be updated. For the HTML export and import of date and time fields, special $[officename] formats are used. -Up to level -Specify the maximum number of levels of the heading number to display. The number of levels shown also depends on how many levels are available in the heading number. This option is only available for type Heading. +Up to level +Use this option with type Heading to specify which heading to display. The displayed heading is the first one before the field, whose outline level is equal to or less than the specified value.
[Libreoffice-bugs] [Bug 154147] libreOffice 7.5 problems during the conversion to pdf format
https://bugs.documentfoundation.org/show_bug.cgi?id=154147 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||miguelangelrv@libreoffice.o ||rg --- Comment #2 from m.a.riosv --- Please attach a sample file, the image doesn't let to test. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150414] Formatting issue when linking to external data
https://bugs.documentfoundation.org/show_bug.cgi?id=150414 --- Comment #6 from m.a.riosv --- (In reply to Ben from comment #5) > Please review the options in Menu/Tools/Options/Load Save/ HTML compatibility. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150281] VBA Application.CentimetersToPoints must give Double in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=150281 Baole Fang changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |baole.f...@gmail.com |desktop.org | --- Comment #2 from Baole Fang --- I start working on this. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153710] "Evaluate up to level" for Chapter Info for User-Defined Index shows only top level or all levels
https://bugs.documentfoundation.org/show_bug.cgi?id=153710
--- Comment #4 from sdc.bla...@youmail.dk ---
(In reply to Dieter from comment #3)
> So is it a bug or a docmentation issue?
(imo) both aspects are relevant -- and may be relevant for a few other tickets
(e.g., bug 93904). I will explain, so that you can decide on a way to proceed,
and also to seek your feedback on the documentation part (because it is a
little complicated).
The documentation part:
The current description cited in comment 2 was introduced recently (22 feb) as
a resolution of bug 105628.
But after that change (26 feb), I got a new/different understanding (summarized
in bug 153560 comment 10), which is what motivated comment 1.
Subsequently, it was decided (9 mar) to document actual behavior (see bug
147004, comment 20).
I just checked now and can see that I have not (yet) added the "latest"
formulation for "user-defined", but was starting to work on it now, so I will
take care of the documentation part of this ticket, following the (9 mar)
decision.
Now the complicated part.
I have just done a similar updating for "Show up to level" for caption
numbering (e.g., AutoCaption [1} (to appear soon in online help). And today a
version was made for Alphabetical Index [2], which will also be used for this
ticket ("User-defined"). I mention these two so that I can seek your opinion
about how to handle the documentation.
The issue is this: If a document uses headings in a "typical" way [3], then
the current online help (cited in comment 2) is pretty accurate. It is only
when "non-typical" structures are used that seeming bugs appear (such as this
ticket, as well as bug 147004 and bug 93904, which also involve fields.)
In AutoCaption [1], I tried to indicate a "rule" for typical heading
structures, and then put the actual rule in a "note". The "actual" rule seems
a little too complicated to "think with", especially when it seems that most of
us (as seen in BZ) are assuming that the "level" option is for specifying how
many levels to show. And as noted, with a "typical" heading structure, it DOES
work that way.
So I tried to find a way to give simple understandable help, but signal that
this is in typical situations, but then also give the "actual rule" that can be
used to explain/understand "atypical" cases.
After the new versions in [1] and [2] appear, then let me know what you think.
No doubt they can be improved. Perhaps a similar solution could work here? At
present, the version for Alphabetical Index [2] does not mention the actual
rule, but maybe it should? (there are also tooltips and extended tips)
The (maybe a) "bug" part.
Both this ticket and attachment 185594 from bug 153560 involve a situation
where the search rule does not find any match, according to the selected level.
In that case, the field displays the first heading in the document (i.e., not
following the rule anymore). In this one (corner) case, the expected behavior
should be: "nothing is displayed"
I consider the current behavior to be a bug. (the attachment gives a good/easy
demonstration).
[1} https://help.libreoffice.org/7.6/en-US/text/shared/optionen/01041100.html
[2] https://help.libreoffice.org/7.6/en-US/text/swriter/01/04120222.html
[3] start with outline level 1, continue with outline 1 or outline level 2.
With outline level 2, all subsequent headings have an outline level of -1, 0,
or +1. In other words, no jumps or gaps in outline levels, each heading is
preceded or followed by another heading that has the same outline level, or is
one greater or one lesser.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153975] Win11 BSOD when I click LibreOffice "Help" (PAGE_FAULT_IN_NONPAGED_AREA)
https://bugs.documentfoundation.org/show_bug.cgi?id=153975 --- Comment #21 from Frank Moore --- (In reply to Stéphane Guillou (stragu) from comment #20) > Yes, please do the following: > - save a HTML file to somewhere on your home directory > - open that HTML file by pasting its location into Opera, for example: > > file:///C:/Users/frank/Downloads/test.html > > If you get a BSOD, we can confirm that this is not our bug. > Would be worth checking if other browsers give you the same issue, and if > not, changing your default browser. BINGO! BSOD! Strange that same install, same browser, same OS on notebook does not have a problem. Thanks very much for all this help. Sorry to have wasted your time. Frank. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153018] The entire document loses formatting done when I use the clone formatting tool
https://bugs.documentfoundation.org/show_bug.cgi?id=153018 Stéphane Guillou (stragu) changed: What|Removed |Added Whiteboard| QA:needsComment| Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #1 from Stéphane Guillou (stragu) --- Thank you for the report, Jose. The issue with tables is already reported in bug 126008. Regarding the lists, can you please attach a test document a give us steps to reproduce the issue? Also, please make sure you test on a recent version (7.4.6 was released recently). Thank you! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153371] Spelling tool causes crash and ANR message on windows 11 and high CPU usage
https://bugs.documentfoundation.org/show_bug.cgi?id=153371 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |NEEDINFO --- Comment #3 from Stéphane Guillou (stragu) --- Thank you for the report, Charlie. - Can you please attach here an example document for us to test? - Please also try version 7.5.1.2 and see if it resolves your issue. Thank you! -- You are receiving this mail because: You are the assignee for the bug.
GSoC 2023 - Project: Quickly insert brackets
Hi LibreOffice Community, My name is Bayram Çiçek. I have a bachelor's degree in Computer Science and I was a GSoC participant for LibreOffice in 2021. My previous GSoC project was '100 paper cuts' - which is a UI/UX-related project. This year, I'd like to apply for a project that is -also- related to UI/UX. The project I'm interested in is: + Project Name: *Quickly insert brackets* + Enhancement request on Bugzilla: https://bugs.documentfoundation.org/show_bug.cgi?id=151710 + Size: 175 hours + Difficulty: Easy(?) + Potential mentors: Andreas Heinisch, Heiko Tietze Also, I want to continue to work on LibreOffice development after GSoC. About me: + Website: bayramcicek.com.tr/ + LinkedIn: linkedin.com/in/bayramcicek/ + Github: github.com/bayramcicek + IRC/Telegram: @bayramcicek + GSoC'21 final report (100 Paper Cuts): https://bayramcicek.com.tr/libreoffice-dev/2021/08/23/final-report-gsoc.html Thanks. -- Regards, Bayram Çiçek
[Libreoffice-bugs] [Bug 150414] Formatting issue when linking to external data
https://bugs.documentfoundation.org/show_bug.cgi?id=150414 Ben changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #5 from Ben --- Hi, I want to confirm this. Even though I think this is a feature not a bug. I would like to highlight that the informations about how styling is handled, are really badly documented. E.g. I try to import a "simple" html table. But € signs do not lead to a currency formatting. The HTML style tag seems to be ignored too. I guess that there are possibilities for tagging or some "hacks" for displaying. But where to find? I would be very graceful for Tips and Tricks. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153601] Crash when saving a document with gpg-key encryption ( EXCEPTION_ACCESS_VIOLATION_READ )
https://bugs.documentfoundation.org/show_bug.cgi?id=153601 Stéphane Guillou (stragu) changed: What|Removed |Added Summary|Can't save a document with |Crash when saving a |gpg-key encryption anymore |document with gpg-key |(Crash-ID: |encryption ( |11aa9d0d-6795-42a7-bb41-9a5 |EXCEPTION_ACCESS_VIOLATION_ |6574fe192) |READ ) CC||stephane.guillou@libreoffic ||e.org Crash report or|11aa9d0d-6795-42a7-bb41-9a5 |static struct crash signature|6574fe192 |com::sun::star::util::DateT ||ime `anonymous ||namespace'::convertUnixTime ||ToDateTime(__int64) Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #9 from Stéphane Guillou (stragu) --- I installed Gpg4win (which bundles Kleopatra) from https://www.gpg4win.org/get-gpg4win.html Then created a keypair with it, then opened LO and saved with encryption, and I could see and use the key successfully. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d887b6a6fa2a572f48498839c5a68791c3196634 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: threaded 7.4.5.1 also worked as expected. Regarding this type of "EXCEPTION_ACCESS_VIOLATION_READ" issue, maybe some troubleshooting like https://windowsreport.com/exception-access-violation-windows-10/ could help? Wondering if the issue is not necessarily on our end. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107450] [META] Cell and sheet protection bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107450 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||151752 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151752 [Bug 151752] Calc: Crash after copy and paste all unprotected cells -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151752] Calc: Crash after copy and paste all unprotected cells
https://bugs.documentfoundation.org/show_bug.cgi?id=151752 Stéphane Guillou (stragu) changed: What|Removed |Added Severity|normal |critical CC||stephane.guillou@libreoffic ||e.org Blocks||107450 Crash report or|f4d27ff3-9520-48c5-a9df-f98 |ScDocument::HasClipFiltered crash signature|c57e02a51 |Rows() --- Comment #5 from Stéphane Guillou (stragu) --- Rainer's crash report: https://crashreport.libreoffice.org/stats/crash_details/f4d27ff3-9520-48c5-a9df-f98c57e02a51 In LO 7.6, it hangs at step 4 (copying step), with high CPU usage and a loop of: warn:legacy.osl:63279:63279:sc/source/core/data/document.cxx:4240: Wrong sheet number Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107450 [Bug 107450] [META] Cell and sheet protection bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153840] [Calc] Copying huge(?) data by Ctrl-C caused BSOD in Win11 with hardware acceleration on
https://bugs.documentfoundation.org/show_bug.cgi?id=153840 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3975 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153975] Win11 BSOD when I click LibreOffice "Help" (PAGE_FAULT_IN_NONPAGED_AREA)
https://bugs.documentfoundation.org/show_bug.cgi?id=153975 Stéphane Guillou (stragu) changed: What|Removed |Added Keywords||haveBacktrace See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||0774, ||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3840 Summary|Win11 BSOD when I click |Win11 BSOD when I click |LibreOffice "Help" |LibreOffice "Help" ||(PAGE_FAULT_IN_NONPAGED_ARE ||A) --- Comment #20 from Stéphane Guillou (stragu) --- Yes, please do the following: - save a HTML file to somewhere on your home directory - open that HTML file by pasting its location into Opera, for example: file:///C:/Users/frank/Downloads/test.html If you get a BSOD, we can confirm that this is not our bug. Would be worth checking if other browsers give you the same issue, and if not, changing your default browser. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100774] BSOD Page_Fault_in_nonpaged_area
https://bugs.documentfoundation.org/show_bug.cgi?id=100774 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3975 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154137] Two new functions please: NOW.NV & TODAY.NV.
https://bugs.documentfoundation.org/show_bug.cgi?id=154137 --- Comment #12 from Eike Rathke --- (In reply to Alexander Van den Panhuysen from comment #11) > When is that going to happen then? Whenever needed or as a side effect when an expression is recalculated that happens to also contain RAND.NV(), like IF(TODAY()>A1;RAND.NV()) where A1 contains a date smaller than today the RAND.NV() is still recalculated on every sheet content change. > It brings me to the question: "What is the purpose of the existing functions > NOW() and TODAY() in a Calc sheet as the resulted values changes al the > time?" Obviously with TODAY() one can calculate the current days since a given date or until a given date or determine a calendar date. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153975] Win11 BSOD when I click LibreOffice "Help"
https://bugs.documentfoundation.org/show_bug.cgi?id=153975 --- Comment #19 from Frank Moore --- (In reply to Stéphane Guillou (stragu) from comment #12) > Thanks Frank. > > Can you please run !analyze -v on one of those dumps, as suggested, and > attach the result of the analysis here? > > More info on creating stacktraces and dealing with dumps here: > https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg Stéphane: I just attached the dump analysis as requested. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153975] Win11 BSOD when I click LibreOffice "Help"
https://bugs.documentfoundation.org/show_bug.cgi?id=153975 --- Comment #18 from Frank Moore --- Created attachment 185919 --> https://bugs.documentfoundation.org/attachment.cgi?id=185919=edit Result of running debug with verbose parameter Requested by analyst -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154146] Calc crash when you leave the comment
https://bugs.documentfoundation.org/show_bug.cgi?id=154146 --- Comment #4 from Stéphane Guillou (stragu) --- *** This bug has been marked as a duplicate of bug 154050 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154153] [WRITER] [EDITING] a random copy-paste debug report with many html tables make Writer crashe after pasting it in a new file (autosave process is accused)
https://bugs.documentfoundation.org/show_bug.cgi?id=154153 loic_dup...@hotmail.com changed: What|Removed |Added CC||loic_dup...@hotmail.com --- Comment #2 from loic_dup...@hotmail.com --- There is no crash report generated. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154153] [WRITER] [EDITING] a random copy-paste debug report with many html tables make Writer crashe after pasting it in a new file (autosave process is accused)
https://bugs.documentfoundation.org/show_bug.cgi?id=154153 --- Comment #1 from loic_dup...@hotmail.com --- Created attachment 185918 --> https://bugs.documentfoundation.org/attachment.cgi?id=185918=edit The "debug report" from BetterBird, that you can copy-past to reproduce the bug The file is redacted, but contains all tables generated by BetterBird debug page and "copy to clipboard" button. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154153] New: [WRITER] [EDITING] a random copy-paste debug report with many html tables make Writer crashe after pasting it in a new file (autosave process is accused)
https://bugs.documentfoundation.org/show_bug.cgi?id=154153 Bug ID: 154153 Summary: [WRITER] [EDITING] a random copy-paste debug report with many html tables make Writer crashe after pasting it in a new file (autosave process is accused) Product: LibreOffice Version: 7.3.2.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: loic_dup...@hotmail.com Description: BetterBird (ThunderBird fork) generate debug report, and allow to copy-paste it. When I copy paste it in a new file AND SAVE IT it's OK. But when I copy paste it and WAIT a while, it crash, and doesn't have managed auto-save. ...I think there is a problem with autosave with a file of this complexity. After crash, reopening Writer shows me that "there is a document to restore", but restored doc is blank. Steps to Reproduce: 1. Create a new Writer file, and change "View" to "Web" (not "page") for easier view. 2. Open the attached file. 3. Copy paste what is inside the attachement in your new created file. 4. Wait for autosave... It should crash. Actual Results: Something make crash Writer (I think it's the autosave) Expected Results: Well, Writer shouldn't crash! :-/ Reproducible: Always User Profile Reset: No Additional Info: I changed the "time before autosave"... And I crashed sooner. I strongly believe it's autosave that cause this, but I don't have proof. On the other hand, if you save it, it's OK. And if you save it and had "small changes", it's still ok. To reproduce the bug, you should copy-past the full document, and wait. For BetterBird users, to create a report on your own, use the BetterBird report menu in : "BetterBird > Help > More debug info > (it opens the debug page) > copy the content to clipboard". About Libre office : Version: 7.3.2.2 (x64) / LibreOffice Community Build ID: 49f2b1bff42cfccbd8f788c8dc32c1c309559be0 CPU threads: 24; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win Locale: fr-FR (fr_FR); UI: fr-FR Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 95433] EDITING autocorrect option "Apply styles" causes Default Style paragraphs to change to "Text Body" paragraph style while typing
https://bugs.documentfoundation.org/show_bug.cgi?id=95433 --- Comment #14 from Jeppe Bundsgaard --- Bug/undocumented feature is still there in Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 8; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: da-DK (da_DK.UTF-8); UI: da-DK Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153975] Win11 BSOD when I click LibreOffice "Help"
https://bugs.documentfoundation.org/show_bug.cgi?id=153975 --- Comment #17 from Frank Moore --- Opening Help directly in my browser as you suggest yields an immediate BSOD "Page Fault...", just as before. My (desktop) install uses LibreOffice_7.5.1_Win_x86-64.msi and LibreOffice_7.5.1_Win_x86-64_helppack_en-US.msi, under Windows 11 Pro. It is curious that I have a notebook, also running Windows 11 Pro, with the same install of LO as above, and LOHelp works fine, just as intended. My default browser, BTW, is Opera. I repeat, LO itself works fine on both my machines; only Help gives me BSOD, and only on my desktop PC. Anything else I can try? Thanks. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153800] Calc sheet tab drag-and-drop target area has shifted vertically (kf5-only)
https://bugs.documentfoundation.org/show_bug.cgi?id=153800 Stéphane Guillou (stragu) changed: What|Removed |Added OS|All |Linux (All) Version|7.6.0.0 alpha0+ Master |7.5.1.2 release Regression By||Jan-Marek Glogowski Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Summary|Unable to drag and drop |Calc sheet tab |sheet tabs in Calc |drag-and-drop target area |(kf5-only, using 7.6|has shifted vertically |master) |(kf5-only) Keywords|possibleRegression |bibisected, bisected, ||regression Whiteboard| QA:needsComment| Blocks||113113 CC||glo...@fbihome.de, ||stephane.guillou@libreoffic ||e.org --- Comment #1 from Stéphane Guillou (stragu) --- Reproduced in: Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 082d009b6a156faa74c9966b0dffc5fa6ce22287 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Not in: Version: 7.4.6.2 / LibreOffice Community Build ID: 5b1f5509c2decdade7fda905e3e1429a67acd63d CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded One has to drag and drop *below* the tabs for it to work. I noticed that because dragging over the tabs makes the sheet scroll down. Heiko had noticed the same thing in https://bugs.documentfoundation.org/show_bug.cgi?id=136901#c5 Same root cause as bug 153458, introduced by: commit afc828b9833b7a612369e95606ba56d41ef2c369 author Jan-Marek Glogowski Sat May 28 23:47:21 2022 +0200 committer Jan-Marek Glogowski Tue Jun 21 17:26:06 2022 +0200 treeb60ec391ff6f93f85eb4f88d756c2f70b79b674c parent dbaf5f6fad2ec10f69cf46f9cb697b8760c2a01f VCL expect correct frame size for native menubars Reviewed-on: https://gerrit.libreoffice.org/c/core/+/135082 Jan-Marek, can you please have a look? Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=113113 [Bug 113113] [META] Sheet tabs bar bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113113] [META] Sheet tabs bar bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=113113 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||153800 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153800 [Bug 153800] Calc sheet tab drag-and-drop target area has shifted vertically (kf5-only) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151833] IMAGE SIZE: Freeze/hang after changing height to 75% relative ("keep ratio" checked
https://bugs.documentfoundation.org/show_bug.cgi?id=151833 Telesto changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||3633 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-23.05' - editeng/inc editeng/source include/editeng include/svx sd/qa sd/source solenv/clang-format svx/source
editeng/inc/outleeng.hxx |5 +
editeng/source/editeng/impedit3.cxx | 20
editeng/source/outliner/outleeng.cxx | 12 +++-
editeng/source/outliner/outlin2.cxx |2 +-
editeng/source/outliner/outliner.cxx |2 +-
editeng/source/outliner/outlvw.cxx|2 +-
include/editeng/outliner.hxx |4
include/svx/compatflags.hxx |1 +
include/svx/svdoutl.hxx |5 +
sd/qa/unit/data/odp/tdf148966-withflag.odp|binary
sd/qa/unit/data/odp/tdf148966-withoutflag.odp |binary
sd/qa/unit/data/pptx/tdf148966.pptx |binary
sd/qa/unit/layout-tests.cxx | 26 ++
sd/source/ui/docshell/docshel4.cxx|3 +++
solenv/clang-format/excludelist |2 +-
svx/source/svdraw/svdmodel.cxx| 17 +
svx/source/svdraw/svdoutl.cxx | 12
17 files changed, 108 insertions(+), 5 deletions(-)
New commits:
commit 3130211151c8a3596f1834a5297692a96458b368
Author: Sarper Akdemir
AuthorDate: Tue Feb 21 02:34:33 2023 +0300
Commit: Andras Timar
CommitDate: Sun Mar 12 21:43:48 2023 +
tdf#148966: pptx: workaround for multiline fields followed by linebreaks
In Impress after fields that span multiple lines, a
linebreak is already forced. (PowerPoint doesn't have such
behaviour)
Therefore if the imported pptx file has a line break after
the multiline field - Impress ends up displaying an extra
line break.
This patch implements ignoring of a linebreak that follows
after a multiline field during paint (when not in EditMode),
using a compatibility flag. (IgnoreBreakAfterMultilineField)
Change-Id: I1e6772424cc0eead06b53d104b06820038a81ea1
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147408
Tested-by: Jenkins
Reviewed-by: Miklos Vajna
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/148334
Reviewed-by: Andras Timar
Tested-by: Andras Timar
diff --git a/editeng/source/outliner/outleeng.hxx b/editeng/inc/outleeng.hxx
similarity index 96%
rename from editeng/source/outliner/outleeng.hxx
rename to editeng/inc/outleeng.hxx
index d19b54eba06a..449b5ca44ce8 100644
--- a/editeng/source/outliner/outleeng.hxx
+++ b/editeng/inc/outleeng.hxx
@@ -21,6 +21,8 @@
#include
#include
+enum class SdrCompatibilityFlag;
+
typedef std::vector NotifyList;
class OutlinerEditEng : public EditEngine
@@ -75,6 +77,9 @@ public:
virtual tools::Rectangle GetBulletArea( sal_Int32 nPara ) override;
+/// @returns state of the SdrCompatibilityFlag
+std::optional GetCompatFlag(SdrCompatibilityFlag eFlag) const;
+
virtual voidSetParaAttribs( sal_Int32 nPara, const SfxItemSet&
rSet ) override;
// belongs into class Outliner, move there before incompatible update!
diff --git a/editeng/source/editeng/impedit3.cxx
b/editeng/source/editeng/impedit3.cxx
index 3191b7a874e7..376d1df7ad13 100644
--- a/editeng/source/editeng/impedit3.cxx
+++ b/editeng/source/editeng/impedit3.cxx
@@ -24,6 +24,7 @@
#include
#include
+#include
#include
#include
#include
@@ -44,11 +45,14 @@
#include
#include
#include
+#include
#include
#include
#include
+#include
+
#include
#include
@@ -3606,6 +3610,22 @@ void ImpEditEngine::Paint( OutputDevice& rOutDev,
tools::Rectangle aClipRect, Po
nTextStart = *curIt;
nTextLen = nTextLen - nTextStart;
bParsingFields = false;
+
+if (nLine + 1 < nLines)
+{
+// tdf#148966 don't paint the
line break following a
+// multiline field based on a
compat flag
+OutlinerEditEng* pOutlEditEng{
dynamic_cast(pEditEngine) };
+if (pOutlEditEng
+&&
pOutlEditEng->GetCompatFlag(SdrCompatibilityFlag::IgnoreBreakAfterMultilineField)
+ .value_or(false))
+{
+int nStartNextLine =
pPortion->GetLines()[nLine + 1].GetStartPortion();
+const TextPortion&
rNextTextPortion = pPortion->GetTextPortions()[nStartNextLine];
+if
(rNextTextPortion.GetKind() == PortionKind::LINEBREAK)
+++nLine; //ignore the
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-23.05' - include/svx sc/source sd/source svx/source sw/source
include/svx/compatflags.hxx | 18
include/svx/svdmodel.hxx| 15 +---
sc/source/ui/docshell/docsh.cxx | 14 ++-
sd/source/ui/docshell/docshel4.cxx |9 +-
svx/source/customshapes/EnhancedCustomShapeFontWork.cxx |4 -
svx/source/svdraw/svdmodel.cxx | 59
svx/source/svdraw/svdoedge.cxx |5 -
svx/source/svdraw/svdotextdecomposition.cxx |5 -
sw/source/uibase/app/docshini.cxx |7 +
9 files changed, 82 insertions(+), 54 deletions(-)
New commits:
commit 19622bf3749531bb66cd190c11ebfdca70b034db
Author: Sarper Akdemir
AuthorDate: Tue Feb 21 02:33:01 2023 +0300
Commit: Andras Timar
CommitDate: Sun Mar 12 21:43:32 2023 +
related tdf#148966: rework sdr compatibility flags
Rework access/set methods for sdr compatibility flags so it
is possible to address a compatibility flag without directly
interfacing with SdrModel.
(preliminary work for exposing compatibility flags to
editeng)
Change-Id: I2fab219f9e125151916228300be2d9d88156d8a6
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147407
Tested-by: Jenkins
Reviewed-by: Miklos Vajna
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/148315
Reviewed-by: Andras Timar
Tested-by: Andras Timar
diff --git a/include/svx/compatflags.hxx b/include/svx/compatflags.hxx
new file mode 100644
index ..6a53c756ebd8
--- /dev/null
+++ b/include/svx/compatflags.hxx
@@ -0,0 +1,18 @@
+/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4;
fill-column: 100 -*- */
+/*
+ * This file is part of the LibreOffice project.
+ *
+ * This Source Code Form is subject to the terms of the Mozilla Public
+ * License, v. 2.0. If a copy of the MPL was not distributed with this
+ * file, You can obtain one at http://mozilla.org/MPL/2.0/.
+ */
+
+/// SdrCompatibilityFlags that are implemented in SdrModelImpl
+enum class SdrCompatibilityFlag
+{
+AnchoredTextOverflowLegacy, ///< for tdf#99729
+LegacySingleLineFontwork, ///< for tdf#148000
+ConnectorUseSnapRect, ///< for tdf#149756
+};
+
+/* vim:set shiftwidth=4 softtabstop=4 expandtab cinoptions=b1,g0,N-s
cinkeys+=0=break: */
diff --git a/include/svx/svdmodel.hxx b/include/svx/svdmodel.hxx
index 1617942c848d..d87c9def5893 100644
--- a/include/svx/svdmodel.hxx
+++ b/include/svx/svdmodel.hxx
@@ -77,6 +77,7 @@ class SdrUndoFactory;
class ImageMap;
class TextChain;
enum class CharCompressType;
+enum class SdrCompatibilityFlag;
namespace comphelper
{
class IEmbeddedHelper;
@@ -571,17 +572,9 @@ public:
void SetAddExtLeading( bool bEnabled );
bool IsAddExtLeading() const { return mbAddExtLeading; }
-// tdf#99729 compatibility flag
-void SetAnchoredTextOverflowLegacy(bool bEnabled);
-bool IsAnchoredTextOverflowLegacy() const;
-
-// tdf#148000 compatibility flag
-void SetLegacySingleLineFontwork(bool bEnabled);
-bool IsLegacySingleLineFontwork() const;
-
-// tdf#149756 compatibility flag
-void SetConnectorUseSnapRect(bool bEnabled);
-bool IsConnectorUseSnapRect() const;
+void SetCompatibilityFlag(SdrCompatibilityFlag eFlag, bool bEnabled);
+/// @returns state of the SdrCompatibilityFlag
+bool GetCompatibilityFlag(SdrCompatibilityFlag eFlag) const;
void ReformatAllTextObjects();
diff --git a/sc/source/ui/docshell/docsh.cxx b/sc/source/ui/docshell/docsh.cxx
index 9a5b5968d9ec..f049f3c55b38 100644
--- a/sc/source/ui/docshell/docsh.cxx
+++ b/sc/source/ui/docshell/docsh.cxx
@@ -77,6 +77,7 @@
#include
#include
+#include
#include
#include
@@ -585,13 +586,16 @@ bool ScDocShell::Load( SfxMedium& rMedium )
InitOptions(true);
// If this is an ODF file being loaded, then by default, use legacy
processing
-// for tdf#99729 (if required, it will be overridden in
*::ReadUserDataSequence())
+// (if required, it will be overridden in *::ReadUserDataSequence())
if (IsOwnStorageFormat(rMedium))
{
-if (m_pDocument->GetDrawLayer())
-m_pDocument->GetDrawLayer()->SetAnchoredTextOverflowLegacy(true);
-if (m_pDocument->GetDrawLayer())
-m_pDocument->GetDrawLayer()->SetLegacySingleLineFontwork(true);
//for tdf#148000
+if (ScDrawLayer* pDrawLayer = m_pDocument->GetDrawLayer())
+{
+
pDrawLayer->SetCompatibilityFlag(SdrCompatibilityFlag::AnchoredTextOverflowLegacy,
+ true); // for tdf#99729
+
pDrawLayer->SetCompatibilityFlag(SdrCompatibilityFlag::LegacySingleLineFontwork,
+ true); // for tdf#148000
+}
}
GetUndoManager()->Clear();
diff --git a/sd/source/ui/docshell/docshel4.cxx
b/sd/source/ui/docshell/docshel4.cxx
index
[Libreoffice-bugs] [Bug 108479] [META] Paste special bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108479 Eyal Rozenberg changed: What|Removed |Added Depends on||154152 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154152 [Bug 154152] Paste-Special of plain text as Text, Number or Formula does nothing -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154152] Paste-Special of plain text as Text, Number or Formula does nothing
https://bugs.documentfoundation.org/show_bug.cgi?id=154152 Eyal Rozenberg changed: What|Removed |Added Blocks||108479 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108479 [Bug 108479] [META] Paste special bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154152] New: Paste-Special of plain text as Text, Number or Formula does nothing
https://bugs.documentfoundation.org/show_bug.cgi?id=154152 Bug ID: 154152 Summary: Paste-Special of plain text as Text, Number or Formula does nothing Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com I have a text editor open, and have copied the string "5678". In a new Calc spreasheet, I now try to paste this content in different ways, into some arbitrary cell. Pressing Ctrl+V: Works, I get 5678. Right-click > Paste: Works, I get 5678. Right-click > Paste Special > Unformatted Text : Works, I get 5678. Right-click > Paste Special > Text : Nothing happens! Right-click > Paste Special > Number :Nothing happens! Right-click > Paste Special > Formula : Nothing happens! Seeing this with: Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 4; OS: Linux 6.1; UI render: default; VCL: gtk3 Locale: en-IL (en_IL); UI: en-US Calc: CL threaded and: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ad387d5b984c906505d25685065f710ed55d CPU threads: 4; OS: Linux 6.1; UI render: default; VCL: gtk3 Locale: he-IL (en_IL); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154131] Pasted text like 1E1 or 5E2 treated as scientific format
https://bugs.documentfoundation.org/show_bug.cgi?id=154131 --- Comment #6 from Eyal Rozenberg --- > I insert a large list of text from the clipboard and stumbled over the fact > that content like 1E1 is converted to 10 or 5E2 to 50 When you paste a bunch of text from the clipboard, you get the Text Import dialog, where you decide how you want the pasting to work. Did you click Ok without checking, and are filing this bug about the default options? If not - then... INVALID? Also, I think I agree with Stuart. Excel/Calc users "know" that when that regular paste does all sorts of weird conversions, just like typing into a cell: Scientific Notation, Dates, numbers starting with 0 which lose the 0, and maybe other stuff. We "know" that to get exactly the pasted text, we need to play with the options. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103164] [META] Footnote and Endnote bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103164 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||153804 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153804 [Bug 153804] Footnotes disappear or move in docx file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153804] Footnotes disappear or move in docx file
https://bugs.documentfoundation.org/show_bug.cgi?id=153804 Stéphane Guillou (stragu) changed: What|Removed |Added Status|NEEDINFO|NEW Summary|Footnotes disappeared in|Footnotes disappear or move |writer docx file after 7.5 |in docx file |update | Version|7.5.0.3 release |7.4.6.2 release Keywords||bibisectRequest, ||filter:docx, regression Blocks||103164 Hardware|Other |All OS|macOS (All) |All --- Comment #6 from Stéphane Guillou (stragu) --- Apologies, I did something wrong in my testing in comment 5. I do see the reshuffling of footnotes, already visible in 7.4: Version: 7.4.6.2 / LibreOffice Community Build ID: 5b1f5509c2decdade7fda905e3e1429a67acd63d CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded but not in 7.3 (each footnote has one paragraph of text): Version: 7.3.7.2 / LibreOffice Community Build ID: e114eadc50a9ff8d8c8a0567d6da8f454beeb84f CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded The issue is still reproducible in a master build from today, and it is similar to bug 152203 and bug 153255 but started at a different point. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103164 [Bug 103164] [META] Footnote and Endnote bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153804] Footnotes disappeared in writer docx file after 7.5 update
https://bugs.documentfoundation.org/show_bug.cgi?id=153804 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #5 from Stéphane Guillou (stragu) --- alidostnuman, could could you please let us know: - which version did you have before updating to 7.5.0.3? - what exactly are the steps to reproduce, starting from the document you shared? I opened the document in various versions from 6.0.0.3 to 7.5.1.2 and always see the same: - footnote 1 with four paragraphs of text - footnotes 2, 3, 4 and 5 with no text at all -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153109] Use all_of, any_of or none_of from STD instead of looping to check a condition over a range
https://bugs.documentfoundation.org/show_bug.cgi?id=153109 Baole Fang changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |baole.f...@gmail.com |desktop.org | Status|NEW |ASSIGNED --- Comment #2 from Baole Fang --- Hi, I'd like to take a look at this. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153816] Removing table removes only it's data and have to be repeated
https://bugs.documentfoundation.org/show_bug.cgi?id=153816 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3818 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153818] Removed tables reappear after loading of document
https://bugs.documentfoundation.org/show_bug.cgi?id=153818 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3816 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153826] PROBLEM W/ CREATED FIELD
https://bugs.documentfoundation.org/show_bug.cgi?id=153826 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |NEEDINFO Version|unspecified |7.4.5.1 release Ever confirmed|0 |1 Whiteboard| QA:needsComment| --- Comment #1 from Stéphane Guillou (stragu) --- I couldn't reproduce with a new file in: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d887b6a6fa2a572f48498839c5a68791c3196634 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded nor on: Version: 7.4.6.2 / LibreOffice Community Build ID: 5b1f5509c2decdade7fda905e3e1429a67acd63d CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded nor on Windows 10: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d887b6a6fa2a572f48498839c5a68791c3196634 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: threaded - Are you able to attach the file in question, removing any sensitive data? - Do you know with what version of LibreOffice was the file created? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146800] Linked libraries don't show source path in Macro Organizer
https://bugs.documentfoundation.org/show_bug.cgi?id=146800 --- Comment #3 from e...@helpidea.net --- May be a valid solution. When develop a library, obviously it is important to understand if you are coding e saving a user library or a linked library. Thank you -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99671] [META] Gallery bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=99671 Bug 99671 depends on bug 132847, which changed state. Bug 132847 Summary: Not all shapes in gallery shown in Detailed View rendered automatically https://bugs.documentfoundation.org/show_bug.cgi?id=132847 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102495] [META] KDE VCL backend bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102495 Bug 102495 depends on bug 147833, which changed state. Bug 147833 Summary: Clone Formatting added to clicked row +1 row using KDE wayland https://bugs.documentfoundation.org/show_bug.cgi?id=147833 What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100156] [META] Wayland-related bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=100156 Bug 100156 depends on bug 147833, which changed state. Bug 147833 Summary: Clone Formatting added to clicked row +1 row using KDE wayland https://bugs.documentfoundation.org/show_bug.cgi?id=147833 What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147833] Clone Formatting added to clicked row +1 row using KDE wayland
https://bugs.documentfoundation.org/show_bug.cgi?id=147833 robby.engelm...@r-engelmann.de changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- --- Comment #5 from robby.engelm...@r-engelmann.de --- The offset during clone formating may be solved. However, it is hard to evaluate, because the cursor is invisible during using the tool. Version informations: Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: 50(Build:2) CPU threads: 8; OS: Linux 6.2; UI render: default; VCL: kf5 (cairo+wayland) Locale: en-US (en_US.UTF-8); UI: en-US Calc: CL threaded Operating System: openSUSE Tumbleweed 20230311 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.8 Kernel Version: 6.2.2-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics Manufacturer: TUXEDO Product Name: TUXEDO System Version: Not Applicable -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: vcl/source
vcl/source/gdi/metaact.cxx |2 ++
1 file changed, 2 insertions(+)
New commits:
commit 668c44e841a10cec8932a446a941e6d7c386bf3b
Author: Caolán McNamara
AuthorDate: Sat Mar 11 21:13:17 2023 +
Commit: Caolán McNamara
CommitDate: Sun Mar 12 20:33:21 2023 +
ofz#56928 Integer-overflow
Change-Id: Ia20a42e16b50ab320e44405e60403c1d3b971bb5
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/148692
Tested-by: Jenkins
Reviewed-by: Caolán McNamara
diff --git a/vcl/source/gdi/metaact.cxx b/vcl/source/gdi/metaact.cxx
index 1c7c320518ab..71dbe5daa4e4 100644
--- a/vcl/source/gdi/metaact.cxx
+++ b/vcl/source/gdi/metaact.cxx
@@ -1483,6 +1483,8 @@ MetaMoveClipRegionAction::MetaMoveClipRegionAction(
tools::Long nHorzMove, tools
void MetaMoveClipRegionAction::Execute( OutputDevice* pOut )
{
+if (!AllowY(pOut->LogicToPixel(Point(mnHorzMove, mnVertMove)).Y()))
+return;
pOut->MoveClipRegion( mnHorzMove, mnVertMove );
}
[Libreoffice-bugs] [Bug 85184] [META] Color picker toolbar, dialog and sidebar drop-down widget bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=85184 V Stuart Foote changed: What|Removed |Added Depends on||93813 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=93813 [Bug 93813] Integration of a color picker/pipette dropper control into the sidebar and color picker dialog -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 93813] Integration of a color picker/pipette dropper control into the sidebar and color picker dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=93813 V Stuart Foote changed: What|Removed |Added Blocks||85184 Summary|Integration of a color |Integration of a color |picker/pipette control into |picker/pipette dropper |the sidebar and color |control into the sidebar |picker dialog |and color picker dialog CC||vsfo...@libreoffice.org Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=85184 [Bug 85184] [META] Color picker toolbar, dialog and sidebar drop-down widget bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 93813] Integration of a color picker/pipette control into the sidebar and color picker dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=93813 V Stuart Foote changed: What|Removed |Added CC||maicoleduardofigueroa@gmail ||.com --- Comment #10 from V Stuart Foote --- *** Bug 154148 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 154148] the dropper function is badly needed
https://bugs.documentfoundation.org/show_bug.cgi?id=154148 V Stuart Foote changed: What|Removed |Added Resolution|--- |DUPLICATE CC||vsfo...@libreoffice.org Status|UNCONFIRMED |RESOLVED --- Comment #2 from V Stuart Foote --- *** This bug has been marked as a duplicate of bug 93813 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153903] "Category and Number" and "Caption Text" in Cross-reference variable dialog are limited to fixed structural relations
https://bugs.documentfoundation.org/show_bug.cgi?id=153903 Eyal Rozenberg changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #2 from Eyal Rozenberg --- I'd say it's a bug to be fixed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-23.05' - sd/source
sd/source/ui/app/sddll.cxx | 24 ++--
1 file changed, 18 insertions(+), 6 deletions(-)
New commits:
commit 55e82ed855c18e5e6a830e3a80160c6a8e0c8a6a
Author: Henry Castro
AuthorDate: Wed Feb 15 11:25:19 2023 -0400
Commit: Andras Timar
CommitDate: Sun Mar 12 20:11:32 2023 +
sd: lok: only register supported views
The Presentation ViewShells:
SlideSorter,
Outline,
Presentation
They are not supported in tiled rendering case,
so switch to default view.
Signed-off-by: Henry Castro
Change-Id: I33b255e0ca530734af6490d14fe48a2512272afc
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147095
Reviewed-by: Andras Timar
Tested-by: Andras Timar
diff --git a/sd/source/ui/app/sddll.cxx b/sd/source/ui/app/sddll.cxx
index c195869b790e..b4734310a39b 100644
--- a/sd/source/ui/app/sddll.cxx
+++ b/sd/source/ui/app/sddll.cxx
@@ -91,12 +91,24 @@ void SdDLL::RegisterFactorys()
{
::sd::ImpressViewShellBase::RegisterFactory (
::sd::IMPRESS_FACTORY_ID);
-::sd::SlideSorterViewShellBase::RegisterFactory (
-::sd::SLIDE_SORTER_FACTORY_ID);
-::sd::OutlineViewShellBase::RegisterFactory (
-::sd::OUTLINE_FACTORY_ID);
-::sd::PresentationViewShellBase::RegisterFactory (
-::sd::PRESENTATION_FACTORY_ID);
+if (comphelper::LibreOfficeKit::isActive())
+{
+::sd::ImpressViewShellBase::RegisterFactory (
+::sd::SLIDE_SORTER_FACTORY_ID);
+::sd::ImpressViewShellBase::RegisterFactory (
+::sd::OUTLINE_FACTORY_ID);
+::sd::ImpressViewShellBase::RegisterFactory (
+::sd::PRESENTATION_FACTORY_ID);
+}
+else
+{
+::sd::SlideSorterViewShellBase::RegisterFactory (
+::sd::SLIDE_SORTER_FACTORY_ID);
+::sd::OutlineViewShellBase::RegisterFactory (
+::sd::OUTLINE_FACTORY_ID);
+::sd::PresentationViewShellBase::RegisterFactory (
+::sd::PRESENTATION_FACTORY_ID);
+}
}
if (!utl::ConfigManager::IsFuzzing() && SvtModuleOptions().IsDraw())
{
[Libreoffice-bugs] [Bug 48459] FORMATTING - proposal for in-line headings, (run-in, inset headings)
https://bugs.documentfoundation.org/show_bug.cgi?id=48459 --- Comment #17 from Eyal Rozenberg --- What is this bug about now? * In-line paragraphs - dupe of 46023. * Allowing character styles in ToC - interesting prospect, but then amend the title accordingly. Would also need to discuss if a document could having its "Heading N" style switched from PS to CS and back. * Two-frame structures which look like a full paragraph with a run-in heading Please decide and clarify using the bug title. In particular, whoever marked this as NEW - which suggestion did you confirm? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153904] [ENHANCEMENT] Allow for inline (= run-in) paragraph styles
https://bugs.documentfoundation.org/show_bug.cgi?id=153904 --- Comment #5 from Eyal Rozenberg --- Finally, I believe this is a dupe of 46023, since it suggests a specific kind of implementation rather than a different feature. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 46023] [RFE, FORMATTING] Allow creation of inline paragraphs (where next paragraph continues on the same line, not on new line)
https://bugs.documentfoundation.org/show_bug.cgi?id=46023 --- Comment #13 from Eyal Rozenberg --- (In reply to Buovjaga from comment #12) I have elaborated on that kind of arguments in the discussion of: https://bugs.documentfoundation.org/show_bug.cgi?id=153904 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153904] [ENHANCEMENT] Allow for inline (= run-in) paragraph styles
https://bugs.documentfoundation.org/show_bug.cgi?id=153904 Eyal Rozenberg changed: What|Removed |Added CC||eyalr...@gmx.com --- Comment #4 from Eyal Rozenberg --- (In reply to ajlittoz from comment #0) First let me ask about the motivation. I can see two kinds: 1. Limitation of the text adopted for indices/tables/bookmarks; 2. Implementation of inline lists (and this would require some more description which you have not provided) Is there something else? Now, about how such paragraphs would work: > - Line break is suppressed. > - Space below of run-in style is ignored Don't you mean constrained to 0? > - Bottom border is suppressed (though it is expected users won't request > borders) How is that expected? Wouldn't the user expect a border below the part of the inline paragraph on the bottom line? Or perhaps, for there to be a border if continuing paragraph doesn't have one? Also, what about different line spacing values for this paragraph and the next one? Or multiple inline paragraphs on the same line? > - In case of justification, last line justification is suppressed to revert > to left (adapt for RTL) What if the inline paragraph is RTL, and the next paragraph is LTR? For that matter, what if you have inline paragraphs on the same line with Left, Center and Right alignment? > - Left indent is used as usual because it defines the starting position of > the line No it doesn't, at least not necessarily. Suppose I have two LTR inline-paragraphs within the same line. The first one is right-aligned, the second one is left-aligned. And, for that matter, what happens with the overlaps? How do you order overflow from these two paragraphs on the next line? ... and what do you do when you have 3, or 4, inline paragraphs on the same line? > - Right indent is pointless because we know we have a partial line (A run-in > paragraph is allowed to span several lines; only the last line receives > special handling). As discussed above, not true. > - By definition of run-in, the base line is the same for the run-in > paragraph and the subsequent one. What if the "run-in" is in English, with baseline at the bottom, while the next paragraph is in Devangari, with baseline at the top? > The new paragraph text is laid out immediately after the end of the run-in > paragraph at a distance defined by the "spacing" parameter of the option. > Start of paragraph actions are suppressed. > > - Spacing above is suppressed. > - Top border is suppressed. That would be unexpected by the user. If they specified spacing above or a border, they expect to have them. This is not like the run-in paragraph's style, for which you can assume the user knows in advance not all properties are to be respected. > - First line indent is ignored (because text is considered a continuation of > run-in para). > - Left indent is ignored on first line but becomes active for second and > subsequent lines. > - Right indent is used as usual. As discussed above, you can't assume where on the first line the run-in paragraph is to be placed. > - First line alignment is honoured just the same as the other lines > Note: for the purpose of alignment, run-in paragraph last line can be > regarded as a mini-frame and its bounding box passed as such to the layout > algorithm if possible. > Such a run-in paragraph style keeps all the other properties of paragraph > styles So, here's the thing. Actually, what you describe necessarily must loses essentially all properties of a paragraph: * Spacing (and probably indentation) * Border * Direction * Alignment * (Tabs - probably) * Drop Caps - by your suggestion There's almost nothing remaining that's not character properties, except perhaps list item association, and even that's not trivial because of positioning and spacing. With this in mind, I don't think these can properly be described as inline paragraphs. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127452] Only first sentence of caption in Index
https://bugs.documentfoundation.org/show_bug.cgi?id=127452 Eyal Rozenberg changed: What|Removed |Added CC||eyalr...@gmx.com --- Comment #8 from Eyal Rozenberg --- 1. Why the first sentence? Shouldn't the limitation be more flexible? What if my language doesn't have sentences? What if I need two sentences? Or - what if I only want the text up until some other mark, like a space, a hyphen or a colon? 2. Why only captions? Shouldn't this be relevant to other styles, e.g. headings? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153904] [ENHANCEMENT] Allow for inline (= run-in) paragraph styles
https://bugs.documentfoundation.org/show_bug.cgi?id=153904 --- Comment #3 from Eyal Rozenberg --- (In reply to Regina Henschel from comment #1) Note that in CSS, marking an object with display: inline makes it not-a-block-object, so that all those style aspects regarding block objects don't apply to it. In other words, it's like saying "this paragraph is not really a paragraph, it's basically like an HTML span or other inline elements.. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153899] Clone format of unmerged cells breaks up merging, applies to first unmerged cell only
https://bugs.documentfoundation.org/show_bug.cgi?id=153899 Eyal Rozenberg changed: What|Removed |Added Summary|Clone format does not work |Clone format of unmerged |with joined cells |cells breaks up merging, ||applies to first unmerged ||cell only -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153899] Clone format of unmerged cells breaks up merging, applies to first unmerged cell only
https://bugs.documentfoundation.org/show_bug.cgi?id=153899 Eyal Rozenberg changed: What|Removed |Added Summary|Clone format does not work |Clone format of unmerged |with joined cells |cells breaks up merging, ||applies to first unmerged ||cell only -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 153899] Clone format does not work with joined cells
https://bugs.documentfoundation.org/show_bug.cgi?id=153899 Eyal Rozenberg changed: What|Removed |Added CC||eyalr...@gmx.com, ||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153899] Clone format does not work with joined cells
https://bugs.documentfoundation.org/show_bug.cgi?id=153899 Eyal Rozenberg changed: What|Removed |Added CC||eyalr...@gmx.com, ||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 153899] Clone format does not work with joined cells
https://bugs.documentfoundation.org/show_bug.cgi?id=153899 --- Comment #4 from Eyal Rozenberg --- So, one question here is: Q1: Should "being merged" be considered one of the formatting properties of a cell? * If it should then the clone-formatting also applies the "not merged" property, and see raal's comment #2. * If it should not - then clone-formatting should never merge nor unmerge. Now, even if "being merged" _is_ one of the formatting properties, then we face a second question: Q2: Should the clone-formatting apply to all the separating cells getting unmerged or just to the first? I believe that the answer Q2 is pretty clearly "Apply to all separating cells". I very much doubt any user would want just one unmerged cell to be affected - even if the merging is broken. As for Q1, here my opinion is less well-formed. I tend to see "mergedness" as not an apsect formatting, but a structural aspect, which should not be affected by clone formatting; but I could be convinced otherwise. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151833] IMAGE SIZE: Freeze/hang after changing height to 75% relative ("keep ratio" checked
https://bugs.documentfoundation.org/show_bug.cgi?id=151833 Noel Grandin changed: What|Removed |Added CC||heiko.tietze@documentfounda ||tion.org --- Comment #9 from Noel Grandin --- Bisecting from source shows that the freeze started with commit dd5039ceea319ebfc72a3e032753b22538add12e Author: Heiko Tietze Date: Tue Aug 24 11:14:46 2021 +0200 Resolves tdf#143633 - Image size wrong after disabling relative image width -- You are receiving this mail because: You are the assignee for the bug.
