[Libreoffice-bugs] [Bug 153388] Calc UI: Incorrect rendering of cell borders
https://bugs.documentfoundation.org/show_bug.cgi?id=153388 David Lynch changed: What|Removed |Added CC||dlynch1...@googlemail.com --- Comment #1 from David Lynch --- Created attachment 185128 --> https://bugs.documentfoundation.org/attachment.cgi?id=185128=edit Exhibits bug 153388 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153388] New: Calc UI: Incorrect rendering of cell borders
https://bugs.documentfoundation.org/show_bug.cgi?id=153388 Bug ID: 153388 Summary: Calc UI: Incorrect rendering of cell borders Product: LibreOffice Version: 7.5.0.3 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: dlynch1...@googlemail.com Description: In the attached spreadsheet: Enter d in g.I6. Observe cell border width between g.I22 and g.I23, it is wrong. [+Page][-Page], the cell border width between g.I22 and g.I23 has changed: it is now correct. Steps to Reproduce: See description Actual Results: See description Expected Results: See description Reproducible: Always User Profile Reset: Yes Additional Info: Same results in safe mode. Not new in 7.5, noticed this several months ago. Incorrect rendering affects only the penultimate border in a vertical direction of a border changed by a change in a parameter to STYLE(). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153387] UX: Sorting string not following Unicode / ASCII order by default
https://bugs.documentfoundation.org/show_bug.cgi?id=153387 --- Comment #1 from Franklin Weng --- Created attachment 185127 --> https://bugs.documentfoundation.org/attachment.cgi?id=185127=edit Demo ods file for data sorting -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153387] New: UX: Sorting string not following Unicode / ASCII order by default
https://bugs.documentfoundation.org/show_bug.cgi?id=153387 Bug ID: 153387 Summary: UX: Sorting string not following Unicode / ASCII order by default Product: LibreOffice Version: 3.6.7.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: frank...@goodhorse.idv.tw Description: In the default behavior of data sorting in Calc (Writer as well, see reference questions), the sorting algorithm is not following Unicode/ASCII code, which I think it's an intuitive and reasonable default behavior. If it is not, what kind of behavior does it follow? I didn't find any document explaining the default sorting algorithm or behavior. Language/locale settings? Opening with en_US.UTF-8 locale got the same result. You can visit the reference 2. I'll attach the file here later. It may not be a bug, but a user experience issue. Reference: 1. https://ask.libreoffice.org/t/calc/86667 2. https://ask.libreoffice.org/t/calc-data-sorting-not-following-ascii-unicode-order/87503 3. https://ask.libreoffice.org/t/writer-not-sort-following-ascii-code/84334 Steps to Reproduce: 1. Open the attached file 2. Data -> Sort Column B as ascending 3. The result does follow ASCII/Unicode code Actual Results: The result does follow ASCII/Unicode code Expected Results: - Following ASCII/Unicode is a reasonable default behavior IMO - If not, any document describing the default sorting algorithm? - If not, any option to force following ASCII/Unicode order? (Filling every character in Tool - Options - Calc - Sort List is NOT a user-friendly solution IMO) Reproducible: Always User Profile Reset: No Additional Info: Earliest version I tested: 版本 3.6.7.2 (組建 ID：e183d5b) Should be inherited from OO.o I think. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153133] Libreoffice Crashes with Youtube running
https://bugs.documentfoundation.org/show_bug.cgi?id=153133 --- Comment #2 from jhassett --- Sorry. Windows -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146548] FORMATTING - Negative numbers not red
https://bugs.documentfoundation.org/show_bug.cgi?id=146548 --- Comment #11 from ady --- Here is how I can trigger / repro this. 1. Open attachment 178096. 2. Tools > Options > LibreOffice > Accessibility > Use automatic font color for screen display (set ON, checked box) 3. OK 4. CTRL+SHIFT+F9 (Recalculate Hard) Result: negative number in default black color. How to show the color again: 5. Tools > Options > LibreOffice > Accessibility > Use automatic font color for screen display (set OFF, unchecked box) 6. OK 7. CTRL+SHIFT+F9 (Recalculate Hard) Result: negative number in red color according to cell Format Code. @Dinky, could you please confirm that the above procedure allows you to show the red color for negative numbers? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153386] Spreadsheet table copy does not copy diagrams correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=153386 --- Comment #1 from bernhard.fri...@mail.de --- Created attachment 185126 --> https://bugs.documentfoundation.org/attachment.cgi?id=185126=edit Visualize the problem -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153386] New: Spreadsheet table copy does not copy diagrams correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=153386 Bug ID: 153386 Summary: Spreadsheet table copy does not copy diagrams correctly Product: LibreOffice Version: 7.3.7.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: bernhard.fri...@mail.de Description: When copying the spreadsheet from January to February, in associated diagrams following is not correctly in the target spreadsheet - Column Legend - References to data going to the source spreadshett instead target (copied) spreadsheet Steps to Reproduce: 1. Copy spreadsheet 2. 3. Actual Results: When copying the spreadsheet from January to February, in associated diagrams following is not correctly in the target spreadsheet - Column Legend - References to data going to the source spreadshett instead target (copied) spreadsheet Expected Results: Correctly corrected spreadsheet Reproducible: Always User Profile Reset: No Additional Info: Version: 7.3.7.2 (x64) / LibreOffice Community Build ID: e114eadc50a9ff8d8c8a0567d6da8f454beeb84f CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112139] [META] Options dialog's Language settings bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=112139 Bug 112139 depends on bug 139961, which changed state. Bug 139961 Summary: Options dialog in Spelling and in Options - Language Settings - Writing Aids should distinguish between user-defined and shared dictionaries https://bugs.documentfoundation.org/show_bug.cgi?id=139961 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153144] Red Frame, Editing, RECORD CHANGES NOT SELECTED
https://bugs.documentfoundation.org/show_bug.cgi?id=153144 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 139961] Options dialog in Spelling and in Options - Language Settings - Writing Aids should distinguish between user-defined and shared dictionaries
https://bugs.documentfoundation.org/show_bug.cgi?id=139961 --- Comment #4 from QA Administrators --- Dear sdc.blanco, 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 146786] File > Close icon missing, X exits the program (not in Safe mode but yes with profile reset)
https://bugs.documentfoundation.org/show_bug.cgi?id=146786 --- Comment #18 from QA Administrators --- Dear Michael Wogan, 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 139846] Find and Find/Replace does not find all valid matches
https://bugs.documentfoundation.org/show_bug.cgi?id=139846 --- Comment #5 from QA Administrators --- Dear lillis_mark, 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 146548] FORMATTING - Negative numbers not red
https://bugs.documentfoundation.org/show_bug.cgi?id=146548 --- Comment #10 from QA Administrators --- Dear Dinky, 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 79364] EDITING: Wrong formatting when typing into selection
https://bugs.documentfoundation.org/show_bug.cgi?id=79364 --- Comment #13 from QA Administrators --- Dear Alexander, 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 140140] WRITER Notebookbar configuration window allows for drag and drop, but this has no effect and is reverted once OK is pressed
https://bugs.documentfoundation.org/show_bug.cgi?id=140140 --- Comment #2 from QA Administrators --- Dear Luca Di Bona, 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 75080] 3D Chart does not display minor axis tick marks
https://bugs.documentfoundation.org/show_bug.cgi?id=75080 --- Comment #12 from QA Administrators --- Dear Luke, 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 139515] FILESAVE DOCX: Percentage data gets lost in a chart, when saving as docx-file
https://bugs.documentfoundation.org/show_bug.cgi?id=139515 --- Comment #8 from QA Administrators --- Dear yousifjkadom, 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 134724] UI - Find in Calc fails when a formula refers to a cell in another sheet's pivot table
https://bugs.documentfoundation.org/show_bug.cgi?id=134724 --- Comment #10 from QA Administrators --- Dear Carl Pearson, 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 125019] Misleading error message for FODT Write Errors. The file could not be written.
https://bugs.documentfoundation.org/show_bug.cgi?id=125019 --- Comment #3 from QA Administrators --- Dear Francesco `ascii` Ongaro, 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 119645] FILEOPEN - CSV text import window hidden behind initial file-open window
https://bugs.documentfoundation.org/show_bug.cgi?id=119645 --- Comment #8 from QA Administrators --- Dear tagishsimon, 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 153297] A complex formula does not work in Calc 7.4.x; (MATCH function)
https://bugs.documentfoundation.org/show_bug.cgi?id=153297
--- Comment #11 from ady ---
FWIW, apparently the problem with the MATCH(1;AA2:AA400;1) function in 7.4.x+
(ATM) seems to be in how it reacts when the list is not really completely
sorted (e.g. ascending in this case).
1. If the list of values is {0;1;0;0...} (i.e. not ascending in its entirety),
the result of the above MATCH seems to be wrong (not "2"). The search/lookup
goes down to the end of the list (they are all zeroes/empty after the first
"1").
2. If the list is entirely ascending {0;1;2;3...} the result is correct ("2").
3. When initially loading attachment 185057, the MATCH function in $DOWN.A1 is
not recalculated, so it (still) results in "1" (=2-1).
4. On (hard) recalculation, the cell $DOWN.A1 is recalculated to 398 (=399-1).
5. Manually replacing $DOWN.A1 with a "1" brings the rest of the depending
cells' values to their original (non-empty) values.
For some reason, MATCH() fails when the lookup array is not actually sorted
according to what the third argument of MATCH() would expect. In theory, in
this case MATCH() should still find the (first) "1" located in $LIST.AA3
anyway, but it doesn't, just because the list is not entirely sorted.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153272] Writer Macro Find with certain Search Attributes performs Replacement.
https://bugs.documentfoundation.org/show_bug.cgi?id=153272 --- Comment #8 from Don --- (In reply to Julien Nabet from comment #7) > For these: > "ParaIsHyphenation" > "ParaHyphenationNoCaps" > "ParaHyphenationMaxHyphens" > "ParaHyphenationMaxLeadingChars" > "ParaHyphenationMaxTrailingChars" > > I asked for some help in https://gerrit.libreoffice.org/c/core/+/146435 but > had no feedback yet. Thank you for your prompt replies and assistance Julien Nabet. I have tested the 7.5.1 daily build and can confirm that the errors with Char Relief, Rotation, Scale Width, and ParaVert Alignment has been corrected. I would assume that Orphan and Widow will be corrected when that patch is released. I tested Writing Mode and it produced the same error I mentioned, I tried combining it with other related settings as I did before and it still caused the disappearing problem non-the-less, although in testing it in the L.O. UI I can't quite figure out how to set it to search for it there anyway, so perhaps this is not a bug?? I'm not sure. As for the hyphenation I will keep an eye out for how that turns out. Considering that your patches have fixed the initial problems listed, should I be marking this bug as "fixed"? Or should I wait until the Hyphenation has been resolved, and until the ParaOrphan and Widow patch has been tested? Kind regards, Don -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153297] A complex formula does not work in Calc 7.4.x; (MATCH function)
https://bugs.documentfoundation.org/show_bug.cgi?id=153297 --- Comment #10 from ady --- (In reply to m.a.riosv from comment #9) > Don't need to change anything, the issue is with MATCH() in DOWN.A1 > returning a different value in 7.4 (399) than in 7.3 (1) Great. I just was trying to follow what Yurij posted (which I quoted above). Anyway. There is a recent bug 152774 that received commits also recently, related to MATCH(), but I don't think it affected version 7.4.x (yet?). In spite of that, perhaps the 2 devs that committed patches there might be able to look at this too, also related to MATCH(). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153334] Support/default to a non-white page background in Dark Mode
https://bugs.documentfoundation.org/show_bug.cgi?id=153334 --- Comment #8 from John Mills --- (In reply to Heiko Tietze from comment #5) > Using system defaults for the UI is mandatory, and the ability to override > the default very much desirable (bug 153229). But I disagree with the *need* > to match the two sets as we primarily do WYSIWYG editing - black ink on > white paper. The option to change it back and forth makes sense in some > scenarios and we made it possible. So the WF verdict on bug 152184 is still > true, IMO. > > I envision a LibreOffice theme that allows to change both system and > application colors at once, if both are defined otherwise it would use the > automatic colors. And I'm not against a dedicated dialog to pick the color > combination similar to the UI chooser. > > *** This bug has been marked as a duplicate of bug 152184 *** I agree Heiko that would be very pragmatic as every user has their own preference, but a real dialog that shows up and not just a tip of the day. Perhaps after this amount of time a brief first start "wizard" would be helpful for users where a couple of simple questions are asked to set preferences such as light/dark mode, UI chooser etc? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153334] Support/default to a non-white page background in Dark Mode
https://bugs.documentfoundation.org/show_bug.cgi?id=153334 --- Comment #8 from John Mills --- (In reply to Heiko Tietze from comment #5) > Using system defaults for the UI is mandatory, and the ability to override > the default very much desirable (bug 153229). But I disagree with the *need* > to match the two sets as we primarily do WYSIWYG editing - black ink on > white paper. The option to change it back and forth makes sense in some > scenarios and we made it possible. So the WF verdict on bug 152184 is still > true, IMO. > > I envision a LibreOffice theme that allows to change both system and > application colors at once, if both are defined otherwise it would use the > automatic colors. And I'm not against a dedicated dialog to pick the color > combination similar to the UI chooser. > > *** This bug has been marked as a duplicate of bug 152184 *** I agree Heiko that would be very pragmatic as every user has their own preference, but a real dialog that shows up and not just a tip of the day. Perhaps after this amount of time a brief first start "wizard" would be helpful for users where a couple of simple questions are asked to set preferences such as light/dark mode, UI chooser etc? -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 153327] LO crashes on create/edit comment in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=153327 --- Comment #11 from ady --- (In reply to Paul from comment #8) > Deleting this file fixed the problem. But I had to recreate my > customisations after that. > > I don't understand why my profile should be fine when switching back to 7.4, > but not fine with 7.5. Well, those are interesting questions indeed. Being able to see the difference between those 2 files (the new, recreated one and the old one that caused the failure) _maybe_ would had been useful for developers to analyze. Although I'm glad you "solved" _your_ problem, it doesn't help to solve the original problem in LO. If someone still has the original profile file that caused the problem, _perhaps_ it might be helpful to attach it here for devs to take a look at it. OTOH, relevant developers might think otherwise. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153334] Support/default to a non-white page background in Dark Mode
https://bugs.documentfoundation.org/show_bug.cgi?id=153334 --- Comment #7 from John Mills --- (In reply to V Stuart Foote from comment #1) > But we can already directly format the "Application color" 'Document > background' and 'Font color' in user profile picking something other than > "Automatic" that follows the os/DE Light/Dark theme -- and saving to a user > "Color scheme" in profile for reuse. > > Printing and Export is not otherwise affected by the visible UI document > background. > > Why would we need to automate this further? And flat NO to it as default. > Especially given the minimal theme support from System Color values vs. > needs for the much broader Application Color values. > > If defaults don't work, users should Personalize their own Application Color > scheme and save it for reuse. > > The LibreOffice Dark theme provides an example, but users can build their > own. Something like this is by far the easiest way to handle this request. Microsoft provided a good UI/UX option here. This should exist in both the dark and light mode. Please do not hide something like this behind complex menu items as it is an important aspect of using a dark mode particularly at night when a white canvas is very straining on your eyes. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 153334] Support/default to a non-white page background in Dark Mode
https://bugs.documentfoundation.org/show_bug.cgi?id=153334 --- Comment #7 from John Mills --- (In reply to V Stuart Foote from comment #1) > But we can already directly format the "Application color" 'Document > background' and 'Font color' in user profile picking something other than > "Automatic" that follows the os/DE Light/Dark theme -- and saving to a user > "Color scheme" in profile for reuse. > > Printing and Export is not otherwise affected by the visible UI document > background. > > Why would we need to automate this further? And flat NO to it as default. > Especially given the minimal theme support from System Color values vs. > needs for the much broader Application Color values. > > If defaults don't work, users should Personalize their own Application Color > scheme and save it for reuse. > > The LibreOffice Dark theme provides an example, but users can build their > own. Something like this is by far the easiest way to handle this request. Microsoft provided a good UI/UX option here. This should exist in both the dark and light mode. Please do not hide something like this behind complex menu items as it is an important aspect of using a dark mode particularly at night when a white canvas is very straining on your eyes. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153297] A complex formula does not work in Calc 7.4.x; (MATCH function)
https://bugs.documentfoundation.org/show_bug.cgi?id=153297 --- Comment #9 from m.a.riosv --- Don't need to change anything, the issue is with MATCH() in DOWN.A1 returning a different value in 7.4 (399) than in 7.3 (1) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153297] A complex formula does not work in Calc 7.4.x; (MATCH function)
https://bugs.documentfoundation.org/show_bug.cgi?id=153297 --- Comment #8 from ady --- (In reply to m.a.riosv from comment #7) > (In reply to m.a.riosv from comment #5) > >... > > The issue in that file is in DOWN.A1 a formula with MATCH in it. I indeed saw that. Let's quote Yurij: "When changing any parameter in the "LIST"..." But there is no mention about what exactly was changed in order to replicate the reported problem. So, I repeat here the question: Which exact cells were modified in order to get that unexpected result? Which modification was made in those specific cells? For example, in attachment 185057 posted in bug 153298, in the worksheet named "DOWN", cell A1 contains the formula: $DOWN.A1: =MATCH(1;$LIST.$AA$2:$LIST.$AA$400;1)-1 or: $DOWN.A1: =MATCH(1,$LIST.$AA$2:$LIST.$AA$400,1)-1 So, in the range $LIST.$AA$2:$LIST.$AA$400 in the "LIST" worksheet, what was that Yurij changed in order to get the problem in the "DOWN" worksheet? Which specific cell in "LIST"? What was either deleted or modified in "LIST"? Similarly, in your attachment 185075 posted in comment 4, you used MATCH with whole columns, multiple times referring to the same column. That is, while MATCH is using the same column and with "1" as third argument. This means that you might understand what you yourself posted, but other users cannot replicate the original problem because there is that small detail I asked before. If either Yurij or m.a.riosv could reply with that little piece of info, I'll gladly try to replicate the problem (too). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153377] Add dark mode enable/disable option setting
https://bugs.documentfoundation.org/show_bug.cgi?id=153377 --- Comment #9 from V Stuart Foote --- Created attachment 185125 --> https://bugs.documentfoundation.org/attachment.cgi?id=185125=edit icon theme toggle btwn Win11 app Light theme mode and Win11 app Dark theme mode Clean install and default profile, current master against 7.6.0 testing on Win11. There are no issues with LibreOffice color theme and icon toggle responding to os/DE theme changes of App color theme mode. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153327] LO crashes on create/edit comment in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=153327 m.a.riosv changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #10 from m.a.riosv --- (In reply to Daniel from comment #9) > > Yes, the problem reappeared when restarting in normal mode. I've since > continued as Paul has. There is certainly a difference between the two > versions that effected 40% of our, er, massive sample size. Whom are 40% of which group of people? In Menu/Help/Restart in Safe, is the option to clean the profile. But usually it's enough cleaning the file registrymodifications.xcu in the root folder of the profile. It keeps the options in Menu/Tools/Options, so not the entire profile needs to be recreated. https://wiki.documentfoundation.org/UserProfile We are mainly volunteers helping out in our spare time, so please. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153385] New: Crash in: libc.so.6
https://bugs.documentfoundation.org/show_bug.cgi?id=153385 Bug ID: 153385 Summary: Crash in: libc.so.6 Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: st...@kelem.net This bug was filed from the crash reporting server and is br-e59fd8c4-e9a6-44af-b3d7-49bee52a0558. = I opened the database and clicked on Queries. Base crashed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153327] LO crashes on create/edit comment in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=153327 --- Comment #9 from Daniel --- (In reply to ady from comment #7) > Reopening. > > I don't think the reporter is saying that there is no bug, but rather that > when using safe mode the problem is not present, neither when using 7.4.x (a > prior version). The question is whether the problem still occurs after > starting version 7.5 in normal mode (after it is not repro in Safe mode). > Resetting user profile (maybe with a backup of the current) might be > necessary. > > Resetting user profile might be also a valid suggestion for Daniel in > comment 4. > > @Paul and @Daniel, please confirm results. Yes, the problem reappeared when restarting in normal mode. I've since continued as Paul has. There is certainly a difference between the two versions that effected 40% of our, er, massive sample size. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153383] Variable Fonts: handling of named instances
https://bugs.documentfoundation.org/show_bug.cgi?id=153383 --- Comment #3 from خالد حسني --- These are the named instances reported by CoreText (you can check with FontBook, you will see the same list of styles), so it is either a font or CoreText bug. The italic styles are synthesized by LibreOffice when missing, which is a standard behavior. We are missing Medium though, needs investigation. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: hwpfilter/source
hwpfilter/source/htags.cxx |5 ++---
hwpfilter/source/htags.h |3 ++-
hwpfilter/source/hwpreader.cxx |4 ++--
3 files changed, 6 insertions(+), 6 deletions(-)
New commits:
commit f71ce9b35598d6aa64f3b095e0b3c7683948c280
Author: Caolán McNamara
AuthorDate: Sat Feb 4 17:14:36 2023 +
Commit: Caolán McNamara
CommitDate: Sat Feb 4 22:54:28 2023 +
ofz: Use-of-uninitialized-value
Change-Id: I97fb4edcad3a014b622f1a936adecd634121ad3f
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146559
Tested-by: Jenkins
Reviewed-by: Caolán McNamara
diff --git a/hwpfilter/source/htags.cxx b/hwpfilter/source/htags.cxx
index 51fbd9b539a2..69d0398ca952 100644
--- a/hwpfilter/source/htags.cxx
+++ b/hwpfilter/source/htags.cxx
@@ -52,9 +52,8 @@ bool HyperText::Read(HWPFile& hwpf)
EmPicture::EmPicture(size_t tsize)
: size(tsize >= 32 ? tsize - 32 : 0)
+, data(size, 0)
{
-if (size != 0)
-data.reset( new uchar[size] );
}
EmPicture::~EmPicture()
@@ -70,7 +69,7 @@ bool EmPicture::Read(HWPFile & hwpf)
name[0] = 'H';
name[1] = 'W';
name[2] = 'P';
-return hwpf.ReadBlock(data.get(), size) != 0;
+return hwpf.ReadBlock(data.data(), size) != 0;
}
diff --git a/hwpfilter/source/htags.h b/hwpfilter/source/htags.h
index 0a302bf188af..d662a002ecb3 100644
--- a/hwpfilter/source/htags.h
+++ b/hwpfilter/source/htags.h
@@ -21,6 +21,7 @@
#define INCLUDED_HWPFILTER_SOURCE_HTAGS_H
#include
+#include
#ifdef _WIN32
#include
#endif
@@ -34,7 +35,7 @@ struct EmPicture
size_t size;
char name[16];
char type[16];
-std::unique_ptr data;
+std::vector data;
explicit EmPicture(size_t size);
~EmPicture(void);
diff --git a/hwpfilter/source/hwpreader.cxx b/hwpfilter/source/hwpreader.cxx
index 3cab4cb9ba72..302ebf7599f8 100644
--- a/hwpfilter/source/hwpreader.cxx
+++ b/hwpfilter/source/hwpreader.cxx
@@ -510,7 +510,7 @@ void HwpReader::makeDrawMiscStyle( HWPDrawingObject *hdo )
if (emp)
{
startEl("office:binary-data");
-chars(base64_encode_string(emp->data.get(), emp->size));
+chars(base64_encode_string(emp->data.data(), emp->size));
endEl("office:binary-data");
}
endEl("draw:fill-image");
@@ -3824,7 +3824,7 @@ void HwpReader::makePicture(Picture * hbox)
EmPicture *emp = hwpfile.GetEmPicture(hbox);
if( emp )
{
- chars(base64_encode_string(emp->data.get(),
emp->size));
+ chars(base64_encode_string(emp->data.data(),
emp->size));
}
}
else{
[Libreoffice-bugs] [Bug 153380] Copying/pasting datas from QGIS makes LibreOffice hanging
https://bugs.documentfoundation.org/show_bug.cgi?id=153380 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- Please, could you give the link to a QGIS table that makes LIbreOffice hangs at pasting. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153297] A complex formula does not work in Calc 7.4.x; (MATCH function)
https://bugs.documentfoundation.org/show_bug.cgi?id=153297 --- Comment #7 from m.a.riosv --- (In reply to m.a.riosv from comment #5) >... > The issue in that file is in DOWN.A1 a formula with MATCH in it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153364] libreoffice writer dont open odt document
https://bugs.documentfoundation.org/show_bug.cgi?id=153364 --- Comment #4 from elias estatistics --- pspp v.1.6. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153384] New: LibreOffice Writer - Resets numbering footnotes to default automatically
https://bugs.documentfoundation.org/show_bug.cgi?id=153384 Bug ID: 153384 Summary: LibreOffice Writer - Resets numbering footnotes to default automatically Product: LibreOffice Version: 7.4.4.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: hudson...@gmail.com Description: I am using the LibreOffice 7.4.4.2, on Windows 10 (64 bits). I am having problem with the configuration of the footnote numbering. When I configure for numbering the footnotes by page, the program (Writer) automatically resets for the default configuration, that is by document. Oddly, when I format the footnotes (e.g. text and font), the problem disappears. Steps to Reproduce: 1. There exists a huge file (with more than 300 pages), with more than 700 footnotes. 2. Opening the file, before to format the footnotes, if the footnote numbering is by document, change it for by page, in Tools->Footnotes and Endnotes. 3. Then write the text body of the document. Actual Results: The footnotes are renumbered by default and automatically by document instead of by page. Expected Results: Do not renumber the document footnotes. Reproducible: Sometimes User Profile Reset: No Additional Info: None. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153364] libreoffice writer dont open odt document
https://bugs.documentfoundation.org/show_bug.cgi?id=153364 --- Comment #3 from elias estatistics --- Created attachment 185124 --> https://bugs.documentfoundation.org/attachment.cgi?id=185124=edit spv file to open from pspp, and then save as odt file, which dont open tjhe spv file to be open from pspp, and then save as odt file, which dont open -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153383] Variable Fonts: handling of named instances
https://bugs.documentfoundation.org/show_bug.cgi?id=153383 --- Comment #2 from Thomas Linard --- I forgot the last item in the "Expected Results" list: Thin ExtraLight Light Regular Medium SemiBold Bold ExtraBold -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153383] Variable Fonts: handling of named instances
https://bugs.documentfoundation.org/show_bug.cgi?id=153383 --- Comment #1 from Thomas Linard --- Created attachment 185123 --> https://bugs.documentfoundation.org/attachment.cgi?id=185123=edit Screenshot -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 69254] Mac: Handling of fonts with more than 4 styles (R/B/I/BI) is suboptimal
https://bugs.documentfoundation.org/show_bug.cgi?id=69254 Thomas Linard changed: What|Removed |Added Blocks||153383 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153383 [Bug 153383] Variable Fonts: handling of named instances -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153383] Variable Fonts: handling of named instances
https://bugs.documentfoundation.org/show_bug.cgi?id=153383 Thomas Linard changed: What|Removed |Added Depends on||69254 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=69254 [Bug 69254] Mac: Handling of fonts with more than 4 styles (R/B/I/BI) is suboptimal -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153383] New: Variable Fonts: handling of named instances
https://bugs.documentfoundation.org/show_bug.cgi?id=153383 Bug ID: 153383 Summary: Variable Fonts: handling of named instances Product: LibreOffice Version: 7.5.0.3 release Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: thlin...@gmail.com Description: Congratulations on all the progress made in font feature support with version 7.5. I tested a variable font (Martian Mono: https://github.com/evilmartians/mono/blob/main/fonts/variable/MartianMono%5Bwdth%2Cwght%5D.ttf) under macOS 12.6.3. The VF has 8 named instances: Thin ExtraLight Light Regular Medium SemiBold Bold ExtraBold Steps to Reproduce: 1. Install the font. 2. In Libre Office 7.5.0.3 > Format > Character, choose "Family: Martian Mono". 3. Open "Typeface". Actual Results: See the following: Regular SemiExpanded Regular Thin ExtraLight Light SemiBold Bold ExtraBold Italic Bold Italic Expected Results: Thin ExtraLight Light Regular Medium SemiBold Bold (the VF doesn't have any Italic, Medium is missing, SemiExpanded Regular is not a named instance) Reproducible: Always User Profile Reset: Yes Additional Info: I also test Labrada (https://github.com/Omnibus-Type/Labrada/tree/main/fonts/variable): Medium named instance is missing. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153229] [RFE] Please provide a user preference to disable inheriting the system UI theme
https://bugs.documentfoundation.org/show_bug.cgi?id=153229 --- Comment #23 from M-Rick --- Created attachment 185122 --> https://bugs.documentfoundation.org/attachment.cgi?id=185122=edit LibreOffice 7.4 launched with light theme in PopOS while system is in dark mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153364] libreoffice writer dont open odt document
https://bugs.documentfoundation.org/show_bug.cgi?id=153364 Telesto changed: What|Removed |Added Version|7.1.0.3 release |7.0.0.3 release -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153364] libreoffice writer dont open odt document
https://bugs.documentfoundation.org/show_bug.cgi?id=153364 Telesto changed: What|Removed |Added CC||tele...@surfxs.nl Version|7.5.0.3 release |7.1.0.3 release --- Comment #2 from Telesto --- Also in Version: 7.0.0.3 Build ID: 8061b3e9204bef6b321a21033174034a5e2ea88e CPU threads: 8; OS: Mac OS X 10.16; UI render: default; VCL: osx Locale: nl-NL (nl_NL.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153229] [RFE] Please provide a user preference to disable inheriting the system UI theme
https://bugs.documentfoundation.org/show_bug.cgi?id=153229 --- Comment #22 from M-Rick --- Created attachment 185121 --> https://bugs.documentfoundation.org/attachment.cgi?id=185121=edit LibreOffice 7.5 launched with light theme in macOS while system is in dark mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153229] [RFE] Please provide a user preference to disable inheriting the system UI theme
https://bugs.documentfoundation.org/show_bug.cgi?id=153229 --- Comment #21 from M-Rick --- On macOS this can be done easily with the following command: defaults write org.libreoffice.script NSRequiresAquaSystemAppearance -bool yes (disable dark mode) It works pretty well On Linux it can be done in Gnome specifying the GTK theme variant: libreoffice %U (default behaviour follows system settings) Exec=env GTK_THEME=Pop libreoffice %U (force light theme in PopOS) Exec=env GTK_THEME=Pop-dark libreoffice %U (force dark theme in PopOS) On Windows I don't know. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153371] Spelling tool causes crash and ANR message on windows 11 and high CPU usage
https://bugs.documentfoundation.org/show_bug.cgi?id=153371 --- Comment #2 from Telesto --- Possibly bug 152738, based on the description -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153382] Unexpected open files (prual, all MS Word equivalent) loss, restoration to old saved version
https://bugs.documentfoundation.org/show_bug.cgi?id=153382 --- Comment #1 from Ron Hale --- Created attachment 185120 --> https://bugs.documentfoundation.org/attachment.cgi?id=185120=edit Image of Help | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'libreoffice-7-5' - sd/uiconfig
sd/uiconfig/simpress/ui/pmsummarypage.ui |1 + 1 file changed, 1 insertion(+) New commits: commit 648d5135b465361ddf5540519263aafe96acb64a Author: Caolán McNamara AuthorDate: Wed Feb 1 19:59:25 2023 + Commit: Adolfo Jayme Barrientos CommitDate: Sat Feb 4 20:40:33 2023 + leader of group should default to active Change-Id: I1c49b227e63f01ffdd1c3b427ef780ea38a6d1ba Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146409 Tested-by: Jenkins Reviewed-by: Adolfo Jayme Barrientos diff --git a/sd/uiconfig/simpress/ui/pmsummarypage.ui b/sd/uiconfig/simpress/ui/pmsummarypage.ui index 38637bbef087..4d91c3324159 100644 --- a/sd/uiconfig/simpress/ui/pmsummarypage.ui +++ b/sd/uiconfig/simpress/ui/pmsummarypage.ui @@ -66,6 +66,7 @@ False True True +True 0
[Libreoffice-commits] core.git: Branch 'libreoffice-7-5' - cui/uiconfig
cui/uiconfig/ui/langtoolconfigpage.ui | 349 ++ cui/uiconfig/ui/optdeeplpage.ui | 170 2 files changed, 271 insertions(+), 248 deletions(-) New commits: commit 1191c565ea55bdce98a4426f9729786d1b012c75 Author: Caolán McNamara AuthorDate: Thu Feb 2 09:13:46 2023 + Commit: Adolfo Jayme Barrientos CommitDate: Sat Feb 4 20:40:05 2023 + Resolves: tdf#152642 match spacing and layout of other option pages Change-Id: I18c398762f92a28d72dae3ae76991553e9ebb04c (cherry picked from commit 21e35521a8155856cfeb0b86aeafd8af6ab988ae) Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146499 Tested-by: Jenkins Reviewed-by: Adolfo Jayme Barrientos diff --git a/cui/uiconfig/ui/langtoolconfigpage.ui b/cui/uiconfig/ui/langtoolconfigpage.ui index 8be8c1c2359a..e7809cd91fd7 100644 --- a/cui/uiconfig/ui/langtoolconfigpage.ui +++ b/cui/uiconfig/ui/langtoolconfigpage.ui @@ -5,7 +5,10 @@ True False +True +True 6 +vertical 12 @@ -14,21 +17,26 @@ 0 none - + True False -True -True +12 +6 +6 +12 True False start -6 -4 If you enable this, the data will be sent to an external server. True + + +static + + 0 @@ -42,7 +50,6 @@ True True start -start none https://languagetool.org/legal/privacy @@ -58,8 +65,6 @@ True False start -6 -9 True @@ -67,178 +72,194 @@ 2 + + + + +True +False +LanguageTool API Options + + + + + + + + +False +True +0 + + + + +False +0 +none + + + +True +False +12 +6 +True +6 +12 + + +True +False +start +Base URL: +True +baseurl + + +0 +0 + + - + +True +True +True +True + + +1 +0 + + + + +True False -10 -0 -none - - - -True -False -5 -12 - - -True -False -start -Base URL: -True -baseurl - - -0 -0 - - - - -True -True -True -True - - -1 -0 - - - - -True -False -start -Username: -True -username - - -0 -2 - - - - -True -False -start -API key: -True -apikey - - -0 -4 - - - - -True -True -
[Libreoffice-bugs] [Bug 153382] New: Unexpected open files (prual, all MS Word equivalent) loss, restoration to old saved version
https://bugs.documentfoundation.org/show_bug.cgi?id=153382 Bug ID: 153382 Summary: Unexpected open files (prual, all MS Word equivalent) loss, restoration to old saved version Product: LibreOffice Version: 7.4.2.3 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ron_hale786...@yahoo.com Description: I will be editing a writer document, and it will disapear, aloug with all other open writer documents. The app is closed and when I go to the containing folder ato open it, I am ask if I want to restore the lost doccuments. A positive response will restore the working document with the last saved edits. I do not whether there has been data loss in any other open documents. Steps to Reproduce: 1.Unknown - seems to be random with a long time period 2. 3. Actual Results: Unknown - seems to be random with a long time period Expected Results: Data loss in all open writer documents Reproducible: Sometimes User Profile Reset: No Additional Info: It would help if I could copy the Help | about info. Iy you need that, I have a BMP copy, but do not see a way to include it yet. It is too much for an old man to type with one hand. LibreOffice bug report info dated 4 Feb 23.bmp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104281] Support processing optional smart font features for OOXML
https://bugs.documentfoundation.org/show_bug.cgi?id=104281 --- Comment #6 from Thomas Linard --- The properties are: w14:ligatures https://learn.microsoft.com/en-us/dotnet/api/documentformat.openxml.wordprocessing.runproperties.ligatures w14:numSpacing https://learn.microsoft.com/en-us/dotnet/api/documentformat.openxml.wordprocessing.runproperties.numberspacing w14:numForm https://learn.microsoft.com/en-us/dotnet/api/documentformat.openxml.wordprocessing.runproperties.numberingformat w14:stylisticSets https://learn.microsoft.com/en-us/dotnet/api/documentformat.openxml.wordprocessing.runproperties.stylisticsets w14:cntxtAlts https://learn.microsoft.com/en-us/dotnet/api/documentformat.openxml.wordprocessing.runproperties.contextualalternatives like this: -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98596] Linux: Handling of fonts with more than 4 styles (R/B/I/BI) is suboptimal
https://bugs.documentfoundation.org/show_bug.cgi?id=98596 Thomas Linard changed: What|Removed |Added CC||burkhard.gr...@t-online.de --- Comment #14 from Thomas Linard --- *** Bug 147739 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 147739] for opentype fonts font weight "Medium" is not displayed if weight "Regular" is also installed
https://bugs.documentfoundation.org/show_bug.cgi?id=147739 Thomas Linard changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #6 from Thomas Linard --- *** This bug has been marked as a duplicate of bug 98596 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153381] New: External links in Data tab of LibreOffice 7.5.0.3 returns nothing
https://bugs.documentfoundation.org/show_bug.cgi?id=153381 Bug ID: 153381 Summary: External links in Data tab of LibreOffice 7.5.0.3 returns nothing Product: LibreOffice Version: 7.5.0.3 release Hardware: x86-64 (AMD64) OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tmtpn...@yahoo.com Description: The external links in the Data tab under Calc of the newly released LibreOffice 7.5.0.3 for Mac failed to fetch nor return any data. Actual Results: Returns Nothing Expected Results: Returns data Reproducible: Always User Profile Reset: No Additional Info: Nothing -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153377] Add dark mode enable/disable option setting
https://bugs.documentfoundation.org/show_bug.cgi?id=153377 --- Comment #8 from V Stuart Foote --- Created attachment 185119 --> https://bugs.documentfoundation.org/attachment.cgi?id=185119=edit icon theme toggle btwn Win10 Light theme mode and Win10 Dark theme mode @M-Rick, the attached screen clip shows current master against LO 7.6.0 behavior on Win10 Custom color theme control selection of App theme Light or Dark Win11 should perform similar. Aside from request of bug 153229, please let us know if Win11 is mishandling the UI theme. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152903] CALC Autofilter Search items does not re-focus upon return from interaction with another app/internet page
https://bugs.documentfoundation.org/show_bug.cgi?id=152903 --- Comment #11 from Colin --- (In reply to ady from comment #10) > (In reply to Colin from comment #9) > > And it still fails to refocus Search items. > > What happens if you click on the search box again when you hover over it? > Can you continue typing-in? The search box resists all attempts to refocus. The only way to access it is to exit the pane and then reactivate it. I've tried double clicking and even a different mouse. I also just deactivated all extensions that are not part of the LO download package - also to no avail What I haven't tried is throwing the mouse against the wall - yet. Please advise if you would recommend that ;)) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153297] A complex formula does not work in Calc 7.4.x; (MATCH function)
https://bugs.documentfoundation.org/show_bug.cgi?id=153297 --- Comment #6 from ady --- It has not been so easy for me to understand exactly where the problem is, so I am about to post some kind of summary, up to this point (or at least I'll try), FWIW. First, there is a duplicate of this bug report, already marked as such, bug 153298. There is one original attachment 185057 posted in bug 153298. That file weights around 4.35MB. Then m.a.riosv posted a different file, attachment 185075, which weights around 1.05MB. According to OP (Yurij), using LO 7.4.x, when some data in some worksheet (named "LIST", and up to worksheet "Ser") is modified in some way, some of the formulas in another worksheet named "DOWN" result in what looks like "empty" cells (or something similar to that). This problem is not present in version 7.3.7 of LO. What neither Yurij nor m.a.riosv were able to explain (or I could not understand them, sorry) in simple steps (up to this point) is, which exact cells you modify in order to get that unexpected result, and which modification you made. For example, something like: _ "go to worksheet "LIST", to cell A1 and change the content to "xwy" (without quotation marks)". Another possible example would be: "go to worksheet "LIST", to cell AA10 and delete its content. If someone could provide a clear step-by-step procedure, indicating file name, worksheet (tab) name, cell address, and which specific change was made in that cell, I don't know how to try to replicate whatever issue results in worksheet "DOWN" (or in whatever sheet and cell the problem is ultimately seen). Could someone please be so kind and provide such clear step-by-step procedure? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140147] position of cursor not saved
https://bugs.documentfoundation.org/show_bug.cgi?id=140147 Aron Budea changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=14 | |1586| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151427] Writer is not opening at last cursor position
https://bugs.documentfoundation.org/show_bug.cgi?id=151427 Aron Budea changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=14 | |1586| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141586] Restoring last document position is unreliable
https://bugs.documentfoundation.org/show_bug.cgi?id=141586 Aron Budea changed: What|Removed |Added CC||aron.bu...@gmail.com See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=14 | |0147, | |https://bugs.documentfounda | |tion.org/show_bug.cgi?id=15 | |1427| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141586] Restoring last document position is unreliable
https://bugs.documentfoundation.org/show_bug.cgi?id=141586 Aron Budea changed: What|Removed |Added CC||schli...@lmu.de --- Comment #27 from Aron Budea --- *** Bug 142768 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 142768] cursor does not stick when closing and reopening
https://bugs.documentfoundation.org/show_bug.cgi?id=142768 Aron Budea changed: What|Removed |Added CC||aron.bu...@gmail.com --- Comment #5 from Aron Budea --- *** This bug has been marked as a duplicate of bug 141586 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141586] Restoring last document position is unreliable
https://bugs.documentfoundation.org/show_bug.cgi?id=141586 Aron Budea changed: What|Removed |Added CC||delest.ha...@gmail.com --- Comment #26 from Aron Budea --- *** Bug 141024 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 141024] Last position not saved in Writer document with 7.1 (portable)
https://bugs.documentfoundation.org/show_bug.cgi?id=141024 Aron Budea changed: What|Removed |Added CC||aron.bu...@gmail.com --- Comment #4 from Aron Budea --- *** This bug has been marked as a duplicate of bug 141586 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141586] Restoring last document position is unreliable
https://bugs.documentfoundation.org/show_bug.cgi?id=141586 --- Comment #25 from Aron Budea --- *** Bug 140860 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 140860] Open writer document doesn't position cursor where it was at previous close
https://bugs.documentfoundation.org/show_bug.cgi?id=140860 Aron Budea changed: What|Removed |Added CC||aron.bu...@gmail.com --- Comment #3 from Aron Budea --- *** This bug has been marked as a duplicate of bug 141586 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141586] Restoring last document position is unreliable
https://bugs.documentfoundation.org/show_bug.cgi?id=141586 Aron Budea changed: What|Removed |Added CC||sla...@cheapnet.it --- Comment #24 from Aron Budea --- *** Bug 140368 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 140368] LibreOffice Writer doesn't point to last changed line
https://bugs.documentfoundation.org/show_bug.cgi?id=140368 Aron Budea changed: What|Removed |Added CC||aron.bu...@gmail.com --- Comment #2 from Aron Budea --- *** This bug has been marked as a duplicate of bug 141586 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153377] Add dark mode enable/disable option setting
https://bugs.documentfoundation.org/show_bug.cgi?id=153377 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org --- Comment #7 from V Stuart Foote --- Your attachment 185115 is concerning. Assume this is a launch of LO 7.5.0.3 build. The Colibre icon theme shown is not its Dark mode icon theme. That should only happen if you have made an icon theme selection of "Colibre" set in your user profile (Tools -> Options -> View ). The default automatic mode should show "Automatic (Colibre (Dark))" But it could be a Windows 11 annoyance. We need to know. Please clear your user profile (via Help -> Restart in Safemode..., or simply delete/rename %APPDATA%/LibreOffice) and launch with defaults. Also, it would be helpful if you could install in parallel and test a current master against the 7.6 build as additional Dark theme mode handling proceeds. =-ref-= [1] daily builds of master are here: https://dev-builds.libreoffice.org/daily/master/Win-x86_64@tb77-TDF/ [2] instructions for /a administrative install "in parallel" are here: https://wiki.documentfoundation.org/Installing_in_parallel/Windows -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147576] SLIDESHOW: Shapes get stretched in slideshow
https://bugs.documentfoundation.org/show_bug.cgi?id=147576 Aron Budea changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=13 | |2557, | |https://bugs.documentfounda | |tion.org/show_bug.cgi?id=15 | |0402, | |https://bugs.documentfounda | |tion.org/show_bug.cgi?id=15 | |0102| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153380] Copying/pasting datas from QGIS makes LibreOffice hanging
https://bugs.documentfoundation.org/show_bug.cgi?id=153380 M-Rick changed: What|Removed |Added OS|All |Windows (All) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 51510] FILESAVE: Exporting documents with embedded SVG to doc or docx converts the image to low-resolution pixel graphics
https://bugs.documentfoundation.org/show_bug.cgi?id=51510 Aron Budea changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=13 | |2590| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132590] Export selection cuts off pixels on the right side and at the bottom side
https://bugs.documentfoundation.org/show_bug.cgi?id=132590 Aron Budea changed: What|Removed |Added Blocks|109323 | See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=12 | |6319, | |https://bugs.documentfounda | |tion.org/show_bug.cgi?id=51 | |510,| |https://bugs.documentfounda | |tion.org/show_bug.cgi?id=10 | |5998| CC||aron.bu...@gmail.com Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=109323 [Bug 109323] [META] Graphic export bugs and enhancements (jpg, png, eps, tiff, gif ...) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109323] [META] Graphic export bugs and enhancements (jpg, png, eps, tiff, gif ...)
https://bugs.documentfoundation.org/show_bug.cgi?id=109323 Aron Budea changed: What|Removed |Added Depends on|132590 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=132590 [Bug 132590] Export selection cuts off pixels on the right side and at the bottom side -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136584] Export Selection crops part of the image
https://bugs.documentfoundation.org/show_bug.cgi?id=136584 Aron Budea changed: What|Removed |Added CC||aron.bu...@gmail.com --- Comment #16 from Aron Budea --- *** This bug has been marked as a duplicate of bug 126319 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134545] FILESAVE LO Draw export to PNG asks for but does not record the relation of pixels to real-world size.
https://bugs.documentfoundation.org/show_bug.cgi?id=134545 Aron Budea changed: What|Removed |Added CC||aron.bu...@gmail.com --- Comment #2 from Aron Budea --- *** This bug has been marked as a duplicate of bug 126319 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 60814] Colors of shapes change after copy+paste from one drawing to another
https://bugs.documentfoundation.org/show_bug.cgi?id=60814 --- Comment #17 from Clemens Eisserer --- I am sorry, I cannot re-test every bug I report, as I do reporting frequently on many different open-source projects. However, keeping a bug-report alive, that has been filed 10 years ago and still not is fixed, seems to be a waste of time anyway. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153229] [RFE] Please provide a user preference to disable inheriting the system UI theme
https://bugs.documentfoundation.org/show_bug.cgi?id=153229 Mike Kaganski changed: What|Removed |Added CC||lyubomir.ko...@yahoo.com --- Comment #20 from Mike Kaganski --- *** Bug 153379 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 153379] Theme changed to dark in ver 7.5.0.3
https://bugs.documentfoundation.org/show_bug.cgi?id=153379 Mike Kaganski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Mike Kaganski --- *** This bug has been marked as a duplicate of bug 153229 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153380] New: Copying/pasting datas from QGIS makes LibreOffice hanging
https://bugs.documentfoundation.org/show_bug.cgi?id=153380 Bug ID: 153380 Summary: Copying/pasting datas from QGIS makes LibreOffice hanging Product: LibreOffice Version: 7.4.5.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: m.rick@gmail.com Description: When copying datas from QGIS data table to a Calc spreadsheet makes LibreOffice hanging. It works well with Excel or any other spreadsheet application. Only LibreOffice seems being incompatible. It affects any versions of LibreOffice. Steps to Reproduce: 1. Open the data table in a QGIS project 2. Select the datas an copy them 3. Open LibreOffice, on a spreadsheet document or create a new one 4. Paste the datas, LibreOffice hangs. It happens with Writer as well. Actual Results: LibreOffice hangs and it needs to force closing the application. Expected Results: The datas should be pasted in place in the spreadsheet including the column headers just like they are in the QGIS table. Reproducible: Always User Profile Reset: No Additional Info: Works well with any other spreadsheet softwares. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153229] [RFE] Please provide a user preference to disable inheriting the system UI theme
https://bugs.documentfoundation.org/show_bug.cgi?id=153229 Mike Kaganski changed: What|Removed |Added CC||m.rick@gmail.com --- Comment #19 from Mike Kaganski --- *** Bug 153377 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 153377] Add dark mode enable/disable option setting
https://bugs.documentfoundation.org/show_bug.cgi?id=153377 Mike Kaganski changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #6 from Mike Kaganski --- *** This bug has been marked as a duplicate of bug 153229 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152903] CALC Autofilter Search items does not re-focus upon return from interaction with another app/internet page
https://bugs.documentfoundation.org/show_bug.cgi?id=152903 --- Comment #10 from ady --- (In reply to Colin from comment #9) > And it still fails to refocus Search items. What happens if you click on the search box again when you hover over it? Can you continue typing-in? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143235] Calc drag and drop of rows or columns not working on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=143235 --- Comment #14 from M-Rick --- Created attachment 185118 --> https://bugs.documentfoundation.org/attachment.cgi?id=185118=edit Moving the column with a single click -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143235] Calc drag and drop of rows or columns not working on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=143235 --- Comment #13 from M-Rick --- I made a try under Windows, it's not a real drag-and-drop feature anyway. First the cursor must be placed exactly on the border of the selected column. If you don't have a good view or working on a laptop with the trackpad, it's a nightmare to be done. Then, once the column has been moved, the older one still remains in position. Only the datas are moved. So it needs anyway to remove the previous column at the end. The expected behaviour is to click on the column header and move it to its new location just like on this screenshot, without any special additional pressed key, something simple and easy. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150598] FILESAVE XLS Cell color lost upon save
https://bugs.documentfoundation.org/show_bug.cgi?id=150598 --- Comment #7 from ady --- > So, apparently the difference in color background seems to be solved (at > some point) since 7.4.4, but the same attachment 182009 [details] in comment > 1 can trigger another export difference that is not yet solved, in Vertical > Text Alignment. > > BTW, opening files in this 7.6.alpha seems slower than in 7.4.4. ... and column width difference. (Sorry, I forgot.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150598] FILESAVE XLS Cell color lost upon save
https://bugs.documentfoundation.org/show_bug.cgi?id=150598 --- Comment #6 from ady --- Using LO 7.4.4 (see later for newer version)... In the same cells where there is different background color (i.e. color in the original vs. no color in the newly saved xls(x) file), there seems to be also a different Text Alignment. Text Alignment in Cell S29: For attachment 182009 in comment 1 opened in LO 7.4.4: Horizontal: Left Vertical: Default >From originally downloaded, Re-saved as xls with LO 7.4.4: Horizontal: Default Vertical: Default >From originally downloaded, Re-saved as xlsx with LO 7.4.4: Horizontal: Default Vertical: Bottom So, different export for xls, and (another) different for xlsx. Now, using: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d8e6b488ceaff7c88856ebcfcfec14d2d8cd7652 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (es_AR); UI: en-US Calc: CL threaded Here there seems to be no change in background color (yea!) when comparing to the original (meaning that I export from the original again, using this alpha version), but there are other changes. 1. Some column width is not the same as in the original when exporting / re-saving as xlsX. This was also notable when exporting using LO 7.4.4. This difference in column width is _not_ notable when exporting to xls. 2. Cell S29 has the following Text Alignment: For attachment 182009 in comment 1 opened in this 7.6 alpha+: Horizontal: Left Vertical: Default >From originally downloaded, Re-saved as xls with this 7.6 alpha+: Horizontal: Left (compare to 7.7.4, yea!) Vertical: Default >From originally downloaded, Re-saved as xlsx with this 7.6 alpha+: Horizontal: Left (compare to 7.7.4, yea!) Vertical: Bottom (this seems to be forcing "Bottom" over "Default"?) So, apparently the difference in color background seems to be solved (at some point) since 7.4.4, but the same attachment 182009 in comment 1 can trigger another export difference that is not yet solved, in Vertical Text Alignment. BTW, opening files in this 7.6.alpha seems slower than in 7.4.4. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153378] FILEOPEN PPTX: Wrong text direction for math symbols (-+) in right-to-left shape
https://bugs.documentfoundation.org/show_bug.cgi?id=153378 --- Comment #2 from Pablo --- Created attachment 185117 --> https://bugs.documentfoundation.org/attachment.cgi?id=185117=edit PowerPoint 2023 PDF export -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153379] New: Theme changed to dark in ver 7.5.0.3
https://bugs.documentfoundation.org/show_bug.cgi?id=153379 Bug ID: 153379 Summary: Theme changed to dark in ver 7.5.0.3 Product: LibreOffice Version: 7.5.0.3 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: lyubomir.ko...@yahoo.com Description: Theme of all components changed to dark. It puts an enormous strain on the eyes. Please let users choose their darl/light theme regardless of system theme Actual Results: Install ver 7.5.0.3 Expected Results: Let users choose dark/light theme independently of system theme Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: SpreadsheetDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: no -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153378] FILEOPEN PPTX: Wrong text direction for math symbols (-+) in right-to-left shape
https://bugs.documentfoundation.org/show_bug.cgi?id=153378 --- Comment #1 from Pablo --- Created attachment 185116 --> https://bugs.documentfoundation.org/attachment.cgi?id=185116=edit PPTX with right-to-left text boxes, numbers and +- symbols -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153378] New: FILEOPEN PPTX: Wrong text direction for math symbols (-+) in right-to-left shape
https://bugs.documentfoundation.org/show_bug.cgi?id=153378 Bug ID: 153378 Summary: FILEOPEN PPTX: Wrong text direction for math symbols (-+) in right-to-left shape Product: LibreOffice Version: 7.5.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: pablo.pl...@gmail.com Description: The attached PPTX has two text boxes set with align-right and text-direction-rtl. The text has numbers/letters and +- math symbols. The direction of the math symbols in Impress is wrong. I didn't test other symbols like <, >... Steps to Reproduce: 1. Open the attached PPTX presentation with Impress. 2. Compare the text to the attached PDF exported from PowerPoint. Actual Results: The first text box show: "100-" The second text box show: "+C1" Expected Results: "-100" "C1+" Reproducible: Always User Profile Reset: No Additional Info: Tested with LibreOffice 7.5.0.3 and Version: 7.4.5.1 / LibreOffice Community Build ID: 40(Build:1) CPU threads: 2; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-IL (en_IL); UI: en-US Ubuntu package version: 1:7.4.5-0ubuntu0.20.04.1~lo1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153377] Add dark mode enable/disable option setting
https://bugs.documentfoundation.org/show_bug.cgi?id=153377 M-Rick changed: What|Removed |Added Attachment #185115|Capture dâécran |Capture dâécran 2023-02-03 filename|2023-02-03 115330.png |115330.png --- Comment #5 from M-Rick --- Comment on attachment 185115 --> https://bugs.documentfoundation.org/attachment.cgi?id=185115 Dark mode under Windows 11 Not very beautiful I meant. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153377] Add dark mode enable/disable option setting
https://bugs.documentfoundation.org/show_bug.cgi?id=153377 M-Rick changed: What|Removed |Added Component|Calc|LibreOffice Version|unspecified |7.5.0.3 release -- You are receiving this mail because: You are the assignee for the bug.
