[Libreoffice-bugs] [Bug 148152] Using a digital pen with LO: Ink drawings / annotations with Stylus, Pen or Finger on Touchscreen or Tablet
https://bugs.documentfoundation.org/show_bug.cgi?id=148152 --- Comment #11 from V Stuart Foote --- *** Bug 153557 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 153557] Feature request: to draw directly in LO Inmpress or Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=153557 V Stuart Foote changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED Severity|normal |enhancement --- Comment #2 from V Stuart Foote --- A good enhancement suggestion, but this was the correct dupe. Sorry for the noise. *** This bug has been marked as a duplicate of bug 148152 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146968] Prototype UI for new Inking feature
https://bugs.documentfoundation.org/show_bug.cgi?id=146968 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||8152 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148152] Using a digital pen with LO: Ink drawings / annotations with Stylus, Pen or Finger on Touchscreen or Tablet
https://bugs.documentfoundation.org/show_bug.cgi?id=148152 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||6968 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153557] Feature request: to draw directly in LO Inmpress or Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=153557 V Stuart Foote changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153557] Feature request: to draw directly in LO Inmpress or Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=153557 V Stuart Foote changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||vsfo...@libreoffice.org --- Comment #1 from V Stuart Foote --- already implemented available at the 7.6.0 release, may not be backported to 7.5.x *** This bug has been marked as a duplicate of bug 153229 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153556] Enhancement Request: Add option to disable dark theme
https://bugs.documentfoundation.org/show_bug.cgi?id=153556 V Stuart Foote changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||vsfo...@libreoffice.org --- Comment #1 from V Stuart Foote --- already implemented available at the 7.6.0 release, may not be backported to 7.5.x *** This bug has been marked as a duplicate of bug 153229 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153555] LibreOffice respects Windows Dark Mode setting over its own Options
https://bugs.documentfoundation.org/show_bug.cgi?id=153555 V Stuart Foote changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||vsfo...@libreoffice.org Resolution|--- |DUPLICATE --- Comment #3 from V Stuart Foote --- already implemented available at the 7.6.0 release, may not be backported to 7.5.x *** This bug has been marked as a duplicate of bug 153229 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153464] If I want to write a list, then the next line is not indented
https://bugs.documentfoundation.org/show_bug.cgi?id=153464 Armin Mohring changed: What|Removed |Added Version|7.4.5.1 release |7.5.0.3 release -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153562] Pasting Selected Range to Sheet as BMP Image, It will be a Chart Image without content.
https://bugs.documentfoundation.org/show_bug.cgi?id=153562 --- Comment #1 from nobu --- Created attachment 185329 --> https://bugs.documentfoundation.org/attachment.cgi?id=185329=edit sample file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153562] New: Pasting Selected Range to Sheet as BMP Image, It will be a Chart Image without content.
https://bugs.documentfoundation.org/show_bug.cgi?id=153562 Bug ID: 153562 Summary: Pasting Selected Range to Sheet as BMP Image, It will be a Chart Image without content. Product: LibreOffice Version: 7.4.3.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tac...@hotmail.co.jp Description: Pasting Selected Range to Sheet as BMP Image, It will be a Chart Image without content. Steps to Reproduce: 1. Open a new Calc. 2. Create a Chart. 3. Select the range including the chart. 4. Move the cursor somewhere. 5. Paste Image in BMP using PasteDropdownIcon. Actual Results: 6. The image of the chart without content is pasted. Expected Results: 6. The image should be the same as the copy source. Reproducible: Always User Profile Reset: No Additional Info: There is a similar Bug in PNG. Not Reproduced with before Version 7.1.8.1 64bit, OS:Windows10 64bit Not Reproduced with before Version 7.4.0.0 alpha1 64bit, OS:Windows10 64bit Reproducible with Version 7.4.3.2 64bit, OS:Windows10 64bit Reproducible with Version 7.5.0.3 64bit, OS:Windows10 64bit Reproducible with Version 7.6.0.0 alpha0 64bit, OS:Windows10 64bit -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152605] Change "heading level" to "outline level" in UI and help pages for Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=152605 Dieter changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3549 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153549] Rename Tools > "Chapter Numbering" to "Heading Numbering"
https://bugs.documentfoundation.org/show_bug.cgi?id=153549 Dieter changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2605 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153506] LibreCalc - When copying an existing sheet to a new sheet LibreCalc does not preserve conditional formatting on new sheet. Example provided in description.
https://bugs.documentfoundation.org/show_bug.cgi?id=153506 ady changed: What|Removed |Added Status|REOPENED|NEEDINFO --- Comment #8 from ady --- @ bwilderhoo Perhaps you don't realize that you are replying to a bug report, not to one specific person. You have 2 different persons replying in the bug report you opened. One closed the report, while the other gave you the benefit of the doubt. So, now that you re-opened the report, and with the additional detail I just wrote, please read carefully the complete reply before answering. (In reply to bwilderhoo from comment #7) > I have used this same kind of conditional formatting in Microsoft Excel and > it has worked as I described above. That means that you are assuming that the exact same syntax is used by LO too. This is an understandable assumption, but unfortunately it is not correct. > > relative sheet name references as described above. Note, the bug is in the > merge of rows during the copy sheet function. The original sheet works just > fine with the existing 2 lines using relative row references. New sheets > created as copies from the original should work the same as the original--- > but in this case they do not because of the bug. In comment 5 I asked you to supply a value and in which specific location you would introduce it in order to trigger the problem you see. If you think that more than one value is necessary, please describe them. Alternatively, please attach a new file with the problem already triggered. To be clear, I have the same suspicion as m.a.riosv. Let's see if bwilderhoo can reply with a relevant sample value(s) or equivalent. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153506] LibreCalc - When copying an existing sheet to a new sheet LibreCalc does not preserve conditional formatting on new sheet. Example provided in description.
https://bugs.documentfoundation.org/show_bug.cgi?id=153506 bwilder...@yahoo.com changed: What|Removed |Added Resolution|NOTABUG |--- Status|RESOLVED|REOPENED --- Comment #7 from bwilder...@yahoo.com --- Sorry, but I don't think we are on the same page on this one. I fully understand how conditional formatting works... and the sheet correctly reflects the conditional formats as they need to be. That is, for row 18 the cell value for each month is compared to the $budget.$B23, and for row 19 the cell value for each month is compared to $budget.$B24. In short, there are two distinct rows cells requiring comparison against two distinct budget cells. In short, as a retired computer programmer myself with 40+ years of experience, I believe this remains a bug. At a minimum, the move or copy sheet function should not modify the column and row numbers used in cell references regardless of whether these references are defined within the conditional formats or simply used in the cell value calculations, and regardless of whether or not the absolute or relative column and row references are used. The only change that I would expect during a move or copy of a sheet is the relative sheet name should be changed. That is, any sheet names references should be updated to the 2023. This seems to be working as expected. The reason that absolute row addresses can not be used is because the budget sheet can have additional rows added over time, and this fact requires the automatic update of all row reference is other sheets in order to prevent incorrect cell values from being used. Note, for this particular budget spreadsheet definition, new expenses (i.e. - rows) can be added over time to the budget sheet but no new columns are allowed. Therefore, the other sheets need to use relative row numbers in order to be kept in proper sync with existing values when new rows (i.e. - expenses) are added to the budget. I have used this same kind of conditional formatting in Microsoft Excel and it has worked as I described above. The simplest thing to do is whenever a sheet is copied then make an exact copy the entire sheet contents including conditional formatting, and only update the relative original sheet name references to use the new sheet name. The extra step that is apparently being done to reduce the number of distinct ranges in the conditional formats is very complex logic and prone to difficulties such as described in this bug report. I recommend the keep it simple approach, and just keep the conditional formats in the new sheet as they were in the original sheet-- with the one exception of updating the relative sheet name references as described above. Note, the bug is in the merge of rows during the copy sheet function. The original sheet works just fine with the existing 2 lines using relative row references. New sheets created as copies from the original should work the same as the original--- but in this case they do not because of the bug. Hope this helps to get on the same page. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153075] Mail Merge: HTML Mail with picture is broken
https://bugs.documentfoundation.org/show_bug.cgi?id=153075 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153542] Libreoffice calc 7.5 very slow and unresponsive when zooming in out (wheel mouse) on large spreadsheet unde Debian
https://bugs.documentfoundation.org/show_bug.cgi?id=153542 --- Comment #7 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153542] Libreoffice calc 7.5 very slow and unresponsive when zooming in out (wheel mouse) on large spreadsheet unde Debian
https://bugs.documentfoundation.org/show_bug.cgi?id=153542 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153526] No Numbering/New Line After Comment
https://bugs.documentfoundation.org/show_bug.cgi?id=153526 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 153526] No Numbering/New Line After Comment
https://bugs.documentfoundation.org/show_bug.cgi?id=153526 --- Comment #7 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152992] Regularly selecting a textbox instead of entering it (Impress)
https://bugs.documentfoundation.org/show_bug.cgi?id=152992 --- Comment #2 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149385] LibreOffice crashed repeadely (see very specific crash report in Description)
https://bugs.documentfoundation.org/show_bug.cgi?id=149385 --- Comment #4 from QA Administrators --- Dear gpspilot1, 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 150410] Insert picture to table change picture
https://bugs.documentfoundation.org/show_bug.cgi?id=150410 --- Comment #3 from QA Administrators --- Dear Jonas Högberg, 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 150381] LibreOffice 7.3.5.2 started giving a warning when clicking link to HTML file
https://bugs.documentfoundation.org/show_bug.cgi?id=150381 --- Comment #10 from QA Administrators --- Dear JIM7, 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 87338] RTL justification in cross-reference list window
https://bugs.documentfoundation.org/show_bug.cgi?id=87338 --- Comment #12 from QA Administrators --- Dear Boruch Baum, 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 140334] Failing widow control in footnotes
https://bugs.documentfoundation.org/show_bug.cgi?id=140334 --- Comment #5 from QA Administrators --- Dear Butch, 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 140330] Conditional formatting breaks after redoing cell deletion
https://bugs.documentfoundation.org/show_bug.cgi?id=140330 --- Comment #3 from QA Administrators --- Dear Xisco Faulí, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139949] Nesting up of sections when going from odt to html and back
https://bugs.documentfoundation.org/show_bug.cgi?id=139949 --- Comment #9 from QA Administrators --- Dear PhVerkerk, 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 135059] Formula objects gone after comparing documents & saving
https://bugs.documentfoundation.org/show_bug.cgi?id=135059 --- Comment #7 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 134821] Empty pages after pasting multiple times
https://bugs.documentfoundation.org/show_bug.cgi?id=134821 --- 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 134451] UI: Alignment between footnotes and endnotes tab different (and a label difference)
https://bugs.documentfoundation.org/show_bug.cgi?id=134451 --- Comment #3 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129033] Navigator's vertical scroll-bar is no longer exhibited under a condition
https://bugs.documentfoundation.org/show_bug.cgi?id=129033 --- Comment #20 from QA Administrators --- Dear ricky.tigg, 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 124824] FILEOPEN: Error rendering page break between two tables in a RTF
https://bugs.documentfoundation.org/show_bug.cgi?id=124824 --- Comment #6 from QA Administrators --- Dear Andrés Maldonado, 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 123380] LibreOfficeKit: Does not load and convert the attached document
https://bugs.documentfoundation.org/show_bug.cgi?id=123380 --- Comment #5 from QA Administrators --- Dear Murat, 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 122424] FILEOPEN RTF: In a specific document space character after table moves to the first cell of next row
https://bugs.documentfoundation.org/show_bug.cgi?id=122424 --- Comment #10 from QA Administrators --- Dear NISZ LibreOffice Team, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 118146] VBA Macro: Application.ActiveWorkbook.SaveAs saves invalid files
https://bugs.documentfoundation.org/show_bug.cgi?id=118146 --- Comment #10 from QA Administrators --- Dear Gabor Kelemen, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 116303] Merge cells toolbar button in Writer is inactive when cell selection doesn't move cursor
https://bugs.documentfoundation.org/show_bug.cgi?id=116303 --- Comment #9 from QA Administrators --- Dear Aron Budea, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114963] Hyperlink in exported SVG file styled incorrectly in Chrome and Opera
https://bugs.documentfoundation.org/show_bug.cgi?id=114963 --- Comment #13 from QA Administrators --- Dear drawbar, 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 114632] FORMATTING: Picture in Frame will loose wrap after frame will have been copied to page footer
https://bugs.documentfoundation.org/show_bug.cgi?id=114632 --- Comment #8 from QA Administrators --- Dear Rainer Bielefeld 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 114575] Autocorrect replacement mixes up Hebrew opening and closing quotes
https://bugs.documentfoundation.org/show_bug.cgi?id=114575 --- Comment #11 from QA Administrators --- Dear Eyal Rozenberg, 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 153549] Rename Tools > "Chapter Numbering" to "Heading Numbering"
https://bugs.documentfoundation.org/show_bug.cgi?id=153549 Adolfo Jayme Barrientos changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #3 from Adolfo Jayme Barrientos --- +1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152605] Change "heading level" to "outline level" in UI and help pages for Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=152605 --- Comment #17 from Commit Notification --- Seth Chaiklin committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/496b1b3179ca096dea1fd91ab2408c02f16b06cf tdf#152605 "heading level"->"outline level" and other tip corrections It will be available in 7.6.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/uiconfig
sw/uiconfig/swriter/ui/tocindexpage.ui | 12 +++- 1 file changed, 7 insertions(+), 5 deletions(-) New commits: commit 496b1b3179ca096dea1fd91ab2408c02f16b06cf Author: Seth Chaiklin AuthorDate: Sat Feb 11 23:43:53 2023 + Commit: Adolfo Jayme Barrientos CommitDate: Sun Feb 12 02:40:14 2023 + tdf#152605 "heading level"->"outline level" and other tip corrections Change-Id: I3751b8586ffe47233f3cd27602bcb5cad4d9ecb5 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146797 Tested-by: Jenkins Reviewed-by: Adolfo Jayme Barrientos diff --git a/sw/uiconfig/swriter/ui/tocindexpage.ui b/sw/uiconfig/swriter/ui/tocindexpage.ui index c29f0e4b384b..17712fa86184 100644 --- a/sw/uiconfig/swriter/ui/tocindexpage.ui +++ b/sw/uiconfig/swriter/ui/tocindexpage.ui @@ -354,9 +354,10 @@ True True True +Creates the index from all paragraphs that have an outline level equal to or greater than “1”. -Creates the index using outline levels. Paragraphs formatted with one of the predefined heading styles (Heading 1-10) are added to the index. +Creates the index from all paragraphs that have an outline level equal to or greater than “1”. @@ -502,6 +503,7 @@ False True True +Include selected paragraph styles with outline level “Text Body” in the index. Includes the paragraph styles that you specify in the Assign Styles dialog as index entries. To select the paragraph styles that you want to include in the index, click the Assign Styles (...) button to the right of this box. @@ -549,7 +551,7 @@ -Opens the Assign Styles dialog, where you can select the paragraph styles to include in the index. Choose the proper heading level on which the style will be included in the index. +Opens the Assign Styles dialog, where you can select the paragraph styles to include in the index by choosing the outline level for where the style should be placed. @@ -1014,7 +1016,7 @@ True -Replaces identical index entries with a single entry that lists the page numbers where the entry occurs in the document. For example, the entries "View 10, View 43" are combined as "View 10, 43". +Replaces identical index entries with a single entry that lists the page numbers where the entry occurs in the document. For example, the entries “View 10, View 43” are combined as “View 10, 43”. @@ -1034,7 +1036,7 @@ True -Replaces identical index entries that occur on the directly following page(s), with a single entry that lists the first page number and a "f" or "ff". For example, the entries "View 10, View 11" are combined as "View 10f", and "View 10, View 11, View 12" as "View 10ff". Actual appearance depends on the locale setting, but can be overridden with Sort - Language. +Replaces identical index entries that occur on the directly following page(s), with a single entry that lists the first page number and a “f” or “ff”. For example, the entries “View 10, View 11” are combined as “View 10f”, and “View 10, View 11, View 12” as “View 10ff”. Actual appearance depends on the locale setting, but can be overridden with Sort - Language. @@ -1054,7 +1056,7 @@ True -Replaces identical index entries that occur on consecutive pages with a single entry and the page range where the entry occurs. For example, the entries "View 10, View 11, View 12" are combined as "View 10-12". +Replaces identical index entries that occur on consecutive pages with a single entry and the page range where the entry occurs. For example, the entries “View 10, View 11, View 12” are combined as “View 10-12”.
[Libreoffice-bugs] [Bug 153558] Inserting between sections is impossible; reordering impossible
https://bugs.documentfoundation.org/show_bug.cgi?id=153558 sdc.bla...@youmail.dk changed: What|Removed |Added CC||sdc.bla...@youmail.dk --- Comment #1 from sdc.bla...@youmail.dk --- 1. Place cursor at end of first section. 2. Press Alt+Enter 3. Enter text as desired between the two sections. Does that resolve the issue? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153484] Spinning wheel in Calc on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=153484 --- Comment #4 from JackVos --- No, I'm afraid I don't. I just started it up to have a look and didn't see any file options. So, you'll need to spell out exactly what you'd like me to do. Thank you. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153561] Rename "Chapter -> Heading" and "E# -> H#" in Entries tab of Insert Table of Contents, Index, Bibliography dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=153561 sdc.bla...@youmail.dk changed: What|Removed |Added Blocks||122497 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||8718 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=122497 [Bug 122497] [META] Table of Contents and Indexes dialog bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122497] [META] Table of Contents and Indexes dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=122497 sdc.bla...@youmail.dk changed: What|Removed |Added Depends on||153561 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153561 [Bug 153561] Rename "Chapter -> Heading" and "E# -> H#" in Entries tab of Insert Table of Contents, Index, Bibliography dialog -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153561] New: Rename "Chapter -> Heading" and "E# -> H#" in Entries tab of Insert Table of Contents, Index, Bibliography dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=153561 Bug ID: 153561 Summary: Rename "Chapter -> Heading" and "E# -> H#" in Entries tab of Insert Table of Contents, Index, Bibliography dialog Product: LibreOffice Version: 7.2.7.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sdc.bla...@youmail.dk 1. Insert - Table of Contents and Index - Table of Contents, Index, or Bibliography 2. Select "Type" tab, then select "Type: Table of Contents" 3. Select "Entries" tab Change: - "Chapter No." -> "Heading No." -- because Chapter refers only to Outline Level 1, but the dialog allows the user to specify other (non-chapter) outline levels (i.e., "Headings") - "E#" -> "H#" (in Structure) -- so that the letter would be consistent with Heading. also consistent with change in bug 148718 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114039] [META] Fields dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=114039 sdc.bla...@youmail.dk changed: What|Removed |Added Depends on||153560 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153560 [Bug 153560] Rename "chapter" to "heading" in Insert Field (Document tab) -- 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 sdc.bla...@youmail.dk changed: What|Removed |Added Blocks||114039 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=114039 [Bug 114039] [META] Fields dialog bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153560] New: Rename "chapter" to "heading" in Insert Field (Document tab)
https://bugs.documentfoundation.org/show_bug.cgi?id=153560 Bug ID: 153560 Summary: Rename "chapter" to "heading" in Insert Field (Document tab) Product: LibreOffice Version: 7.2.7.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sdc.bla...@youmail.dk Insert - Field - More Fields (Ctrl-F2) - Document tab - Type "Chapter" Proposal: Type Format Chapter -> Heading (all) Chapter -> Heading Reason: In LO, chapter is a paragraph with outline level 1, but this dialog allows a user to select which outline level is used. This means that "chapter" is technically incorrect in this dialog (and does not highlight the fact that this variable can be used for headings at any outline level, or gives dissonance with the Level control). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148435] LibreOffice on macOS hangs on using window snapping / window manager (BetterTouchTool, Rectangle, Raycast, Amethyst, ...) or any other redraw, context switch, etc, from
https://bugs.documentfoundation.org/show_bug.cgi?id=148435 Patrick Luby changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=15 | |3484| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153484] Spinning wheel in Calc on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=153484 Patrick Luby changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=14 | |8435| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153559] New: Untranslatable string in safemodedialog.cxx
https://bugs.documentfoundation.org/show_bug.cgi?id=153559 Bug ID: 153559 Summary: Untranslatable string in safemodedialog.cxx Product: LibreOffice Version: 7.5.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: libreaj...@gmail.com Created attachment 185328 --> https://bugs.documentfoundation.org/attachment.cgi?id=185328=edit Safe Mode Dialog in Turkish Hi, This string, "Your user profile has been exported as 'libreoffice-profile.zip'." seems untranslatable in SafeModeDialog.cxx, line: 286 Thanks. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152567] macOS: LibreOffice freezes 7 seconds until popup granting access to certain folder (like documents) appears
https://bugs.documentfoundation.org/show_bug.cgi?id=152567 Patrick Luby changed: What|Removed |Added CC||plub...@neooffice.org --- Comment #5 from Patrick Luby --- I see this occasionally on my Silicon Mac except that it is after opening a file in my Downloads folder. There is a lag of a few seconds and just as I am going to the Finder to launch the Activity Monitor application, the macOS dialog that asks for permission for LibreOffice to access the Downloads folder appears. Are you able to obtain a sample from the Activity Monitor application? Or does it occur too infrequently for that? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153484] Spinning wheel in Calc on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=153484 --- Comment #3 from Patrick Luby --- (In reply to JackVos from comment #2) > Hi Patrick. As mentioned in the Description, "So, I downloaded and installed > 7.4.5.1. But instead of resolving the problem, it made it worse." I definitely missed that section. Anyway, I think the next step is to try to obtain a "sample file" when LibreOffice is hanging. Are you familiar with the macOS Activity Monitor application? In the Finder, it is in the /Applications/Utilities folder. I will ask the same in issue 152567. If we can get a one or more sample files from people experiencing this, that should narrow down what is causing this bug. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153558] New: Inserting between sections is impossible; reordering impossible
https://bugs.documentfoundation.org/show_bug.cgi?id=153558 Bug ID: 153558 Summary: Inserting between sections is impossible; reordering impossible Product: LibreOffice Version: 7.3.5.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rj.amdphr...@gmail.com Description: I have a document with sections that are back to back, with no whitespace between them. The sections themselves are links to other documents and are therefore uneditable. There is no way to place the typing cursor (I-beam, caret, whatever) between sections. This is a design flaw. I need to insert new sections between them, but there is no way to move sections up and down in the section list in the navigator view. This is a design flaw. 1. Enable mouse/keyboard to go to the space between sections when "Formatting marks" display mode is enabled. Perhaps even when it's not enabled. 2. Enable reordering sections. Both need to exist. These are just normal expected features. Steps to Reproduce: 1. create sections that links to external document. 2. Remove whitespace between them. 3. Try to insert anything at all between the two sections. Actual Results: failure Expected Results: success Reproducible: Always User Profile Reset: No Additional Info: I'm hungry. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152605] Change "heading level" to "outline level" in UI and help pages for Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=152605 --- Comment #16 from Commit Notification --- Seth Chaiklin committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/6f15382790e2e758ef7328a62341b30c655aced1 tdf#152605 change "heading level" to "outline level" in UI It will be available in 7.6.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152605] Change "heading level" to "outline level" in UI and help pages for Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=152605 Commit Notification changed: What|Removed |Added Whiteboard||target:7.6.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/uiconfig
sw/uiconfig/swriter/ui/captionoptions.ui |5 +++-- sw/uiconfig/swriter/ui/flddocumentpage.ui |5 +++-- sw/uiconfig/swriter/ui/fldvarpage.ui |3 ++- sw/uiconfig/swriter/ui/optcaptionpage.ui | 11 +++ sw/uiconfig/swriter/ui/tocindexpage.ui|3 ++- 5 files changed, 17 insertions(+), 10 deletions(-) New commits: commit 6f15382790e2e758ef7328a62341b30c655aced1 Author: Seth Chaiklin AuthorDate: Wed Feb 8 14:21:20 2023 + Commit: Adolfo Jayme Barrientos CommitDate: Sat Feb 11 23:31:44 2023 + tdf#152605 change "heading level" to "outline level" in UI This patch addresses extended tips in the UI that refer to a heading or chapter level, with the aim to remove this kind of terminology. In many cases, tooltips are added, and extended tips are corrected. Also, add "Outline" in front of "level" in the UI for Caption Options and AutoCaption. Change-Id: Idcf16892599913af31372b89d180251c86945d21 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146622 Tested-by: Jenkins Reviewed-by: Adolfo Jayme Barrientos diff --git a/sw/uiconfig/swriter/ui/captionoptions.ui b/sw/uiconfig/swriter/ui/captionoptions.ui index e4c89373ee6f..fbe32fede7b7 100644 --- a/sw/uiconfig/swriter/ui/captionoptions.ui +++ b/sw/uiconfig/swriter/ui/captionoptions.ui @@ -102,9 +102,10 @@ True False True +Specify the maximum outline level of the immediately prior heading number to include in the caption number. -Select the number of outline levels from the top of the chapter hierarchy down to include in the caption label. +Specify the maximum outline level of the immediately prior heading number to include in the caption number. For numbers to appear, the selected heading must have numbering applied. @@ -135,7 +136,7 @@ True False -_Level: +_Outline level: True level 1 diff --git a/sw/uiconfig/swriter/ui/flddocumentpage.ui b/sw/uiconfig/swriter/ui/flddocumentpage.ui index 9863c4e0b6d5..086dc0c924f0 100644 --- a/sw/uiconfig/swriter/ui/flddocumentpage.ui +++ b/sw/uiconfig/swriter/ui/flddocumentpage.ui @@ -345,7 +345,7 @@ True False -_Level +_Outline level True level 0 @@ -361,9 +361,10 @@ True adjustment1 True +Specifies the maximum outline level of the immediately prior heading to be used. -Select the chapter heading level that you want to include in the selected field. +The first immediately prior heading with an outline level equal or less than the specified number is selected for display. If “Chapter number” is selected, then numbering must be applied in the Chapter Numbering dialog (see Tools menu). diff --git a/sw/uiconfig/swriter/ui/fldvarpage.ui b/sw/uiconfig/swriter/ui/fldvarpage.ui index 78aa13b9b78f..caa033ee231c 100644 --- a/sw/uiconfig/swriter/ui/fldvarpage.ui +++ b/sw/uiconfig/swriter/ui/fldvarpage.ui @@ -429,12 +429,13 @@ True False +Choose the maximum outline level of the heading number to prepend to the displayed field. None -Choose the heading or chapter level at which to restart numbering in the document. +Choose the maximum outline level of the heading number to prepend to the displayed field. The selected heading number comes from the first immediately prior heading with the specified outline level or less. No heading number is displayed if “None” is selected. diff --git a/sw/uiconfig/swriter/ui/optcaptionpage.ui b/sw/uiconfig/swriter/ui/optcaptionpage.ui index 0bc7de887e73..0ad93bc4d888 100644 --- a/sw/uiconfig/swriter/ui/optcaptionpage.ui +++ b/sw/uiconfig/swriter/ui/optcaptionpage.ui @@ -147,10 +147,11 @@ center True True +Enter optional text characters to appear after the caption category and number.
[Libreoffice-commits] core.git: sw/source
sw/source/uibase/wrtsh/wrtsh1.cxx |5 +
1 file changed, 1 insertion(+), 4 deletions(-)
New commits:
commit d8b72d2d841d35f3dfdd38aa9adcedae7550279b
Author: Justin Luth
AuthorDate: Sat Feb 11 11:15:44 2023 -0500
Commit: Justin Luth
CommitDate: Sat Feb 11 23:24:21 2023 +
sw wrtsh1: cleanup unused pointer
Having a separate pCurRule was made useless by
commit 3234a9deaa8db760bbd7dbb6414aa3e8f9993c34
Author: Vladimir Glazounov
Date: Mon Feb 21 15:07:41 2005 +
INTEGRATION: CWS swqcore05 (1.40.82); FILE MERGED
Change-Id: I5fe0c7b09245acd9376d46b448708f29594a7266
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146824
Tested-by: Jenkins
Reviewed-by: Justin Luth
diff --git a/sw/source/uibase/wrtsh/wrtsh1.cxx
b/sw/source/uibase/wrtsh/wrtsh1.cxx
index 8b6b3b225113..5f7ac28519b4 100644
--- a/sw/source/uibase/wrtsh/wrtsh1.cxx
+++ b/sw/source/uibase/wrtsh/wrtsh1.cxx
@@ -1349,12 +1349,9 @@ void SwWrtShell::SplitNode( bool bAutoFormat )
// cursor position in the document.
void SwWrtShell::NumOrBulletOn(bool bNum)
{
-// determine numbering rule found at current cursor position in the
document.
-const SwNumRule* pCurRule = GetNumRuleAtCurrCursorPos();
-
StartUndo(SwUndoId::NUMORNONUM);
-const SwNumRule * pNumRule = pCurRule;
+const SwNumRule* pNumRule = GetNumRuleAtCurrCursorPos();
// - activate outline rule respectively turning on outline rule for
// current text node. But, only for turning on a numbering ( ==
true).
[Libreoffice-bugs] [Bug 137281] Clarify what "heading" means in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=137281 --- Comment #5 from sdc.bla...@youmail.dk --- Add "Heading" to General Glossary (bug 153547) https://gerrit.libreoffice.org/c/help/+/146796 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: download.lst external/liborcus
download.lst|4
external/liborcus/ExternalProject_liborcus.mk |2
external/liborcus/UnpackedTarball_liborcus.mk |2
external/liborcus/bugfix-0.18.0-unset-border-colors.patch.1 | 236
external/liborcus/liborcus-no-benchmark.patch.1 | 19
5 files changed, 4 insertions(+), 259 deletions(-)
New commits:
commit 3c988ef450b809767ca7f897c59041758af53f4b
Author: Kohei Yoshida
AuthorDate: Sat Feb 11 17:05:45 2023 -0500
Commit: Kohei Yoshida
CommitDate: Sat Feb 11 23:04:29 2023 +
Update liborcus to 0.18.1
Change-Id: I0439640789e59e4dd6e92d7f2975538de2f42f53
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146826
Tested-by: Jenkins
Reviewed-by: Kohei Yoshida
diff --git a/download.lst b/download.lst
index 0f42585bb7c8..4b8e212456e2 100644
--- a/download.lst
+++ b/download.lst
@@ -423,8 +423,8 @@ OPENSSL_TARBALL := openssl-3.0.8.tar.gz
# three static lines
# so that git cherry-pick
# will not run into conflicts
-ORCUS_SHA256SUM :=
0a8c55a227f13dbda08da8a1f6e18f27ba873da55a2cdd23bd0825989d1abff8
-ORCUS_TARBALL := liborcus-0.18.0.tar.xz
+ORCUS_SHA256SUM :=
6006b9f1576315e313df715a7e72a17f3e0b17d7b6bd119cfa8a0b608ce971eb
+ORCUS_TARBALL := liborcus-0.18.1.tar.xz
# three static lines
# so that git cherry-pick
# will not run into conflicts
diff --git a/external/liborcus/ExternalProject_liborcus.mk
b/external/liborcus/ExternalProject_liborcus.mk
index b07df31a34d0..7f2e5f24083f 100644
--- a/external/liborcus/ExternalProject_liborcus.mk
+++ b/external/liborcus/ExternalProject_liborcus.mk
@@ -99,6 +99,8 @@ $(call gb_ExternalProject_get_state_target,liborcus,build) :
$(if $(ENABLE_DEBUG),--enable-debug,--disable-debug) \
--disable-spreadsheet-model \
--without-tools \
+ --without-benchmark \
+ --without-doc-example \
--disable-python \
--disable-werror \
$(if $(filter
MACOSX,$(OS)),--prefix=/@.__OOO)
\
diff --git a/external/liborcus/UnpackedTarball_liborcus.mk
b/external/liborcus/UnpackedTarball_liborcus.mk
index 48b7fb4743e9..ca4a40acf4e5 100644
--- a/external/liborcus/UnpackedTarball_liborcus.mk
+++ b/external/liborcus/UnpackedTarball_liborcus.mk
@@ -21,8 +21,6 @@ $(eval $(call gb_UnpackedTarball_add_patches,liborcus,\
external/liborcus/libtool.patch.0 \
external/liborcus/fix-pch.patch.0 \
external/liborcus/liborcus_newline.patch.1 \
- external/liborcus/liborcus-no-benchmark.patch.1 \
- external/liborcus/bugfix-0.18.0-unset-border-colors.patch.1 \
))
ifeq ($(OS),WNT)
diff --git a/external/liborcus/bugfix-0.18.0-unset-border-colors.patch.1
b/external/liborcus/bugfix-0.18.0-unset-border-colors.patch.1
deleted file mode 100644
index 5b8a04069e99..
--- a/external/liborcus/bugfix-0.18.0-unset-border-colors.patch.1
+++ /dev/null
@@ -1,236 +0,0 @@
-diff --git a/src/liborcus/xls_xml_context.cpp
b/src/liborcus/xls_xml_context.cpp
-index 85916fc7..739678ee 100644
a/src/liborcus/xls_xml_context.cpp
-+++ b/src/liborcus/xls_xml_context.cpp
-@@ -1292,7 +1292,7 @@ void xls_xml_context::start_element_border(const
xml_token_attrs_t& attrs)
- {
- ss::border_direction_t dir = ss::border_direction_t::unknown;
- ss::border_style_t style = ss::border_style_t::unknown;
--ss::color_rgb_t color;
-+std::optional color;
- long weight = 0;
-
- for (const xml_token_attr_t& attr : attrs)
-@@ -1950,8 +1950,14 @@ void xls_xml_context::commit_default_style()
- {
- for (const border_style_type& b : m_default_style->borders)
- {
--border_style->set_style(b.dir, b.style);
--border_style->set_color(b.dir, 255, b.color.red, b.color.green,
b.color.blue);
-+if (b.dir == ss::border_direction_t::unknown)
-+continue;
-+
-+if (b.style != ss::border_style_t::unknown)
-+border_style->set_style(b.dir, b.style);
-+
-+if (b.color)
-+border_style->set_color(b.dir, 255, b.color->red,
b.color->green, b.color->blue);
- }
- }
-
-@@ -2109,8 +2115,14 @@ void xls_xml_context::commit_styles()
-
- for (const border_style_type& b : style->borders)
- {
--border_style->set_style(b.dir, b.style);
--border_style->set_color(b.dir, 255, b.color.red,
b.color.green, b.color.blue);
-+if (b.dir == ss::border_direction_t::unknown)
-+continue;
-+
-+if (b.style != ss::border_style_t::unknown)
-+border_style->set_style(b.dir, b.style);
-+
-+if (b.color)
-+border_style->set_color(b.dir, 255, b.color->red,
[Libreoffice-bugs] [Bug 150209] Partially obstructed headings in floating Navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=150209 Dieter changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #14 from Dieter --- (In reply to inoukdemers from comment #8) > Hello all and apologies for the delay. > > 1. Here is the version information: > > Version: 7.3.7.2 (x64) / LibreOffice Community Could you retest with actual version 7.5? Is bug still present there? => NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153020] open a .doc format document in libreoffice 7.4.3 is stuck, it is normal in 7.3.7 version
https://bugs.documentfoundation.org/show_bug.cgi?id=153020 Dieter changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO CC||dgp-m...@gmx.de Ever confirmed|0 |1 --- Comment #6 from Dieter --- (In reply to wujiahuan from comment #5) > My linux desktop is centos 8, the locale set is zh_CN.UTF-8，the document > font is 宋体 Have you tested with clean user profile? => NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: bin/lo-pack-sources
bin/lo-pack-sources | 16 +++-
1 file changed, 15 insertions(+), 1 deletion(-)
New commits:
commit a0165bb7900f6d03a49076d755568ac33ee8e9c9
Author: Sebastian Andrzej Siewior
AuthorDate: Fri Feb 10 22:18:05 2023 +0100
Commit: Thorsten Behrens
CommitDate: Sat Feb 11 22:45:27 2023 +
lo-pack-sources: Add support for pbzip2.
Use pbzip for compression if possible. Otherwise fallback to bzip2.
Signed-off-by: Sebastian Andrzej Siewior
Change-Id: I9091c5dfe25ee00854b6938464af23b56cdcb31c
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146814
Tested-by: Jenkins
Reviewed-by: Thorsten Behrens
diff --git a/bin/lo-pack-sources b/bin/lo-pack-sources
index 289a595b06e0..a34a4c95ab6a 100755
--- a/bin/lo-pack-sources
+++ b/bin/lo-pack-sources
@@ -285,19 +285,33 @@ sub generate_module_tarball()
my ($source_dir, $release_version, $module, $md5, $bzip2, $xz,
$lo_topdir_name, $module_tarball_name) = @_;
my $PARALLELISM = $ENV{'PARALLELISM'};
my $CPUS_XZ = 0;
+my $CPUS_BZ2 = "";
+my $bzip_arguments;
# Set CPUS_ to the number of CPUs that should be used. If PARALLELISM
# is set then this is used otherwise autodetect is used.
if (defined $PARALLELISM) {
if ($PARALLELISM > 0) {
$CPUS_XZ = $PARALLELISM;
+$CPUS_BZ2 = "-p$PARALLELISM";
} else {
$CPUS_XZ = 1;
+$CPUS_BZ2 = "-p1";
}
}
+if (defined $bzip2) {
+ my $exit_code = system("pbzip2 --version >/dev/null 2>&1");
+ if ($exit_code == 0) {
+ $bzip_arguments = "pbzip2 -z -b20 $CPUS_BZ2";
+ } else {
+ $bzip_arguments = "bzip2 -z --best";
+ print("Consider installing pbzip2, using bzip2
now.\n");
+ }
+}
+
my $temp_dir = prepare_module_sources($source_dir, $release_version,
$module, $lo_topdir_name);
-pack_module_sources($temp_dir, $md5, "$module_tarball_name.tar.bz2",
"bzip2 -z --best > ") if (defined $bzip2);
+pack_module_sources($temp_dir, $md5, "$module_tarball_name.tar.bz2",
"$bzip_arguments > ") if (defined $bzip2);
pack_module_sources($temp_dir, $md5, "$module_tarball_name.tar.xz", "xz -z
-T$CPUS_XZ -e > ") if (defined $xz);
remove_tempdir($temp_dir);
}
[Libreoffice-commits] core.git: 2 commits - bin/lo-pack-sources
bin/lo-pack-sources | 24 ++--
1 file changed, 18 insertions(+), 6 deletions(-)
New commits:
commit cb9883b1e9fb620f280e950de2bb50f9ec3a4c5e
Author: Sebastian Andrzej Siewior
AuthorDate: Tue Jan 24 23:00:44 2023 +0100
Commit: Thorsten Behrens
CommitDate: Sat Feb 11 22:45:18 2023 +
lo-pack-sources: Use threaded compression for xz.
The xz utility can compress in parallel by using more CPU cores. The
more CPUs are available the quicker it gets.
The option -T0 automatically detects the number of available CPUs and
uses all of them.
Additional benefit is that xz starting with v5.4 can decompress the
archive using multiple CPUs as well.
The parallel compression works by splitting the input in multiple blocks
of equal size which are compressed in parallel. Since the state is not
preserved / reuse across blocks, the compression gets a little worse:
-6 255M (current default)
-T0 261M
-eT0259M
-7T0251M
-7eT0 249M
-7 uses larger blocks and dictionary which requires more memory on the
compressing and decompressing side vs the current default -6.
The -e option spends some extra cycles and improves the compression a
bit.
Use parallel compression and spend some extra cycles.
Signed-off-by: Sebastian Andrzej Siewior
Change-Id: Ib69c4bc1996ddd52153b8ac27b653c21e3998a68
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146793
Tested-by: Jenkins
Reviewed-by: Thorsten Behrens
diff --git a/bin/lo-pack-sources b/bin/lo-pack-sources
index b4150ab87ad7..289a595b06e0 100755
--- a/bin/lo-pack-sources
+++ b/bin/lo-pack-sources
@@ -283,10 +283,22 @@ sub pack_module_sources()
sub generate_module_tarball()
{
my ($source_dir, $release_version, $module, $md5, $bzip2, $xz,
$lo_topdir_name, $module_tarball_name) = @_;
+my $PARALLELISM = $ENV{'PARALLELISM'};
+my $CPUS_XZ = 0;
+
+# Set CPUS_ to the number of CPUs that should be used. If PARALLELISM
+# is set then this is used otherwise autodetect is used.
+if (defined $PARALLELISM) {
+if ($PARALLELISM > 0) {
+$CPUS_XZ = $PARALLELISM;
+} else {
+$CPUS_XZ = 1;
+ }
+}
my $temp_dir = prepare_module_sources($source_dir, $release_version,
$module, $lo_topdir_name);
pack_module_sources($temp_dir, $md5, "$module_tarball_name.tar.bz2",
"bzip2 -z --best > ") if (defined $bzip2);
-pack_module_sources($temp_dir, $md5, "$module_tarball_name.tar.xz", "xz -z
> ") if (defined $xz);
+pack_module_sources($temp_dir, $md5, "$module_tarball_name.tar.xz", "xz -z
-T$CPUS_XZ -e > ") if (defined $xz);
remove_tempdir($temp_dir);
}
commit 30f49b56ba6712fb8fb3dd8febb870a1157e1516
Author: Sebastian Andrzej Siewior
AuthorDate: Fri Feb 10 21:49:25 2023 +0100
Commit: Thorsten Behrens
CommitDate: Sat Feb 11 22:45:10 2023 +
lo-pack-sources: Split archiver invocation away from tar.
Instead of passing --bzip2 or --xz invoke the compression program via a
pipe. This make the replacement of compressor as well its options
easier.
Signed-off-by: Sebastian Andrzej Siewior
Change-Id: Ib69c4bc1996ddd52153b8ac27b653c21e3998a67
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146105
Tested-by: Jenkins
Reviewed-by: Thorsten Behrens
diff --git a/bin/lo-pack-sources b/bin/lo-pack-sources
index 8c795dc170c5..b4150ab87ad7 100755
--- a/bin/lo-pack-sources
+++ b/bin/lo-pack-sources
@@ -155,11 +155,11 @@ sub generate_sources_version_file($$)
sub generate_tarball($$$)
{
-my ($dir, $tarball, $tar_compress_option) = @_;
+my ($dir, $tarball, $compressor_option) = @_;
print "Creating $tarball...";
# generate the tarball in the current directory; avoid "./" prefix in the
stored paths; show progress
-system ("tar -c $tar_compress_option -f $tarball -C $dir $lo_topdir_name")
&&
+system ("tar -c -C $dir $lo_topdir_name | $compressor_option $tarball") &&
die "Error: releasing failed: $!\n";
print "\n";
}
@@ -274,9 +274,9 @@ sub prepare_module_sources()
sub pack_module_sources()
{
-my ($temp_dir, $md5, $tarball, $tar_compress_option) = @_;
+my ($temp_dir, $md5, $tarball, $compressor_option) = @_;
-generate_tarball($temp_dir, $tarball, $tar_compress_option);
+generate_tarball($temp_dir, $tarball, $compressor_option);
generate_md5($tarball) if (defined $md5);
}
@@ -285,8 +285,8 @@ sub generate_module_tarball()
my ($source_dir, $release_version, $module, $md5, $bzip2, $xz,
$lo_topdir_name, $module_tarball_name) = @_;
my $temp_dir = prepare_module_sources($source_dir, $release_version,
$module, $lo_topdir_name);
-pack_module_sources($temp_dir, $md5, "$module_tarball_name.tar.bz2",
"--bzip2") if (defined
[Libreoffice-bugs] [Bug 153549] Rename Tools > "Chapter Numbering" to "Heading Numbering"
https://bugs.documentfoundation.org/show_bug.cgi?id=153549 Dieter changed: What|Removed |Added CC||dgp-m...@gmx.de --- Comment #2 from Dieter --- I agree, that it would solve some problem +1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153557] New: Feature request: to draw directly in LO Inmpress or Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=153557 Bug ID: 153557 Summary: Feature request: to draw directly in LO Inmpress or Writer Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: puigp...@gmail.com Created attachment 185327 --> https://bugs.documentfoundation.org/attachment.cgi?id=185327=edit Example of a slide with handwriting It wuld be very usegul to be able to have a draring menu to draw directly in a ppt in Impress or in a Doc in the Writer, to use ie. a Wabom tablet to drqaw in a slide, as it is in MS Office. The idea is to ber able to add handwritten comment sor text. Otherwise I have to draw in another program (xournalpp) and copy´paste into my Impress slides: this is very slow ant not practical... -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153506] LibreCalc - When copying an existing sheet to a new sheet LibreCalc does not preserve conditional formatting on new sheet. Example provided in description.
https://bugs.documentfoundation.org/show_bug.cgi?id=153506 m.a.riosv changed: What|Removed |Added Resolution|--- |NOTABUG Status|NEEDINFO|RESOLVED --- Comment #6 from m.a.riosv --- (In reply to bwilderhoo from comment #4) > Hi, > > Thanks for the feedback. Here is what you are missing (and it is a easy > thing to miss). The condition for range B18:M18 is to check the cell value > against the cell $Budget.$B23, whereas the condition for range B19:M19 is to > check the cell value against the cell $Budget.$B24. Basically, the first And it's what the new condition does. >. > > For merged line that covers both rows with the range of B18:M19 the > condition is to check the cell value against the cell phone budgeted amount. > The electricity budgeted amount is lost in the merge. In fact, because the > conditions are checking against different budgeted amounts no merged single > condition can be used to cover both of the ranges. The two lines are I think it is not understood how the condicional format works. For a range, like B18:M19 it analyzes the conditions for every cell, varying accordingly the relative ranges in the conditions. E.g. for B18 -> $Budget.$B23 is analyzed, for B19 -> $Budget.$B24 is it. > mutually exclusive checks and ranges that need to remain as is, and not > merged when copied to a new sheet. If you want the ranges not to be merged, use an absolute reference also for the row $Budget.$B$23 This was done to reduce duplicated ranges with the same conditions. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138133] Insert media from scanner froze LO
https://bugs.documentfoundation.org/show_bug.cgi?id=138133 --- Comment #7 from mooregraeme --- If inserting media from a scanner froze LibreOffice, try force quitting the application and restarting it. If the issue persists, try disconnecting and reconnecting the scanner, and check if there are any updates available for the scanner driver. You can also try using a different application to scan and save the media, and then import the saved file into LibreOffice. If none of these solutions work, you may need to seek further technical assistance. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153506] LibreCalc - When copying an existing sheet to a new sheet LibreCalc does not preserve conditional formatting on new sheet. Example provided in description.
https://bugs.documentfoundation.org/show_bug.cgi?id=153506 --- Comment #5 from ady --- (In reply to bwilderhoo from comment #4) > Please confirm that you are seeing what I have described above. I still don't see it. I added values to both sheets (original and copy) in row 19, and I see the same expected result. I modify the value in row 24 of the Budget sheet, and I see the same results in both sheets, every time. Please either attach an example, a file with specific values in "Budget" that will trigger the "incorrect" (conditional) format (IIUC, a different resulting format in the newly-created sheet than the resulting format in the original sheet). Or, alternatively (and preferably ATM), please simply write down at least one value and where exactly to introduce it (i.e. in which cell of which sheet in your attachment 185308) in order to trigger the unexpected resulting format. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153484] Spinning wheel in Calc on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=153484 --- Comment #2 from JackVos --- Hi Patrick. As mentioned in the Description, "So, I downloaded and installed 7.4.5.1. But instead of resolving the problem, it made it worse." -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153390] FILESAVE XLSX Saving from XLS to XLSX changes vertical alignment of cell
https://bugs.documentfoundation.org/show_bug.cgi?id=153390 Bartosz changed: What|Removed |Added CC||gan...@poczta.onet.pl --- Comment #2 from Bartosz --- The issue is reproducible also during XLSX to XLSX save. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153536] Calc toolbar partially hides
https://bugs.documentfoundation.org/show_bug.cgi?id=153536 --- Comment #14 from ady --- (In reply to V Stuart Foote from comment #13) > Believe that NB Tabbed UI issue is bug 140557, lets not hijack this NB > Groupedbar UI issue. I will not add more confusion than what there is already, so I will not open a new bug report nor change anything else regarding all these several UI bugs, until they are resolved. I just want to point out that what I am seeing now in LO 7.4.5 and in 7.6.alpha+, I was not seeing in LO 7.4.4. To be clear, it is possible that I was using some different setting in Windows (e.g. Accessibility > font size), or even that I used a different LO UI with 7.4.4. Whichever the case, I don't recall experiencing this half-toolbar hidden repeated annoying behavior with 7.4.4. -- 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 153122, which changed state. Bug 153122 Summary: "numbering separator" missing from Insert Caption help and "caption order" missing from (Caption) options helps https://bugs.documentfoundation.org/show_bug.cgi?id=153122 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103859] [META] EMF/WMF (Enhanced/Windows Metafile) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103859 Bug 103859 depends on bug 142018, which changed state. Bug 142018 Summary: [EMF] Few Arcs with different pens: wrong line width for the 3rd arc https://bugs.documentfoundation.org/show_bug.cgi?id=142018 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: emfio/qa emfio/source
emfio/qa/cppunit/emf/EmfImportTest.cxx | 45 ++---
emfio/source/reader/emfreader.cxx | 25 +++---
emfio/source/reader/mtftools.cxx |4 +-
3 files changed, 43 insertions(+), 31 deletions(-)
New commits:
commit bbdbe8ea2ef176ef6f08b30b3c18876c2c4f0c22
Author: Bartosz Kosiorek
AuthorDate: Fri Feb 3 22:55:54 2023 +0100
Commit: Bartosz Kosiorek
CommitDate: Sat Feb 11 21:24:18 2023 +
tdf#142018 Properly create Pen width if style is COSMETIC
Change-Id: I6453058c4af352a3b0e14cbccbc1a67c73cd1426
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146551
Tested-by: Jenkins
Reviewed-by: Bartosz Kosiorek
diff --git a/emfio/qa/cppunit/emf/EmfImportTest.cxx
b/emfio/qa/cppunit/emf/EmfImportTest.cxx
index 75f2b9001a08..e858fd7afc4d 100644
--- a/emfio/qa/cppunit/emf/EmfImportTest.cxx
+++ b/emfio/qa/cppunit/emf/EmfImportTest.cxx
@@ -180,14 +180,19 @@ void Test::testPolyPolygon()
assertXPath(pDocument, aXPathPrefix +
"mask/polypolygoncolor[2]/polypolygon", "path",
"m2574 13194v-12065h15303v12065z");
-assertXPath(pDocument, aXPathPrefix + "mask/polygonstroke", 116);
+assertXPath(pDocument, aXPathPrefix + "mask/polygonstroke", 44);
assertXPathContent(pDocument, aXPathPrefix +
"mask/polygonstroke[1]/polygon",
- "2574,13194 2574,1129 17877,1129 17877,13194");
-assertXPath(pDocument, aXPathPrefix + "mask/polygonstroke[1]/line",
"color", "#ff");
-
+ "2574,13194 2574,1129");
+assertXPath(pDocument, aXPathPrefix + "mask/polygonstroke[1]/line",
"color", "#00");
+assertXPath(pDocument, aXPathPrefix + "mask/polygonstroke[1]/line",
"width", "0");
+assertXPathContent(pDocument, aXPathPrefix +
"mask/polygonstroke[2]/polygon",
+ "2574,1129 2574,1129");
+assertXPath(pDocument, aXPathPrefix + "mask/polygonstroke[2]/line",
"color", "#00");
+assertXPath(pDocument, aXPathPrefix + "mask/polygonstroke[2]/line",
"width", "0");
assertXPathContent(pDocument, aXPathPrefix +
"mask/polygonstroke[10]/polygon",
- "8674,13194 8674,1129");
+ "8674,1129 8674,1129");
assertXPath(pDocument, aXPathPrefix + "mask/polygonstroke[10]/line",
"color", "#00");
+assertXPath(pDocument, aXPathPrefix + "mask/polygonstroke[10]/line",
"width", "0");
assertXPath(pDocument, aXPathPrefix + "mask/textsimpleportion", 28);
assertXPath(pDocument, aXPathPrefix + "mask/textsimpleportion[6]",
"width", "459");
@@ -1547,7 +1552,7 @@ void Test::TestRoundRect()
void Test::TestCreatePen()
{
// Check import of EMF image with records: RESTOREDC, SAVEDC, MOVETOEX,
LINETO, POLYLINE16, EXTTEXTOUTW with DxBuffer
-// The CREATEPEN record is used with PS_COSMETIC line style, which
sometimes will be displayed as solid hairline
+// The CREATEPEN record is used with PS_COSMETIC line style, and in this
case width must be set to 0
Primitive2DSequence aSequence =
parseEmf(u"/emfio/qa/cppunit/emf/data/TestCreatePen.emf");
CPPUNIT_ASSERT_EQUAL(1, static_cast(aSequence.getLength()));
drawinglayer::Primitive2dXmlDump dumper;
@@ -1556,29 +1561,29 @@ void Test::TestCreatePen()
assertXPath(pDocument, aXPathPrefix + "mask/polypolygon", "path", "m0
0h31250v18192h-31250z");
-assertXPath(pDocument, aXPathPrefix + "mask/polygonstroke", 748);
+assertXPath(pDocument, aXPathPrefix + "mask/polygonstroke", 3);
assertXPathContent(pDocument, aXPathPrefix +
"mask/polygonstroke[1]/polygon",
- "27875,16523 27875,1453");
-assertXPath(pDocument, aXPathPrefix + "mask/polygonstroke[1]/line",
"color", "#ff");
-assertXPath(pDocument, aXPathPrefix + "mask/polygonstroke[1]/line",
"width", "6");
+ "17898,5693 20172,5693");
+assertXPath(pDocument, aXPathPrefix + "mask/polygonstroke[1]/line",
"color", "#008000");
+assertXPath(pDocument, aXPathPrefix + "mask/polygonstroke[1]/line",
"width", "0");
assertXPathContent(pDocument, aXPathPrefix +
"mask/polygonstroke[2]/polygon",
- "27975,16453 27875,16453");
-assertXPath(pDocument, aXPathPrefix + "mask/polygonstroke[2]/line",
"color", "#ff");
-assertXPath(pDocument, aXPathPrefix + "mask/polygonstroke[2]/line",
"width", "6");
+ "17898,6959 20172,6959");
+assertXPath(pDocument, aXPathPrefix + "mask/polygonstroke[2]/line",
"color", "#80");
+assertXPath(pDocument, aXPathPrefix + "mask/polygonstroke[2]/line",
"width", "0");
assertXPathContent(pDocument, aXPathPrefix +
"mask/polygonstroke[3]/polygon",
- "27925,16078 27875,16078");
+ "17898,7381 20172,7381");
assertXPath(pDocument, aXPathPrefix + "mask/polygonstroke[3]/line",
"color", "#ff");
-assertXPath(pDocument, aXPathPrefix +
[Libreoffice-bugs] [Bug 115709] [META] DOCX (OOXML) Tracking changes-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=115709 Bug 115709 depends on bug 147892, which changed state. Bug 147892 Summary: Corrupt DOCX document after saving (track changes involved) https://bugs.documentfoundation.org/show_bug.cgi?id=147892 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147892] Corrupt DOCX document after saving (track changes involved)
https://bugs.documentfoundation.org/show_bug.cgi?id=147892 László Németh changed: What|Removed |Added Assignee|nem...@numbertext.org |libreoffice-b...@lists.free ||desktop.org Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #17 from László Németh --- Fixed in master, backport is in progress. @Milan: thanks for the bug report! @Miklós: thanks for bibisecting & analysis! @Gábor, Áron, Timur: thanks for handling the issue! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sd/source
sd/source/ui/view/drviewse.cxx | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
New commits:
commit c96e1ec61835bc01e2969ec97fce9a1674fbf6d7
Author: Rafael Lima
AuthorDate: Sat Feb 11 16:36:00 2023 -0300
Commit: Jim Raykowski
CommitDate: Sat Feb 11 21:07:31 2023 +
tdf#45705 Make SID_ZOOM_IN and SID_ZOOM_OUT smoother in Impress
As reported in the bug ticket, the commands SID_ZOOM_IN and SID_ZOOM_OUT
are not smooth and increase/decrease zoom at too big steps.
This patch uses basegfx::zoomtools to zoom in and out, making it smoother.
Change-Id: I801fa6123bf0696046e5d45c7a6b309e7cc3312e
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146825
Tested-by: Jenkins
Reviewed-by: Jim Raykowski
diff --git a/sd/source/ui/view/drviewse.cxx b/sd/source/ui/view/drviewse.cxx
index b3183397a084..5a6a7577951e 100644
--- a/sd/source/ui/view/drviewse.cxx
+++ b/sd/source/ui/view/drviewse.cxx
@@ -95,6 +95,7 @@
#include
#include
#include
+#include
using namespace ::com::sun::star;
using namespace ::com::sun::star::uno;
@@ -1189,8 +1190,11 @@ void DrawViewShell::FuSupport(SfxRequest& rReq)
case SID_ZOOM_OUT: // BASIC
{
+const sal_uInt16 nOldZoom = GetActiveWindow()->GetZoom();
+const sal_uInt16 nNewZoom = basegfx::zoomtools::zoomOut(nOldZoom);
+SetZoom(nNewZoom);
+
mbZoomOnPage = false;
-SetZoom( std::max<::tools::Long>( GetActiveWindow()->GetZoom() /
2, GetActiveWindow()->GetMinZoom() ) );
::tools::Rectangle aVisAreaWin = GetActiveWindow()->PixelToLogic(
::tools::Rectangle( Point(0,0),
GetActiveWindow()->GetOutputSizePixel()) );
mpZoomList->InsertZoomRect(aVisAreaWin);
@@ -1203,8 +1207,11 @@ void DrawViewShell::FuSupport(SfxRequest& rReq)
case SID_ZOOM_IN:
{
+const sal_uInt16 nOldZoom = GetActiveWindow()->GetZoom();
+const sal_uInt16 nNewZoom = basegfx::zoomtools::zoomIn(nOldZoom);
+SetZoom(nNewZoom);
+
mbZoomOnPage = false;
-SetZoom( std::min<::tools::Long>( GetActiveWindow()->GetZoom() *
2, GetActiveWindow()->GetMaxZoom() ) );
::tools::Rectangle aVisAreaWin = GetActiveWindow()->PixelToLogic(
::tools::Rectangle( Point(0,0),
GetActiveWindow()->GetOutputSizePixel()) );
mpZoomList->InsertZoomRect(aVisAreaWin);
[Libreoffice-commits] core.git: sw/qa sw/source
sw/qa/extras/ooxmlexport/data/tdf147892.fodt | 25 ++
sw/qa/extras/ooxmlexport/ooxmlexport12.cxx | 10 +
sw/source/filter/ww8/docxattributeoutput.cxx | 30 ++-
sw/source/filter/ww8/docxattributeoutput.hxx |4 +--
4 files changed, 53 insertions(+), 16 deletions(-)
New commits:
commit 382892341a63e400f221e1a533fd5a5d6b4d9d70
Author: László Németh
AuthorDate: Fri Feb 10 13:43:40 2023 +0100
Commit: László Németh
CommitDate: Sat Feb 11 21:06:21 2023 +
tdf#147892 DOCX: fix corrupt export at para marker revision history
OOXML export of tracked deletion of tracked paragraph insertion
resulted invalid document.xml, because change tracking history of
paragraph markers isn't supported by OOXML. Export the tracked deletion
of the last run of paragraphs without history (tracked insertion).
This way w:p/w:pPr/w:rPr contains only w:del or w:ins, not both of them
(with broken tag order).
Note: it's possible to optimize the fix to keep the change
tracking history of the characters of the last run of the paragraph,
except the paragraph marker.
Regression from commit 19b3fcf8b0374c361c7f6c285fd5c89b5a2f
"tdf#142387 DOCX track changes: export w:del in w:ins".
Minimal unit test document was created by Miklós Vajna.
Change-Id: I425f4d63c8c6ac29ccd807c1574748c7b9b39e80
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146782
Tested-by: László Németh
Reviewed-by: László Németh
diff --git a/sw/qa/extras/ooxmlexport/data/tdf147892.fodt
b/sw/qa/extras/ooxmlexport/data/tdf147892.fodt
new file mode 100644
index ..bb3ffc324dc1
--- /dev/null
+++ b/sw/qa/extras/ooxmlexport/data/tdf147892.fodt
@@ -0,0 +1,25 @@
+
+http://purl.org/dc/elements/1.1/;
xmlns:text="urn:oasis:names:tc:opendocument:xmlns:text:1.0"
office:version="1.3" office:mimetype="application/vnd.oasis.opendocument.text">
+
+
+
+
+
+
+ Bob
+ 2023-01-02T00:00:00
+
+
+
+
+ Alice
+ 2023-01-01T00:00:00
+
+
+
+
+
+
+
+
+
diff --git a/sw/qa/extras/ooxmlexport/ooxmlexport12.cxx
b/sw/qa/extras/ooxmlexport/ooxmlexport12.cxx
index 444fbf51a39c..2713a582c9d9 100644
--- a/sw/qa/extras/ooxmlexport/ooxmlexport12.cxx
+++ b/sw/qa/extras/ooxmlexport/ooxmlexport12.cxx
@@ -1997,6 +1997,16 @@ CPPUNIT_TEST_FIXTURE(Test, testTdf142387)
assertXPathContent(pXmlDoc,
"/w:document/w:body/w:p/w:ins/w:del/w:r/w:delText", "inserts ");
}
+CPPUNIT_TEST_FIXTURE(Test, testTdf147892)
+{
+loadAndSave("tdf147892.fodt");
+xmlDocUniquePtr pXmlDoc = parseExport("word/document.xml");
+// w:del in w:ins is exported correctly
+// (both w:del and w:ins were exported for para marker)
+assertXPath(pXmlDoc, "/w:document/w:body/w:p[1]/w:pPr/w:rPr/w:del", 1);
+assertXPath(pXmlDoc, "/w:document/w:body/w:p[1]/w:pPr/w:rPr/w:ins", 0);
+}
+
DECLARE_OOXMLEXPORT_TEST(testTdf123054, "tdf123054.docx")
{
CPPUNIT_ASSERT_EQUAL(OUString("No Spacing"),
diff --git a/sw/source/filter/ww8/docxattributeoutput.cxx
b/sw/source/filter/ww8/docxattributeoutput.cxx
index 0aef9a066741..528033e7b3b7 100644
--- a/sw/source/filter/ww8/docxattributeoutput.cxx
+++ b/sw/source/filter/ww8/docxattributeoutput.cxx
@@ -1510,13 +1510,13 @@ void DocxAttributeOutput::EndParagraphProperties(const
SfxItemSet& rParagraphMar
if ( pRedlineParagraphMarkerDeleted )
{
-StartRedline( pRedlineParagraphMarkerDeleted );
-EndRedline( pRedlineParagraphMarkerDeleted );
+StartRedline( pRedlineParagraphMarkerDeleted, /*bLastRun=*/true );
+EndRedline( pRedlineParagraphMarkerDeleted, /*bLastRun=*/true );
}
if ( pRedlineParagraphMarkerInserted )
{
-StartRedline( pRedlineParagraphMarkerInserted );
-EndRedline( pRedlineParagraphMarkerInserted );
+StartRedline( pRedlineParagraphMarkerInserted, /*bLastRun=*/true );
+EndRedline( pRedlineParagraphMarkerInserted, /*bLastRun=*/true );
}
// mergeTopMarks() after paragraph mark properties child elements.
@@ -1623,7 +1623,7 @@ void DocxAttributeOutput::StartRun( const SwRedlineData*
pRedlineData, sal_Int32
m_pSerializer->mark(Tag_StartRun_3); // let's call it "postponed text"
}
-void DocxAttributeOutput::EndRun(const SwTextNode* pNode, sal_Int32 nPos,
sal_Int32 nLen, bool /*bLastRun*/)
+void DocxAttributeOutput::EndRun(const SwTextNode* pNode, sal_Int32 nPos,
sal_Int32 nLen, bool bLastRun)
{
int nFieldsInPrevHyperlink = m_nFieldsInHyperlink;
// Reset m_nFieldsInHyperlink if a new hyperlink is about to start
@@ -1707,9 +1707,9 @@ void DocxAttributeOutput::EndRun(const SwTextNode* pNode,
sal_Int32 nPos, sal_In
// InputField with extra grabbag params - it is sdt field
[Libreoffice-bugs] [Bug 120200] [META] Update or correct help for features
https://bugs.documentfoundation.org/show_bug.cgi?id=120200 sdc.bla...@youmail.dk changed: What|Removed |Added Depends on||153551 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153551 [Bug 153551] Mistake in the "Caption" and "Category" entries for Insert Caption help -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153551] Mistake in the "Caption" and "Category" entries for Insert Caption help
https://bugs.documentfoundation.org/show_bug.cgi?id=153551 sdc.bla...@youmail.dk changed: What|Removed |Added Summary|Mistake in the "Category" |Mistake in the "Caption" |entry for Insert Caption|and "Category" entries for |help|Insert Caption help Blocks||120200 --- Comment #1 from sdc.bla...@youmail.dk --- Same page, same problem for the "Caption" entry. Actual: "Type the text that you want to appear after the caption number." Needed: to indicate that the text appears after the category and caption number. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=120200 [Bug 120200] [META] Update or correct help for features -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148435] LibreOffice on macOS hangs on using window snapping / window manager (BetterTouchTool, Rectangle, Raycast, Amethyst, ...) or any other redraw, context switch, etc, from
https://bugs.documentfoundation.org/show_bug.cgi?id=148435 Patrick Luby changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3484 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153484] Spinning wheel in Calc on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=153484 Patrick Luby changed: What|Removed |Added CC||plub...@neooffice.org See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||8435 --- Comment #1 from Patrick Luby --- I may be wrong but the hang you see sound more like issue 152567. Issue 149807 was fixed in LibreOffice 7.4.4 so one way to figure out which issue you are seeing is to download LibreOffice 7.4.5 or 7.5.0 from the following link: https://www.libreoffice.org/download/download-libreoffice/ Does the hang still occur with either of those LibreOffice versions? If yes, then it is probably issue 152567 or a new bug. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 45705] DRAW/IMPRESS: New UNO commands for "Zoom in" and "Zoom out" of document canvas, to support keyboard zoom (comment 47)
https://bugs.documentfoundation.org/show_bug.cgi?id=45705 Rafael Lima changed: What|Removed |Added Status|NEW |ASSIGNED CC||rafael.palma.l...@gmail.com Assignee|libreoffice-b...@lists.free |rafael.palma.l...@gmail.com |desktop.org | --- Comment #51 from Rafael Lima --- >From what I understood of this ticket, we need a smoother SID_ZOOM_IN / SID_ZOOM_OUT in Impress/Draw. The proposed patch is here: https://gerrit.libreoffice.org/c/core/+/146825 This patch fixes the step size and makes it work as the zoom slider. One question remains. Should we create default shortcuts for these commands? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153556] New: Enhancement Request: Add option to disable dark theme
https://bugs.documentfoundation.org/show_bug.cgi?id=153556 Bug ID: 153556 Summary: Enhancement Request: Add option to disable dark theme Product: LibreOffice Version: 7.5.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: raptorhunter...@gmail.com Created attachment 185326 --> https://bugs.documentfoundation.org/attachment.cgi?id=185326=edit LibreOffice is dark despite not being on LibreOffice Dark Color Scheme When using a dark system theme in Windows settings, even with the LibreOffice color scheme set to "LibreOffice" and not "LibreOffice Dark", some aspects of the UI still turn dark. I wish there was a way to disable LibreOffice using the system theme for any colors because I want to have a dark system theme but a light LibreOffice theme and it automatically makes parts of the UI dark with no way to change it (see attached screenshot). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153542] Libreoffice calc 7.5 very slow and unresponsive when zooming in out (wheel mouse) on large spreadsheet unde Debian
https://bugs.documentfoundation.org/show_bug.cgi?id=153542 --- Comment #6 from thurston.m...@laposte.net --- i wonder if the issue is not described in detail here, since at that time, the problem was solved. https://gerrit.libreoffice.org/c/core/+/110538 cheers -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153555] LibreOffice respects Windows Dark Mode setting over its own Options
https://bugs.documentfoundation.org/show_bug.cgi?id=153555 --- Comment #2 from bikehel...@gmail.com --- Created attachment 185325 --> https://bugs.documentfoundation.org/attachment.cgi?id=185325=edit Google Search - Dark Mode Toggle -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153555] LibreOffice respects Windows Dark Mode setting over its own Options
https://bugs.documentfoundation.org/show_bug.cgi?id=153555 --- Comment #1 from bikehel...@gmail.com --- Created attachment 185324 --> https://bugs.documentfoundation.org/attachment.cgi?id=185324=edit 7.4.5.1 Dark Mode Text on Dark Background -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153555] New: LibreOffice respects Windows Dark Mode setting over its own Options
https://bugs.documentfoundation.org/show_bug.cgi?id=153555 Bug ID: 153555 Summary: LibreOffice respects Windows Dark Mode setting over its own Options Product: LibreOffice Version: 7.5.0.3 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: bikehel...@gmail.com Created attachment 185323 --> https://bugs.documentfoundation.org/attachment.cgi?id=185323=edit 7.5.0.3 Dark Icons on Dark Background Hello, Proposal: Popup a prompt to enter a Dark Mode theme when Dark Mode is detected on Windows, but otherwise stay in Light Mode. The problem is, LibreOffice respects the Windows/OS dark mode setting in 7.5.0.3 over its own options. If you go into Tools -> Options -> View and set a Light theme, it instead goes with the Windows Dark Mode setting, Dark Icons on Dark Background, Dark Text on Dark Background, and ignores what you choose. It's very hard to see buttons or read menu options. This makes 7.5.0.3 unusable over 7.4.5.1 and earlier versions for a lot of people. 7.4.5.1 also had the Dark Text on Dark Background issue, but earlier versions did not. I was fiddling with the settings on both and could not get it to behave, even though I did manage to activate other icons on the earlier version. This problem is currently plaguing a nearby low income seniors community. Lots of them have vision issues, and also old bad computers. (Acer Laptops more than a decade old are common. Some have burned out screens, so plugged in free old 17in LCDs from 2004, etc.) These people are prime users of free office software, as they only need to track some expenses and write an occasional letter, so it's not worthwhile to pay for anything. But now they can't see it if they upgrade, which they are prompted to when running it. These computers have very washed out screens while in light mode, where anything over RGB 224 blends together. So in order to be able to see scrollbars and move around webpages, dark mode gets enabled. Most Windows software ignores the flag and continues to function light while in dark mode. Even Google and Bing realized that assumption is a problem, and made it a memorized toggle on their search pages, with two simple clicks. They ignore the Windows setting. I suggest that LibreOffice default to Light Mode on Windows, and Popup a prompt to enter Dark Mode, similar to the tabbed UI popup. Assuming that Microsoft's OS settings are toggled because people like the mode is a dangerous assumption, and respecting it is building on top of quicksand. Microsoft frequently half-implements things, changes their implementation later without notice, etc; I believe that LibreOffice should take the setting as a suggestion rather than something to obey. This probably lines up better with actual use, too. Keep in mind that there are more seniors and more crappy computers out there than actual dark mode users, so the majority may have enabled it just because the other mode has worse visibility a lot of the time. Also, back when tons of Win10 upgrades were done, between 2015 and 2016, hundreds of millions of computers were flipped to pure Dark Mode. Not everyone bothered to change it back to what they had before. A lot of people just got used to it. (Especially common among novice computer users and many seniors.) Doesn't mean that they like it more than Light Mode, though. Is all of this dumb? Yep. Is having to second-guess Microsoft our reality? Yep. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143148] Use pragma once instead of include guards (Episode 2: Endgame)
https://bugs.documentfoundation.org/show_bug.cgi?id=143148 Buovjaga changed: What|Removed |Added Assignee|deepanshuraj...@gmail.com |libreoffice-b...@lists.free ||desktop.org --- Comment #80 from Buovjaga --- (In reply to Deepanshu Raj from comment #79) > please assign me this bug. I want to fix this bug Please remember our discussion: this is a multi-hacker task. You don't assign this to yourself. The point is to try a little bit and not do 4000 changes. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143148] Use pragma once instead of include guards (Episode 2: Endgame)
https://bugs.documentfoundation.org/show_bug.cgi?id=143148 Deepanshu Raj changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |deepanshuraj...@gmail.com |desktop.org | --- Comment #79 from Deepanshu Raj --- please assign me this bug. I want to fix this bug -- You are receiving this mail because: You are the assignee for the bug.
GSoC Project: Sidebar deck for quick find
Hello, I was recently taking a look again at the GSoC ideas list and I found out that it had been updated a bit since I last took a look at it a couple of weeks ago. I, unfortunately, wasn't able to find a mentor to help me with the previous idea (Improving Zoner Draw Filter), and also couldn't find a copy of Zoner Draw 2 for testing, which I was researching to implement so I went to look at the list again for inspiration. Then, the idea to implement Quick Find as a sidebar deck interested me. As I researched the idea further, I read through the discussion and implementation regarding this idea at: https://bugs.documentfoundation.org/show_bug.cgi?id=95405. I also looked at the mock-up at: https://bug-attachments.documentfoundation.org/attachment.cgi?id=184862 & thought that it was pretty close to my view of the project as well. The implementation of the idea seems pretty doable for a beginner like me who is new to open-source development as a whole. In the meanwhile, I've looked into the files srchdlg.cxx and navigatorpanel.ui for an initial idea of the implementation of the project. I think the ideal implementation of this idea would be to - 1) Create an additional find/replace section in sidebar 2) Leave the current find/replace dialogue in place (for the sake of user choice) 3) Show multiple matches of the searched keyword from the content in the sidebar and highlight them alongside with a yellow font color in the file, also allowing the user to cycle through them with a button click Firstly (and most importantly), Are there please any potential mentors who are willing to help me with this project? The GSoC ideas page mentioned potential mentors as *Jim Raykowski and **Heiko Tietze, *can somebody please contact them and ask if they're interested in this project? Are there any foreseeable roadblocks or challenges to the execution of this idea? In which area should I start focusing my research to start working on the document to successfully implement this idea as part of GSoC 2023? Is anyone else currently aiming to implement this idea at LibreOffice or in the LibreOffice open-source community? Lastly, are there any other tips or thoughts regarding this that you would like to give me? Thanking for your time and consideration, Siddharth K
[Libreoffice-bugs] [Bug 153549] Rename Tools > "Chapter Numbering" to "Heading Numbering"
https://bugs.documentfoundation.org/show_bug.cgi?id=153549 --- Comment #1 from Eyal Rozenberg --- Repeating what I've wrote elsewhere: This would certainly be better than Chapter Numbering, seeing how LO Writer doesn't have "chapters".. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153554] New: Crash when closing LibreOffice opened via SDK
https://bugs.documentfoundation.org/show_bug.cgi?id=153554 Bug ID: 153554 Summary: Crash when closing LibreOffice opened via SDK Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: sdk Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: hoss...@libreoffice.org Description: When opening a LibreOffice process via SDK bootstrapping, closing a window can lead to LibreOffice crash. Steps to Reproduce: 1. Compile LibreOffice from sources. 2. Copy the HelloTextTableShape.py from here: https://gerrit.libreoffice.org/c/core/+/146819/1/odk/examples/DevelopersGuide/FirstSteps/HelloTextTableShape.py 3. Invoke $ instdir/program/python odk/examples/DevelopersGuide/FirstSteps/HelloTextTableShape.py 4. After the 3 LibreOffice windows are opened, close one of them. It leads to crash. Actual Results: Crash. You can open LibreOffice again to see the crash recovery window: $ instdir/program/soffice Expected Results: LibrOffice should not crash. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: a942e6e5ecfdd9ff83fc7febb8234c8f0e2813db CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: fa-IR (fa_IR); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153553] New: Make the installation easier by omitting unnecessary checks for standard program and restart
https://bugs.documentfoundation.org/show_bug.cgi?id=153553 Bug ID: 153553 Summary: Make the installation easier by omitting unnecessary checks for standard program and restart Product: LibreOffice Version: 3.3.0 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Installation Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: stehlam...@arcor.de Description: I had LibreOffice in version 7.4.2.3 and wished to upgrade to version 7.5.0.3. LibreOffice was already the standard program to open Microsoft Office Files. Therefore, the installation step to choose the default program for Microsoft Office files should only appear if LibreOffice is not already the standard program for all Microsoft Office file type. In addition, only those items should be displayed which are not opened by LibreOffice by default. A second unnecessary thing: If it occurs that there are things to do during installation which require a restart, the installation routine should follow the guideline: Ask only once. At the moment, I am asked three times that proceeding would require a restart -- despite I have given the allowance to restart already after being asked the first time. Since I had not the time to test all installations, the "affected version" property gives the earliest possible. Steps to Reproduce: Install LibreOffice. Actual Results: Unnecessary step: file-type association Being informed that continuing requires restart multiple times. Expected Results: File-type association only asked if necessary. Being informed that continuing requires restart one time. Reproducible: Always User Profile Reset: No Additional Info: -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138653] SVG images look extremely bad after DOCX export or compress
https://bugs.documentfoundation.org/show_bug.cgi?id=138653 --- Comment #9 from Roland Baudin --- Created attachment 185322 --> https://bugs.documentfoundation.org/attachment.cgi?id=185322=edit Rendering in MS Word 2016 (screenshot) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138653] SVG images look extremely bad after DOCX export or compress
https://bugs.documentfoundation.org/show_bug.cgi?id=138653 --- Comment #8 from Roland Baudin --- Created attachment 185321 --> https://bugs.documentfoundation.org/attachment.cgi?id=185321=edit SVG graphic example (simple equation) -- You are receiving this mail because: You are the assignee for the bug.
