[Libreoffice-bugs] [Bug 153718] EDITING In a Calc table, the default document language setting is not honored throughout the table. Instead, some cells are set to English(USA)
https://bugs.documentfoundation.org/show_bug.cgi?id=153718 ady changed: What|Removed |Added Attachment #186296|application/xml |application/vnd.oasis.opend mime type||ocument.spreadsheet -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 91130] Smaller default font name list
https://bugs.documentfoundation.org/show_bug.cgi?id=91130 --- Comment #52 from robgrune --- suggestions: 1/ Package LO as a stand-alone, all-inclusive flatpak. To include all help files, and a very limited set of generic fonts (eg Arial and Times). To exclude other fonts installed by gnome. 2/ At installation, users choose their Language Pack. This will ensure English users do not install fonts for Gujurati, Chinese, Japanese, Tamil, etc. 3/ Add a menu macro that enable users to EASILY add or remove fonts either: they have downloaded from the web; or, installed from the LO site. 4/ Alter the LO drop down list to enable users to define, choose, label font categories. Example of Categories: Apple fonts; MS fonts; Fancy fonts; Foreign language fonts; etc. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154041] Missing borders of toolbars ("blended" toolbar w/ work area or other toolbar)
https://bugs.documentfoundation.org/show_bug.cgi?id=154041 --- Comment #6 from scorpios...@abv.bg --- > scorpiosoft, can you please share the information from Help > About > LibreOffice? Stéphane Guillou, here it is: Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 8; OS: Windows 10.0 Build 19041; UI render: Skia/Vulkan; VCL: win Locale: bg-BG (bg_BG); UI: en-US Calc: threaded(In reply to Stéphane Guillou (stragu) from comment #5) > What kind of OS-level theme are you using? Sorry ? I am not sure I understand the question. In dark mode I am using theme with name "Adapta" (obtained from here https://www.deviantart.com/niivu/art/Adapta-for-Windows-10-675581778 ). In light mode - default Windows theme. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 93259] Cannot correctly read cell alignments on simple spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=93259 Aron Budea changed: What|Removed |Added Hardware|x86-64 (AMD64) |All Severity|major |normal Blocks||140202 CC||aron.bu...@gmail.com Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=140202 [Bug 140202] [META] Issues with files in MS Office formats created by external producers (not MS Office) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140202] [META] Issues with files in MS Office formats created by external producers (not MS Office)
https://bugs.documentfoundation.org/show_bug.cgi?id=140202 Aron Budea changed: What|Removed |Added Depends on||93259 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=93259 [Bug 93259] Cannot correctly read cell alignments on simple spreadsheet -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140202] [META] Issues with files in MS Office formats created by external producers (not MS Office)
https://bugs.documentfoundation.org/show_bug.cgi?id=140202 Aron Budea changed: What|Removed |Added Depends on||140116 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=140116 [Bug 140116] XLS file not opening in Libo after encrypting it with Biff8 encryption in Apache POI -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140116] XLS file not opening in Libo after encrypting it with Biff8 encryption in Apache POI
https://bugs.documentfoundation.org/show_bug.cgi?id=140116 Aron Budea changed: What|Removed |Added Blocks||140202 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=140202 [Bug 140202] [META] Issues with files in MS Office formats created by external producers (not MS Office) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 119060] [META] XLSX (OOXML) ActiveX and Legacy form control related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=119060 Aron Budea changed: What|Removed |Added Depends on|154463 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154463 [Bug 154463] Typing dots in Text Form Field crashes Writer -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104523] [META] DOCX (OOXML) ActiveX and Legacy form control related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=104523 Aron Budea changed: What|Removed |Added Depends on||154463 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154463 [Bug 154463] Typing dots in Text Form Field crashes Writer -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154463] Typing dots in Text Form Field crashes Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=154463 Aron Budea changed: What|Removed |Added Keywords||haveBacktrace Blocks|119060 |104523 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=104523 [Bug 104523] [META] DOCX (OOXML) ActiveX and Legacy form control related issues https://bugs.documentfoundation.org/show_bug.cgi?id=119060 [Bug 119060] [META] XLSX (OOXML) ActiveX and Legacy form control related issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154463] Typing dots in Text Form Field crashes Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=154463 --- Comment #1 from Aron Budea --- Created attachment 186307 --> https://bugs.documentfoundation.org/attachment.cgi?id=186307=edit Backtrace -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 119060] [META] XLSX (OOXML) ActiveX and Legacy form control related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=119060 Aron Budea changed: What|Removed |Added Depends on||154463 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154463 [Bug 154463] Typing dots in Text Form Field crashes Writer -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105537] [META] Assertion failed crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=105537 Aron Budea changed: What|Removed |Added Depends on||154463 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154463 [Bug 154463] Typing dots in Text Form Field crashes Writer -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154463] New: Typing dots in Text Form Field crashes Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=154463 Bug ID: 154463 Summary: Typing dots in Text Form Field crashes Writer Product: LibreOffice Version: 6.4.0.3 release Hardware: All OS: All Status: UNCONFIRMED Keywords: bibisected, bisected, regression Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: aron.bu...@gmail.com CC: xiscofa...@libreoffice.org Blocks: 105537, 119060 Created attachment 186306 --> https://bugs.documentfoundation.org/attachment.cgi?id=186306=edit Sample DOCX The attached document was created in Writer by: - first enabling "Reorganize Form menu for Microsoft compatibility" in Tools -> Options..., LibreOffice Writer -> Compatibility, - adding a Form -> Legacy Form Fields -> Text Form Field, - saving as DOCX. Another prerequisite is that Tools -> AutoCorrect is enabled. Open the sample, click into the field, and type a bunch of dots (about 4-6). => Crash. Crash report: https://crashreport.libreoffice.org/stats/crash_details/0a8cc30e-d1ba-409b-b2d8-33e8b581e6c7 (a crash report taken on Win with LO 7.5.0.3 should be here, but it isn't for some reason, Xisco, do you know if something is wrong with the crash report server?) A debug build fails with the following assertion: sw/source/core/crsr/bookmark.cxx:89: SwPosition sw::mark::FindFieldSep(const sw::mark::IFieldmark&): Assertion `0 <= nFields' failed Observed in LO 7.6.0.0.alpha0+ (7a7eb4aa21ca0c83db825fe8d5a5278611b391d8) / Ubuntu. This is a regression from the following commit, bibisected using repo bibisect-linux-64-6.4: https://cgit.freedesktop.org/libreoffice/core/commit/?id=b522fc0646915d4da94df38dd249c88b28f25be7 author Michael Stahl 2019-09-24 18:11:45 +0200 committer Michael Stahl 2019-10-23 12:47:40 +0200 sw: maintain fieldmarks in DeleteRange()/DeleteAndJoin()/ReplaceRange() Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=105537 [Bug 105537] [META] Assertion failed crashes https://bugs.documentfoundation.org/show_bug.cgi?id=119060 [Bug 119060] [META] XLSX (OOXML) ActiveX and Legacy form control related issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154187] Allow for static assignment of comment background color to a user
https://bugs.documentfoundation.org/show_bug.cgi?id=154187 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 154218] variable and user field input field mishandles datetime when a locale is active
https://bugs.documentfoundation.org/show_bug.cgi?id=154218 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 154217] Fields variables (user field and variable) cannot format value for update as date (or similar)
https://bugs.documentfoundation.org/show_bug.cgi?id=154217 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 154209] Using "Update entry from selection" button in "Edit Index Entry" switches to "Insert" mode
https://bugs.documentfoundation.org/show_bug.cgi?id=154209 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 150705] Paste contents in Draw looses accents
https://bugs.documentfoundation.org/show_bug.cgi?id=150705 --- Comment #4 from QA Administrators --- Dear Olivier Hallot, 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 154198] [Writer] The second and the before-final vertical lines are hidden in RTL documents.
https://bugs.documentfoundation.org/show_bug.cgi?id=154198 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 154216] Scroll region window object; capture tools inhibited
https://bugs.documentfoundation.org/show_bug.cgi?id=154216 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 154201] Grid resolution not correctly restored from opened document
https://bugs.documentfoundation.org/show_bug.cgi?id=154201 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 154212] A Frame with a Heading disrupts the "Move Chapter Up/Down" in Navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=154212 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 149751] Libreoffice freeze at first startup in Windows 10
https://bugs.documentfoundation.org/show_bug.cgi?id=149751 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149751] Libreoffice freeze at first startup in Windows 10
https://bugs.documentfoundation.org/show_bug.cgi?id=149751 --- Comment #11 from QA Administrators --- Dear siapec, 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 147560] Writer Crashes with multi page documents using numbering outline (different headings) and inserted pictures.
https://bugs.documentfoundation.org/show_bug.cgi?id=147560 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147560] Writer Crashes with multi page documents using numbering outline (different headings) and inserted pictures.
https://bugs.documentfoundation.org/show_bug.cgi?id=147560 --- Comment #7 from QA Administrators --- Dear JCook, 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 101912] [META] Accessibility (a11y) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=101912 Bug 101912 depends on bug 141583, which changed state. Bug 141583 Summary: Rotary switch for side margin setting not accessible https://bugs.documentfoundation.org/show_bug.cgi?id=141583 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141583] Rotary switch for side margin setting not accessible
https://bugs.documentfoundation.org/show_bug.cgi?id=141583 --- Comment #4 from QA Administrators --- Dear juergenkohler23, 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 141167] NVDA does not announce the entries in the "Labels" dialogue box
https://bugs.documentfoundation.org/show_bug.cgi?id=141167 --- Comment #4 from QA Administrators --- Dear Peter Franke, 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 101912] [META] Accessibility (a11y) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=101912 Bug 101912 depends on bug 141167, which changed state. Bug 141167 Summary: NVDA does not announce the entries in the "Labels" dialogue box https://bugs.documentfoundation.org/show_bug.cgi?id=141167 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 93117] LibreOffice freezes when trying to access/open/read/write documents on NFS mounts
https://bugs.documentfoundation.org/show_bug.cgi?id=93117 --- Comment #10 from QA Administrators --- Dear Basic Six, 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 151236] Copy-Paste only transfers plain-text
https://bugs.documentfoundation.org/show_bug.cgi?id=151236 --- Comment #8 from QA Administrators --- Dear Cesar Izurieta, 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 144994] libreoffice crashes with kf5-wayland when LanguageTool extension is in use
https://bugs.documentfoundation.org/show_bug.cgi?id=144994 --- Comment #33 from QA Administrators --- Dear giors_00, 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 95438] SLIDESHOW/VIEWING: Misrendered SVG in presenter console
https://bugs.documentfoundation.org/show_bug.cgi?id=95438 --- Comment #8 from QA Administrators --- Dear Dr. David Alan Gilbert, 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 90756] Impress incorrectly caches linked images on active slide linux+windows
https://bugs.documentfoundation.org/show_bug.cgi?id=90756 --- Comment #4 from QA Administrators --- Dear jebsolutions, 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 71462] VIEWING: Strange blank line in table appear at merged cell
https://bugs.documentfoundation.org/show_bug.cgi?id=71462 --- Comment #12 from QA Administrators --- Dear Luiz Angelo Daros de Luca, 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 67567] FILESAVE: if rotated shaped is grouped, saving as DOC and openening in Word does not show that rotation
https://bugs.documentfoundation.org/show_bug.cgi?id=67567 --- Comment #12 from QA Administrators --- Dear Ljiljan, 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 141320] [RTF] .rtf Rich Text: broken file error due to inserted formula
https://bugs.documentfoundation.org/show_bug.cgi?id=141320 --- Comment #2 from QA Administrators --- Dear mail-bugzilla, 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 141209] URP bridge disposed by invalid UTF-16 (lone low surrogate) in Writer document
https://bugs.documentfoundation.org/show_bug.cgi?id=141209 --- Comment #3 from QA Administrators --- Dear Thomas K, 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 141031] Context Menu doesn't update target on right click in Form browser
https://bugs.documentfoundation.org/show_bug.cgi?id=141031 --- Comment #3 from QA Administrators --- Dear Matheod, 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 132611] FILESAVE: DOCX: Incorrect spacing in footnote after RT (extra CR added b/c of table in footnote)
https://bugs.documentfoundation.org/show_bug.cgi?id=132611 --- Comment #7 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 134248] Jars published on Maven have wrong classpath / Bootstrap does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=134248 --- Comment #9 from QA Administrators --- Dear Alexander Veit, 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 123813] AutoInput in cell doesn't highlight for duplicate values if the gap between possible duplicates is greater than 200 rows.
https://bugs.documentfoundation.org/show_bug.cgi?id=123813 --- Comment #10 from QA Administrators --- Dear Giorgi, 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 116651] EDITING: possible to delete a slide in read-only mode or when edit mode is off
https://bugs.documentfoundation.org/show_bug.cgi?id=116651 --- Comment #6 from QA Administrators --- Dear Vincent Bossier, 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 137543] Add a LET function into Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=137543 Dan Dascalescu changed: What|Removed |Added CC||ddascalescu+freedesktop@gma ||il.com --- Comment #4 from Dan Dascalescu --- This would be very useful to shorten formulas that repeat the same quantity, such as outputting both an absolute and a percentage change between two values. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151338] Change label of "Position and Size" command depending on context
https://bugs.documentfoundation.org/show_bug.cgi?id=151338 --- Comment #9 from Rafael Lima --- Created attachment 186305 --> https://bugs.documentfoundation.org/attachment.cgi?id=186305=edit Screenshot of the proposed fix So I changed the command label for "Table Position and Size" only for this popup. Notice that I also rearranged the order so that commands that are applicable to the table (and not to the selection) are grouped together. Patch here: https://gerrit.libreoffice.org/c/core/+/149700 I just don't know if the string I added will be caught for translation. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103030] [META] Navigator sidebar deck and floating window
https://bugs.documentfoundation.org/show_bug.cgi?id=103030 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||154211 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154211 [Bug 154211] Allow selecting a range between current cursor position and an element in Navigator with Shift + click (EDITING) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 154211] Allow selecting a range between current cursor position and an element in Navigator with Shift + click (EDITING)
https://bugs.documentfoundation.org/show_bug.cgi?id=154211 Stéphane Guillou (stragu) changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |NEW OS|Windows (All) |All Blocks||103030 Version|7.5.1.2 release |Inherited From OOo Ever confirmed|0 |1 Summary|Selecting an area between |Allow selecting a range |current cursor position and |between current cursor |a point in Navigator|position and an element in |(EDITING) |Navigator with Shift + ||click (EDITING) Hardware|x86-64 (AMD64) |All --- Comment #3 from Stéphane Guillou (stragu) --- That could be an interesting feature, but would need to be only possible for some elements in the Navigator (like headings, fields, bookmarks, hyperlinks...), and we would need to check if it interferes in any way with potential multiselection implemented for bug 129610. Copying UX team in for their opinion. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103030 [Bug 103030] [META] Navigator sidebar deck and floating window -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 154211] Allow selecting a range between current cursor position and an element in Navigator with Shift + click (EDITING)
https://bugs.documentfoundation.org/show_bug.cgi?id=154211 Stéphane Guillou (stragu) changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |NEW OS|Windows (All) |All Blocks||103030 Version|7.5.1.2 release |Inherited From OOo Ever confirmed|0 |1 Summary|Selecting an area between |Allow selecting a range |current cursor position and |between current cursor |a point in Navigator|position and an element in |(EDITING) |Navigator with Shift + ||click (EDITING) Hardware|x86-64 (AMD64) |All --- Comment #3 from Stéphane Guillou (stragu) --- That could be an interesting feature, but would need to be only possible for some elements in the Navigator (like headings, fields, bookmarks, hyperlinks...), and we would need to check if it interferes in any way with potential multiselection implemented for bug 129610. Copying UX team in for their opinion. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103030 [Bug 103030] [META] Navigator sidebar deck and floating window -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154211] Selecting an area between current cursor position and a point in Navigator (EDITING)
https://bugs.documentfoundation.org/show_bug.cgi?id=154211 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||9610 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140969] UI: All selected items in canvas should be highlighted in navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=140969 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||9610 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129610] Allow multiselecting of objects in Navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=129610 Stéphane Guillou (stragu) changed: What|Removed |Added Version|unspecified |Inherited From OOo See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||0969, ||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4211 CC||stephane.guillou@libreoffic ||e.org -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 90244] SIDEBAR: Enhancing Navigator in Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=90244 Bug 90244 depends on bug 111839, which changed state. Bug 111839 Summary: Navigator: enhanchement: Select shapes on slide from navigator https://bugs.documentfoundation.org/show_bug.cgi?id=111839 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 111839] Navigator: enhanchement: Select shapes on slide from navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=111839 Stéphane Guillou (stragu) changed: What|Removed |Added Status|NEW |RESOLVED CC||stephane.guillou@libreoffic ||e.org Resolution|--- |DUPLICATE --- Comment #3 from Stéphane Guillou (stragu) --- Fixed by same commits as bug 62851, so marking as duplicate. *** This bug has been marked as a duplicate of bug 62851 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 62851] UI: Shapes without name cannot be selected via Navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=62851 Stéphane Guillou (stragu) changed: What|Removed |Added CC||zolnaitamas2...@gmail.com --- Comment #18 from Stéphane Guillou (stragu) --- *** Bug 111839 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 62851] UI: Shapes without name cannot be selected via Navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=62851 Stéphane Guillou (stragu) changed: What|Removed |Added Whiteboard||target:7.2.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154462] New: BASIC The ScriptForge.SF_FileSystem.pickfile macro runs once, then returns error
https://bugs.documentfoundation.org/show_bug.cgi?id=154462 Bug ID: 154462 Summary: BASIC The ScriptForge.SF_FileSystem.pickfile macro runs once, then returns error Product: LibreOffice Version: 7.3.7.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: merdemostf...@gmail.com Created attachment 186304 --> https://bugs.documentfoundation.org/attachment.cgi?id=186304=edit error message generated by ScriptForge.SF_FileSystem.pickfile() This code evinces the error:- sub pickafile() f = ScriptForge.SF_FileSystem.pickfile() print(f) End Sub -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: extensions/uiconfig
extensions/uiconfig/spropctrlr/ui/labelselectiondialog.ui | 10 ++ 1 file changed, 10 insertions(+) New commits: commit 9c7d3ce813c761b116232bc291e2737c59d383da Author: Olivier Hallot AuthorDate: Wed Mar 29 13:27:50 2023 -0300 Commit: Olivier Hallot CommitDate: Wed Mar 29 22:18:04 2023 + Add extended tip to labelselectiondialog.ui Change-Id: I6b4d0a30c2a1a51694770ecd02eea3cf3677b5eb Reviewed-on: https://gerrit.libreoffice.org/c/core/+/149732 Tested-by: Jenkins Reviewed-by: Olivier Hallot diff --git a/extensions/uiconfig/spropctrlr/ui/labelselectiondialog.ui b/extensions/uiconfig/spropctrlr/ui/labelselectiondialog.ui index 012a6fc13c3a..f73b01361c94 100644 --- a/extensions/uiconfig/spropctrlr/ui/labelselectiondialog.ui +++ b/extensions/uiconfig/spropctrlr/ui/labelselectiondialog.ui @@ -165,6 +165,11 @@ False True True + + +Check the No assignment box to remove the link between a control and the assigned label field. + + False @@ -186,5 +191,10 @@ cancel help + + +Specifies the source for the label of the control. + +
[Libreoffice-bugs] [Bug 154461] pdf export of ✔ (U+2714 HEAVY CHECK MARK) in Noto Color Emoji produces blank PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=154461 --- Comment #5 from Daniel Kahn Gillmor --- Created attachment 186303 --> https://bugs.documentfoundation.org/attachment.cgi?id=186303=edit Evince properties page describing fonts (no glyphs explicitly missing) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154461] pdf export of ✔ (U+2714 HEAVY CHECK MARK) in Noto Color Emoji produces blank PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=154461 --- Comment #4 from Daniel Kahn Gillmor --- Created attachment 186302 --> https://bugs.documentfoundation.org/attachment.cgi?id=186302=edit Evince screenshot rendering PDF (check mark invisible) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154461] pdf export of ✔ (U+2714 HEAVY CHECK MARK) in Noto Color Emoji produces blank PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=154461 --- Comment #3 from Daniel Kahn Gillmor --- Created attachment 186301 --> https://bugs.documentfoundation.org/attachment.cgi?id=186301=edit LibreOffice screenshot (check mark visible) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154461] pdf export of ✔ (U+2714 HEAVY CHECK MARK) in Noto Color Emoji produces blank PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=154461 --- Comment #2 from Daniel Kahn Gillmor --- Created attachment 186300 --> https://bugs.documentfoundation.org/attachment.cgi?id=186300=edit source Impress presentation -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154461] pdf export of ✔ (U+2714 HEAVY CHECK MARK) in Noto Color Emoji produces blank PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=154461 --- Comment #1 from Daniel Kahn Gillmor --- Created attachment 186299 --> https://bugs.documentfoundation.org/attachment.cgi?id=186299=edit resulting PDF -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154461] New: pdf export of ✔ (U+2714 HEAVY CHECK MARK) in Noto Color Emoji produces blank PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=154461 Bug ID: 154461 Summary: pdf export of ✔ (U+2714 HEAVY CHECK MARK) in Noto Color Emoji produces blank PDF Product: LibreOffice Version: 7.4.5.1 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Printing and PDF export Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: d...@fifthhorseman.net Description: I made an Impress presentation with a single character in it (✔, U+2714 HEAVY CHECK MARK). the glyph was rendered in the Noto Color Emoji font. I exported it to PDF and the resulting PDF looks blank. highlighting the pdf shows that there is an invisible character there, and inspecting the pdf suggests that Poppler knows that the character is present, and the font subset is embedded. but nothing is visible. I suppose it's possible that this is a bug in Poppler (in PDF rendering, that is), but i suspect it's a bug in LibreOffice Impress. Steps to Reproduce: 1. create an impress document 2. put a single ✔ character (U+2714 HEAVY CHECK MARK) 3. export to pdf Actual Results: PDF with invisible character Expected Results: PDF with visible character Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.4.5.1 / LibreOffice Community Build ID: 40(Build:1) CPU threads: 4; OS: Linux 6.1; UI render: default; VCL: x11 Locale: en-US (en_US.UTF-8); UI: en-US Debian package version: 4:7.4.5-2 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154041] Missing borders of toolbars ("blended" toolbar w/ work area or other toolbar)
https://bugs.documentfoundation.org/show_bug.cgi?id=154041 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||stephane.guillou@libreoffic ||e.org --- Comment #5 from Stéphane Guillou (stragu) --- scorpiosoft, can you please share the information from Help > About LibreOffice? What kind of OS-level theme are you using? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 62867] Word wrap does not work properly when image is left of the left margin.
https://bugs.documentfoundation.org/show_bug.cgi?id=62867 --- Comment #15 from Justin L --- I attempted to solve it with https://gerrit.libreoffice.org/c/core/+/149665, but failed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107656] [META] Frame bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107656 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||154409 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154409 [Bug 154409] A single click on a shape/image with frame should select the frame, instead of the image -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114426] [META] Caption bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=114426 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||154409 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154409 [Bug 154409] A single click on a shape/image with frame should select the frame, instead of the image -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154409] A single click on a shape/image with frame should select the frame, instead of the image
https://bugs.documentfoundation.org/show_bug.cgi?id=154409 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||114426, 107656 Version|7.6.0.0 alpha0+ Master |Inherited From OOo Severity|normal |enhancement Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #6 from Stéphane Guillou (stragu) --- I agree with the idea here, as long as we keep the direct access to caption text. It would help avoid quite a few mishaps, as Telesto listed. Seems there is widespread agreement on this enhancement, so setting to new. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107656 [Bug 107656] [META] Frame bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=114426 [Bug 114426] [META] Caption bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154460] New: Unclear sentence: "Change typewriter apostrophe, single quotation marks and correct double primes."
https://bugs.documentfoundation.org/show_bug.cgi?id=154460 Bug ID: 154460 Summary: Unclear sentence: "Change typewriter apostrophe, single quotation marks and correct double primes." Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: minor Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tuomas.hiet...@iki.fi Description: The string "Change typewriter apostrophe, single quotation marks and correct double primes." occurs two times in LO. It's not correct English and the meaning is somewhat unclear. "Change typewriter apostrophe" - change into what? I assume typographically correct apostrophe: https://en.wikipedia.org/wiki/Apostrophe#Typographic_form "single quotation marks" - what are these being changed into? "correct double primes"- I assume this means changing ASCII double quotation marks into double prime Unicode characters (U+2033). Steps to Reproduce: 1. See https://translations.documentfoundation.org/translate/libo_ui-master/dictionariesendialog/en/?checksum=b58b6639d4a0d406 and https://translations.documentfoundation.org/translate/libo_ui-master/dictionariespt_brdialog/en/?checksum=be0cc6427d743477 Actual Results: The sentence is unclear. Expected Results: The sentence is correct English and explains better what the option actually does. Reproducible: Always User Profile Reset: No Additional Info: n/a -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154442] _LO_Writer_kolontitul
https://bugs.documentfoundation.org/show_bug.cgi?id=154442 --- Comment #9 from Mike Kaganski --- Роман: в дополнение к Вашему багрепорт здесь, если Вам нужна помощь по правильному форматированию колонтитулов (верхний колонтитул в английском называется header, в отличие от заголовка, который heading), то Вы можете задать вопрос на https://forumooo.ru. A native-language community support in Russian is available at https://forumooo.ru. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154459] New: "Change three dots with ellipsis." is not correct English
https://bugs.documentfoundation.org/show_bug.cgi?id=154459 Bug ID: 154459 Summary: "Change three dots with ellipsis." is not correct English Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: trivial Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tuomas.hiet...@iki.fi Description: The string "Change three dots with ellipsis." which occurs in two places in LO is not correct English. Change to "Replace three dots with ellipsis". Steps to Reproduce: 1. See https://translations.documentfoundation.org/translate/libo_ui-master/dictionariesendialog/en/?checksum=6d36ee69f25efdbe and https://translations.documentfoundation.org/translate/libo_ui-master/dictionariespt_brdialog/en/?checksum=8a8defd14f45906a Actual Results: The sentence is not correct English. Expected Results: The sentence is correct English. Reproducible: Always User Profile Reset: No Additional Info: n/a -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153718] EDITING In a Calc table, the default document language setting is not honored throughout the table. Instead, some cells are set to English(USA)
https://bugs.documentfoundation.org/show_bug.cgi?id=153718 --- Comment #7 from Ben Opp --- Created attachment 186298 --> https://bugs.documentfoundation.org/attachment.cgi?id=186298=edit clicking on document language in bottom UI panel, these are the choices available 4 more German dictionaries and English(USA) dictionary are installed, but not available for selecting. There is a mismatch between the installed dictionaries and the ones I can set as document language -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153718] EDITING In a Calc table, the default document language setting is not honored throughout the table. Instead, some cells are set to English(USA)
https://bugs.documentfoundation.org/show_bug.cgi?id=153718 --- Comment #6 from Ben Opp --- Created attachment 186297 --> https://bugs.documentfoundation.org/attachment.cgi?id=186297=edit available dictionaries in spellchecking options All German dictionaries are installed (Austria, Germany, Switzerland, Luxemburg, Liechtenstein, Belgium) but are missing from the list. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153718] EDITING In a Calc table, the default document language setting is not honored throughout the table. Instead, some cells are set to English(USA)
https://bugs.documentfoundation.org/show_bug.cgi?id=153718 --- Comment #5 from ben@eml.cc --- Uploaded the spreadsheet. I don't know if I marked the content type correctly, it's an .ods file creates with LO Calc. I also noticed something interesting in the language settings, will add screenshots -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153718] EDITING In a Calc table, the default document language setting is not honored throughout the table. Instead, some cells are set to English(USA)
https://bugs.documentfoundation.org/show_bug.cgi?id=153718 ben@eml.cc 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 153718] EDITING In a Calc table, the default document language setting is not honored throughout the table. Instead, some cells are set to English(USA)
https://bugs.documentfoundation.org/show_bug.cgi?id=153718 --- Comment #4 from ben@eml.cc --- Created attachment 186296 --> https://bugs.documentfoundation.org/attachment.cgi?id=186296=edit This sample document exhibited the described behavior, but does not when I open it now. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154442] _LO_Writer_kolontitul
https://bugs.documentfoundation.org/show_bug.cgi?id=154442 --- Comment #8 from Roman --- (In reply to Mike Kaganski from comment #6) > (In reply to V Stuart Foote from comment #5) > > I don't see why would we need to revisit it, or how should it be handled > here. It's just an incorrect expectation from OP, that header/footer are > part of margins: it is not how ODF page model is designed. > > In ODF, margins are space where *no* part of document is present. And that > is fixed: no matter how you try, header/footer/page body won't eat it. > > In other applications, where margins are for headers/footers, it's just a > fake, and when headers increase in size, they start eating page body. So > there, there is no guarantee that page body is not affected, just a > different point of surprise. > > There *can* be a convenience tool, that allows "placing" header/footer "on > margins" by decreasing them, and making the header/footer take that space, > in one action. It would be an enhancement request for such a convenience > tool. See LOkol-prim3. This thing must be raised and forbid it to raise and lower the margins of the page. Also, you see the interval below it to the fields, if you set it to 0, then the page number will be directly above the text, which is not beautiful. The title I didn't understand. If these are the headings that have styles and are used in the table of contents - this is completely different. Смотрим LOkol-prim3. Вот эту штуку надо поднять и запретить ей подымать и опускать поля страницы. Также вы под ней видите интервал до полей, если его поставить 0 то номер страницы будет находиться прям над текстом, что не красиво. Заголовок чего я так и не понял. Если это те заголовки на которые есть стили и используются в оглавлениях - это совершенно иное. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154442] _LO_Writer_kolontitul
https://bugs.documentfoundation.org/show_bug.cgi?id=154442 --- Comment #7 from Roman --- Created attachment 186295 --> https://bugs.documentfoundation.org/attachment.cgi?id=186295=edit LOkol-prim3 -- You are receiving this mail because: You are the assignee for the bug.
combining proposal for ODF for multiple-color gradient and theme colors
Hi all, hi Armin, hi Tomaž, attached is a draft proposal for ODF. It covers multi-color gradient and theme colors. It includes the intended final RelaxNG. Of cause in the meantime all new attributes and elements need to be in loext-namespace. That is not included in the draft. The draft describes the way I suggest to go. What do you think? One question for example is, whether to export the 12 scheme colors as individual elements or all together as list. [I know it is a lot of work to implement such. I'm willing to help implementing it after we have agreed on the goal.] Kind regards, Regina ODF draft multi-color gradient plus theme v1.odt Description: application/vnd.oasis.opendocument.text
[Libreoffice-bugs] [Bug 154442] _LO_Writer_kolontitul
https://bugs.documentfoundation.org/show_bug.cgi?id=154442 --- Comment #6 from Mike Kaganski --- (In reply to V Stuart Foote from comment #5) I don't see why would we need to revisit it, or how should it be handled here. It's just an incorrect expectation from OP, that header/footer are part of margins: it is not how ODF page model is designed. In ODF, margins are space where *no* part of document is present. And that is fixed: no matter how you try, header/footer/page body won't eat it. In other applications, where margins are for headers/footers, it's just a fake, and when headers increase in size, they start eating page body. So there, there is no guarantee that page body is not affected, just a different point of surprise. There *can* be a convenience tool, that allows "placing" header/footer "on margins" by decreasing them, and making the header/footer take that space, in one action. It would be an enhancement request for such a convenience tool. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153899] Clone format of unmerged cells breaks up merging, applies to first unmerged cell only
https://bugs.documentfoundation.org/show_bug.cgi?id=153899 --- Comment #10 from Eyal Rozenberg --- This was discussed in the design meeting this evening, but - not in a satisfactory manner IMHO. Here's what the minutes say: > + merging cells with the keep option does exactly this, we > must not format hidden cells this bug does not regard the merging action, so either this sentence is incorrect or I misunderstand it. > + copying/cloning merged cells takes merge state into account, > however, applying a format via cell style, which is the supposed > workflow does not I'm sorry, that does not make sense. This bug is about "clone formatting". If it takes the merge state into account, the answer to Q1 is affirmative. Now, what about Q2? > + cloning the merged state is a convenience feature I don't understand this sentence. Cloning is a feature in LO calc, and you guys decided it also applies the merged or unmerged state. What does it matter whether cloning is a "convenience feature" or not? Given your position, the obvious decision is for the format to apply to all unmerged cells. I haven't read any argument for the alternative in the minutes. And thus I don't understand why you concluded > => WF/NAB rather than will-fix, is-a-bug. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153899] Clone format of unmerged cells breaks up merging, applies to first unmerged cell only
https://bugs.documentfoundation.org/show_bug.cgi?id=153899 --- Comment #10 from Eyal Rozenberg --- This was discussed in the design meeting this evening, but - not in a satisfactory manner IMHO. Here's what the minutes say: > + merging cells with the keep option does exactly this, we > must not format hidden cells this bug does not regard the merging action, so either this sentence is incorrect or I misunderstand it. > + copying/cloning merged cells takes merge state into account, > however, applying a format via cell style, which is the supposed > workflow does not I'm sorry, that does not make sense. This bug is about "clone formatting". If it takes the merge state into account, the answer to Q1 is affirmative. Now, what about Q2? > + cloning the merged state is a convenience feature I don't understand this sentence. Cloning is a feature in LO calc, and you guys decided it also applies the merged or unmerged state. What does it matter whether cloning is a "convenience feature" or not? Given your position, the obvious decision is for the format to apply to all unmerged cells. I haven't read any argument for the alternative in the minutes. And thus I don't understand why you concluded > => WF/NAB rather than will-fix, is-a-bug. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 33304] Header / Footer should be inserted into margin, not into text body
https://bugs.documentfoundation.org/show_bug.cgi?id=33304 V Stuart Foote changed: What|Removed |Added URL||https://ask.libreoffice.org ||/t/writer-relationship-betw ||een-page-margins-and-other- ||typographic-elements/47015/ ||4 CC||vsfo...@libreoffice.org -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 154080] Comment indicator is too small, non-circumspect, easy to miss
https://bugs.documentfoundation.org/show_bug.cgi?id=154080 --- Comment #10 from Eyal Rozenberg --- Created attachment 186294 --> https://bugs.documentfoundation.org/attachment.cgi?id=186294=edit Screenshot of calc window with attachment 185851, with 7.6 nightly Situation is somewhat better with a recent 7.6 nightly. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 154080] Comment indicator is too small, non-circumspect, easy to miss
https://bugs.documentfoundation.org/show_bug.cgi?id=154080 --- Comment #10 from Eyal Rozenberg --- Created attachment 186294 --> https://bugs.documentfoundation.org/attachment.cgi?id=186294=edit Screenshot of calc window with attachment 185851, with 7.6 nightly Situation is somewhat better with a recent 7.6 nightly. -- You are receiving this mail because: You are the assignee for the bug.
Re: [libreoffice-design] Re: Moving to LibreOffice 8?
/(I see that I replied to only one list, so just wanted to include
design and marketing. Sorry for the double-up.)/
Thank you all for sharing your opinion.
Please keep in mind that "a really big jump" or "a major innovation"
will always be very subjective and depend on personal areas of interest
or specialties, and I suspect that we will have dozens of different
opinions (and no agreement) if we ask what constitutes a feature that is
significant enough to warrant a major version number.
Concretely, here is the shortlist of things that, in my _subjective_
opinion, are important in the upcoming version (somewhat similar to
László's):
- availability on all major desktop platforms, including through
official app stores
- advertise availability for ARM processors on Windows
- build baseline bump
- zoom gesture support
- cementing of updated visual identity and improved theming following
the OS's
- improvements in accessibility of documents, including accessibility
checked in sidebar and tagged PDF export by default
- two new languages
- multi-page floating tables
- _maybe_ Skia by default on macOS
- _maybe_ new Windows installer
Waiting for significantly "bigger" (again, very subjective) changes in
LibreOffice is a bit unrealistic, knowing the project grows and has
grown very organically.
In the end, I have no strong opinion about it. I just hope everyone can
remain respectful and understand that sometimes, decisions have to be
made, and I believe the marketing team, after some discussion with the
rest of the TDF team, the Design team and the ESC, are a good fit to
take such decisions, instead of heated conversations filled with
subjective opinions on what feature is or isn't important.
The recent interaction makes me think a year/month versioning scheme is
beneficial in that discussing version bumps will not be needed anymore.
It's definitely not worth getting insulted, and I am sorry Italo had to
be at the receiving end of that. And as Jorge said: let's not get bogged
down into something that is in the end quite trivial.
I do however want to say I appreciate and take note of input from people
like Regina (associating major releases with ODF releases, the default
standard we are proud of), Kelvene (cultural aspect of the number),
David (deciding early on to allow work on more disruptive projects) and
Nigel ("The universal office suite", highlighting our strength in
language and platform support).
Cheers!
On 29/3/23 21:36, Jaron Kuppers wrote:
I agree with Italo that changing to version 8 makes sense and that it
is a marketing decision. Office suite updates that become new version
numbers rarely include much in the way of ground breaking innovation
and waiting for some integration of some new 'ground breaking' feature
does not make sense. Nor does waiting for ODF1.4 which is not a change
in some way unique to LibreOffice. A new version can also be framed
around the plan for that new version. What huge changes are we going
to make during version 8? It does not have to be limited to what
changes warranted a number change. I think universal accessibility
warrants a number change and makes for great marketing.
Italo, the way people talk to you is not okay... know that you have
the respect of many/most community members who trust in your marketing
expertise. Many are quick to speak on a topic they have no formal
training in.
My 2 cents...
Cheers,
Jaron
On Wed, Mar 29, 2023 at 5:14 AM Pedro Rosmaninho
wrote:
I would just like to counter what Eyal Rosenberg says. Version number
should be a marketing decision.
But I agree with his points that marketing must consider that major
innovations or missing features should be included with a major number
change otherwise said number change will fall flat.
The number 8 is a great opportunity so it shouldn't be wasted without
having something impactful when it is launched.
Regina Henschel escreveu no dia terça,
28/03/2023
à(s) 15:40:
> Hi Italo,
>
> the change from 6.x to 7.0 happens together with the change from
ODF 1.2
> to ODF 1.3. If the decision it to keep this kind of numbering, I
think a
> change to 8.0 should happen when LibreOffice starts support for
ODF 1.4.
> ODF 1.4 will hopefully be released end of 2024.
>
> Kind regards,
> Regina
>
> Italo Vignoli schrieb am 27.03.2023 um 19:11:
> > Moving to LibreOffice 8 (instead of 7.6) makes sense for marketing
> > purposes, as media is looking at LibreOffice as the real
innovator in
> > the open source office suite market, and the feeling of
journalists is
> > that we are forever stuck at 7.x.
> >
> > We all know that the next version will not include any significant
> > innovation which can justify the change of version, apart from
the new
> > build system for Windows and the availability of LibreOffice
for Arm
[Libreoffice-bugs] [Bug 154354] Printing a sheet, the filled colour of subsequent cell in the row inherit the filled colour of the first cell after rotating text to a 45 degree angle
https://bugs.documentfoundation.org/show_bug.cgi?id=154354 Stéphane Guillou (stragu) changed: What|Removed |Added Regression By||Armin Le Grand Keywords|bibisectRequest |bibisected, bisected -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-22.05' - sw/qa writerfilter/source
sw/qa/extras/ooxmlexport/data/tdf146955.odt |binary
sw/qa/extras/ooxmlexport/ooxmlexport17.cxx| 12
writerfilter/source/dmapper/DomainMapper_Impl.cxx | 12 +---
3 files changed, 17 insertions(+), 7 deletions(-)
New commits:
commit 8bc5e39f8df1b8f387fd1c3b6d5a16e48eb2e50a
Author: László Németh
AuthorDate: Wed May 25 11:57:13 2022 +0200
Commit: Aron Budea
CommitDate: Wed Mar 29 19:43:05 2023 +
tdf#146955 DOCX import: fix SAX exception with footnotes
(Likely broken) DOCX documents exported by Writer raised a SAX
exception, when PopFootOrEndnote() tried to access to a
not-existent footnote, because PushFootOrEndnote() failed to
create that.
Note: the original ODT contains hundreds of frames, and
these and the text content of the document have been put
into the TOC section during Writer's DOCX export, resulting a
broken document.
Regression from commit 9b39ce0e66acfe812e1d50e530dc2ccdef3e1357
"tdf#76260 DOCX import: fix slow footnote import".
Change-Id: I9e32feb0cae778a87f034a8b5c41989fec90899d
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/134934
Tested-by: Jenkins
Reviewed-by: László Németh
(cherry picked from commit 73696a01224a3758bde686f32ec7e6f4c90877fe)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/149727
Reviewed-by: Andras Timar
Tested-by: Jenkins CollaboraOffice
diff --git a/sw/qa/extras/ooxmlexport/data/tdf146955.odt
b/sw/qa/extras/ooxmlexport/data/tdf146955.odt
new file mode 100644
index ..c7a849f9b756
Binary files /dev/null and b/sw/qa/extras/ooxmlexport/data/tdf146955.odt differ
diff --git a/sw/qa/extras/ooxmlexport/ooxmlexport17.cxx
b/sw/qa/extras/ooxmlexport/ooxmlexport17.cxx
index 98be0085ab6e..e889b07009ea 100644
--- a/sw/qa/extras/ooxmlexport/ooxmlexport17.cxx
+++ b/sw/qa/extras/ooxmlexport/ooxmlexport17.cxx
@@ -13,6 +13,7 @@
#include
#include
+#include
#include
#include
#include
@@ -633,6 +634,17 @@ DECLARE_OOXMLEXPORT_TEST(testTdf144563, "tdf144563.docx")
}
}
+// broken test document?
+#if !defined(_WIN32)
+DECLARE_OOXMLEXPORT_TEST(testTdf146955, "tdf146955.odt")
+{
+// import of a (broken?) DOCX export with dozens of frames raised a SAX
exception,
+// when the code tried to access to a non-existent footnote
+uno::Reference xNotes(mxComponent,
uno::UNO_QUERY);
+CPPUNIT_ASSERT_EQUAL(sal_Int32(2), xNotes->getFootnotes()->getCount());
+}
+#endif
+
DECLARE_OOXMLEXPORT_TEST(testTdf144668, "tdf144668.odt")
{
uno::Reference xPara1(getParagraph(1, u"level1"),
uno::UNO_QUERY);
diff --git a/writerfilter/source/dmapper/DomainMapper_Impl.cxx
b/writerfilter/source/dmapper/DomainMapper_Impl.cxx
index e176e38c945d..cdbd753dd74e 100644
--- a/writerfilter/source/dmapper/DomainMapper_Impl.cxx
+++ b/writerfilter/source/dmapper/DomainMapper_Impl.cxx
@@ -3608,13 +3608,11 @@ void DomainMapper_Impl::PopFootOrEndnote()
uno::Reference< text::XFootnote > xFootnoteFirst, xFootnoteLast;
auto xFootnotes = xFootnotesSupplier->getFootnotes();
auto xEndnotes = xEndnotesSupplier->getEndnotes();
-if (IsInFootnote())
-xFootnotes->getByIndex(xFootnotes->getCount()-1) >>= xFootnoteLast;
-else
-xEndnotes->getByIndex(xEndnotes->getCount()-1) >>= xFootnoteLast;
-if ( ( ( IsInFootnote() && xFootnotes->getCount() > 1 ) ||
- ( !IsInFootnote() && xEndnotes->getCount() > 1 ) ) &&
-xFootnoteLast->getLabel().isEmpty() )
+if ( ( ( IsInFootnote() && xFootnotes->getCount() > 1 &&
+ ( xFootnotes->getByIndex(xFootnotes->getCount()-1) >>=
xFootnoteLast ) ) ||
+ ( !IsInFootnote() && xEndnotes->getCount() > 1 &&
+ ( xEndnotes->getByIndex(xEndnotes->getCount()-1) >>=
xFootnoteLast ) )
+ ) && xFootnoteLast->getLabel().isEmpty() )
{
// copy content of the first remaining temporary footnote
if ( IsInFootnote() )
Re: [libreoffice-design] Re: Moving to LibreOffice 8?
I agree with Italo that changing to version 8 makes sense and that it is a marketing decision. Office suite updates that become new version numbers rarely include much in the way of ground breaking innovation and waiting for some integration of some new 'ground breaking' feature does not make sense. Nor does waiting for ODF1.4 which is not a change in some way unique to LibreOffice. A new version can also be framed around the plan for that new version. What huge changes are we going to make during version 8? It does not have to be limited to what changes warranted a number change. I think universal accessibility warrants a number change and makes for great marketing. Italo, the way people talk to you is not okay... know that you have the respect of many/most community members who trust in your marketing expertise. Many are quick to speak on a topic they have no formal training in. My 2 cents... Cheers, Jaron On Wed, Mar 29, 2023 at 5:14 AM Pedro Rosmaninho wrote: > I would just like to counter what Eyal Rosenberg says. Version number > should be a marketing decision. > But I agree with his points that marketing must consider that major > innovations or missing features should be included with a major number > change otherwise said number change will fall flat. > The number 8 is a great opportunity so it shouldn't be wasted without > having something impactful when it is launched. > > > Regina Henschel escreveu no dia terça, > 28/03/2023 > à(s) 15:40: > > > Hi Italo, > > > > the change from 6.x to 7.0 happens together with the change from ODF 1.2 > > to ODF 1.3. If the decision it to keep this kind of numbering, I think a > > change to 8.0 should happen when LibreOffice starts support for ODF 1.4. > > ODF 1.4 will hopefully be released end of 2024. > > > > Kind regards, > > Regina > > > > Italo Vignoli schrieb am 27.03.2023 um 19:11: > > > Moving to LibreOffice 8 (instead of 7.6) makes sense for marketing > > > purposes, as media is looking at LibreOffice as the real innovator in > > > the open source office suite market, and the feeling of journalists is > > > that we are forever stuck at 7.x. > > > > > > We all know that the next version will not include any significant > > > innovation which can justify the change of version, apart from the new > > > build system for Windows and the availability of LibreOffice for Arm > > > processors on Windows (which has not been announced). > > > > > > Playing with the number 8, which can be rotated 90° to become the > > > "infinite" symbol, we can frame the next version as LibreOffice for an > > > infinite number of users, as we cover all hardware platforms and all > > > operating systems for personal productivity. > > > > > > This is my opinion. If the community wants to stick with 7.6, I won't > > > insist. I have received enough insults both public and private for the > > > marketing plan, and I am still receiving them from a few people, that I > > > am not willing to enter into that process again (even if the decision > on > > > the "community" tag has not been mine, but it looks like people have a > > > very short memory). > > > > > > Looking forward to your thoughts. > > > > > > -- > > To unsubscribe e-mail to: design+unsubscr...@global.libreoffice.org > > Problems? > > https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ > > Posting guidelines + more: > https://wiki.documentfoundation.org/Netiquette > > List archive: https://listarchives.libreoffice.org/global/design/ > > Privacy Policy: https://www.documentfoundation.org/privacy > > > > -- > To unsubscribe e-mail to: design+unsubscr...@global.libreoffice.org > Problems? > https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ > Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette > List archive: https://listarchives.libreoffice.org/global/design/ > Privacy Policy: https://www.documentfoundation.org/privacy >
[Libreoffice-bugs] [Bug 114027] [META] LibreOffice from Mac App Store bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=114027 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||151083 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151083 [Bug 151083] Systematic crash when accepting restart after extension installation (macOS AppStore) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151083] Systematic crash when accepting restart after extension installation (macOS AppStore)
https://bugs.documentfoundation.org/show_bug.cgi?id=151083 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||114027 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=114027 [Bug 114027] [META] LibreOffice from Mac App Store bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151077] Multiple extensions require repeat installation and activation, with error messages on first installation (macOS appstore version)
https://bugs.documentfoundation.org/show_bug.cgi?id=151077 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||114027 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=114027 [Bug 114027] [META] LibreOffice from Mac App Store bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114027] [META] LibreOffice from Mac App Store bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=114027 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||151077 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151077 [Bug 151077] Multiple extensions require repeat installation and activation, with error messages on first installation (macOS appstore version) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154203] No unopkg command line tool in macOS app store bundle
https://bugs.documentfoundation.org/show_bug.cgi?id=154203 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||114027 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=114027 [Bug 114027] [META] LibreOffice from Mac App Store bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114027] [META] LibreOffice from Mac App Store bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=114027 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||154203 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154203 [Bug 154203] No unopkg command line tool in macOS app store bundle -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153430] loadComponentfromUrl shows "lock" error message if url contains a backslash
https://bugs.documentfoundation.org/show_bug.cgi?id=153430 Buovjaga changed: What|Removed |Added OS|All |Windows (All) Version|7.5.0.3 release |7.4.2.3 release -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: extensions/uiconfig
extensions/uiconfig/spropctrlr/ui/labelselectiondialog.ui | 70 ++ 1 file changed, 33 insertions(+), 37 deletions(-) New commits: commit eebbe47a5e08fa5e8442c621f454d54484235ac8 Author: Olivier Hallot AuthorDate: Wed Mar 29 13:17:53 2023 -0300 Commit: Olivier Hallot CommitDate: Wed Mar 29 19:26:26 2023 + Bump Glade release for labelselectiondialog.ui Change-Id: Id941b353e8d9f0df2de3816d47e03ec564351701 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/149731 Tested-by: Olivier Hallot Reviewed-by: Olivier Hallot diff --git a/extensions/uiconfig/spropctrlr/ui/labelselectiondialog.ui b/extensions/uiconfig/spropctrlr/ui/labelselectiondialog.ui index cf4073db11a5..012a6fc13c3a 100644 --- a/extensions/uiconfig/spropctrlr/ui/labelselectiondialog.ui +++ b/extensions/uiconfig/spropctrlr/ui/labelselectiondialog.ui @@ -1,5 +1,5 @@ - + @@ -13,34 +13,31 @@ -False -6 +False +6 Label Field Selection True -0 -dialog - - - +0 +dialog -False +False True True vertical 6 -False -end +False +end _OK True -True -True -True -True +True +True +True +True True @@ -53,8 +50,8 @@ _Cancel True -True -True +True +True True @@ -67,8 +64,8 @@ _Help True -True -True +True +True True @@ -82,14 +79,14 @@ False True -end +end 0 True -False +False True True vertical @@ -97,14 +94,14 @@ True -False +False start These are control fields that can be used as label fields for the $controlclass$ $controlname$. -True +True True -control -60 -60 +control +60 +60 0 0 @@ -117,21 +114,20 @@ True -False +False True True -in +in True -True +True True True liststore1 -False -1 -True -True +False +1 +True @@ -165,10 +161,10 @@ _No assignment True -True -False -True -True +True +False +True +True False
Minutes from the UX/design meeting 2023-Mar-29
Present: John, Alejandro, Heiko Comments: Stuart Tickets/Topics * Customize dialog is too big to display on 1280x800 laptop screen + https://bugs.documentfoundation.org/show_bug.cgi?id=154021 + resolved NOB, Gnome theme occupies white space excessively (Stuart) + reducing font size solved the problem (Vince, OP) + we might be able to reduce the number of shown items in the lists (Heiko) + we should consider to adjust the minimum required size (John) + 1280x800 is still common (Heiko) + most users are on Windows (John) + don't make it worse for the vast majority (John) => keep ticket in WF/NAB state * Clone format of unmerged cells breaks up merging, applies to first unmerged cell only + https://bugs.documentfoundation.org/show_bug.cgi?id=153899 + merging cells with the keep option does exactly this, we must not format hidden cells + copying/cloning merged cells takes merge state into account, however, applying a format via cell style, which is the supposed workflow does not + cloning the merged state is a convenience feature => WF/NAB * Comment indicator is too small, non-circumspect, easy to miss + https://bugs.documentfoundation.org/show_bug.cgi?id=154080 + indicators have changed recently and are easy to spot at 100% but still somewhat harder at 200% + indicators can be controlled by TOCV > Text Overflow resp. Comment indicator + keeping the UI and the interaction simple is the best, meaning no flashing for example + changing the comment color is interesting + corner case, hard to believe it's needed by many => move checkboxes and colors for text overflow and comment indicator into application color (easy hack w. medium to interesting difficulty) * Insert Caption and Caption Options dialogs have a mix of settings affecting the whole category or only current caption + https://bugs.documentfoundation.org/show_bug.cgi?id=153248 + excellent mockup in bug 148597 comment 20 + seems to be powerful, and makes it more consistent (John) + useful for power users (John) => interesting GSoC project OpenPGP_signature Description: OpenPGP digital signature
