[Libreoffice-bugs] [Bug 32531] Incorrect cursor key movement between table cells of different directionality
https://bugs.documentfoundation.org/show_bug.cgi?id=32531 Eyal changed: What|Removed |Added Version|unspecified |Inherited From OOo --- Comment #31 from Eyal --- The bug is still present as described in my initial report. Checked again with MS Word and it behaves as expected, ie. in a table with mixed directionality cursor movement is consistent with the main directionality. NOTE: In Word, the role of the cursor keys is reversed when switching from the main directionality to the opposite directionality. For example, if the main directionality is LTR, with an RTL word (or table cell) in the middle, then using the right cursor key keeps moving to the next character, even when in the RTL word, so in effect the right cursor key visually moves the cursor to the left. Let's say LLL represents LTR text and RRR represents RTL text. The cursor is at the beginning of the text, and the users just presses the right-arrow key. This is hos the cursor moves: LLL RRR LLL <<< It doesn't matter whether this is plain text or table cells. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146490] UI: Field in a header/footer (like page number) lists a single time in navigator (and only for last page)
https://bugs.documentfoundation.org/show_bug.cgi?id=146490 --- Comment #7 from Jim Raykowski --- (In reply to Telesto from comment #6) > I encountered the same problem in slightly different consternation at bug > 146491. Where it seems - no understanding of the code - that hidden fields > are written to DOCX. Which is likely wrong (polluting the file). Which makes > showing hidden fields in navigator more of a feature Seems the revert patch for bug 146491 only solves that particular issue. I can still make hidden fields appear in the Navigator upon adding a Header to the example file or unchecking the 'Same content on left and right pages' option in the Page Style Header and/or Footer tab(s). Definitely will dig through the code to try to find out why this happens and if it can be changed before throwing in the towel and doing a hack around. Showing hidden fields may be useful when a field is in a hidden section or in folded outline content. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 61963] UI: 'Group and Outline' impossible with active Filter
https://bugs.documentfoundation.org/show_bug.cgi?id=61963 Rainer Bielefeld Retired changed: What|Removed |Added CC||LibreOffice@bielefeldundbus ||s.de --- Comment #12 from Rainer Bielefeld Retired --- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139612] Option "Search criteria = and <> must apply to whole cells" doesn't affect to calculation as must.
https://bugs.documentfoundation.org/show_bug.cgi?id=139612 Mike Kaganski changed: What|Removed |Added CC||hailholyqu...@gmx.de --- Comment #19 from Mike Kaganski --- *** Bug 146657 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 146657] COUNTIF mismatches Text
https://bugs.documentfoundation.org/show_bug.cgi?id=146657 Mike Kaganski changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Mike Kaganski --- Generally COUNTIF depends on what is selected at Options->LibreOffice->Calculate, General Calculations/Search criteria = and <> must apply to whole cells. However, until recently, there was bug 139612, fixed in 7.2.5. *** This bug has been marked as a duplicate of bug 139612 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146661] Linked images are missing
https://bugs.documentfoundation.org/show_bug.cgi?id=146661 --- Comment #2 from John --- The file was ODT, not DOC or DOCX I included only the content.xml and not the document itself by intent. I don't want to share my template. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146661] Linked images are missing
https://bugs.documentfoundation.org/show_bug.cgi?id=146661 --- Comment #1 from John --- Created attachment 177405 --> https://bugs.documentfoundation.org/attachment.cgi?id=177405=edit contentxml -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146661] New: Linked images are missing
https://bugs.documentfoundation.org/show_bug.cgi?id=146661 Bug ID: 146661 Summary: Linked images are missing Product: LibreOffice Version: 7.2.4.1 release Hardware: x86 (IA32) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: johnsmithbeat...@gmail.com Description: I don't know how to reproduced, but I'm really pissed off. Two days ago I created a document with 5 linked images. A very simple one, really. One image per page, png/jpg, and a small caption after it. Everything worked fine. Today I opened the document just to see that the first (house.jpg) and third (boris.png) images are missing. No, I don't mean that writer show me "image not found" placeholder. They simply missing. What the heck. I really want to use Writer over Word because it have table styles. But I simply cannot. Writer is actually pre-pre-alpha. How can I use software that will sinetly, like a Japanese shinobi, kill my data, harm my documents? This is the worst possible thing the software can do. Silently. Harm. User's. Files. I would be OK to pay $500 for S T A B L E Writer. But. If LO if so unstable, then maybe you should make a public announce that this is just pre-pre-pre-alpha and nobody should take it seriously unless the version 0.5 is ready? The problem is not just missing images. Few years ago there was a similar bug (now fixed) when Writer silently removed any formatting. That is, you will notice the missing formatting only when you open the document next time. Everybody blame Microsoft FUD (Fear, uncertainty, and doubt) "propaganda" about open-source software. I don't care what Microsoft says, but the bugs like the ones described above do exactly the same: they make me feel fear, uncertainty, and doubt. How can I trust the software after this? It's like one night you awaked and see your wife with a knife near your neck, and she crazy laught. It would be quite hard to trust her after this, right? Steps to Reproduce: - Actual Results: - Expected Results: - Reproducible: Always User Profile Reset: No Additional Info: - -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146398] Gtk3: crash when quickly switching between comments in sidebar after I edited the previous comment
https://bugs.documentfoundation.org/show_bug.cgi?id=146398 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 146417] Create a suggestion for document link if same word linked
https://bugs.documentfoundation.org/show_bug.cgi?id=146417 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 146415] Allow Basic + "Extended" Dictionaries
https://bugs.documentfoundation.org/show_bug.cgi?id=146415 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 95539] Option + arrow does not work properly when RTL is enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=95539 --- Comment #14 from QA Administrators --- Dear Zeev Turchinsky, 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 73494] Font fallback issue with text of mixed directionality in the UI
https://bugs.documentfoundation.org/show_bug.cgi?id=73494 --- Comment #10 from QA Administrators --- Dear Khaled Hosny, 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 61963] UI: 'Group and Outline' impossible with active Filter
https://bugs.documentfoundation.org/show_bug.cgi?id=61963 --- Comment #11 from QA Administrators --- Dear Rainer Bielefeld Retired, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 57422] presenter console RTL support needs completion
https://bugs.documentfoundation.org/show_bug.cgi?id=57422 --- Comment #11 from QA Administrators --- Dear Lior Kaplan, 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 56412] RTL UI: Movement of embedded objects is opposite to the change direction
https://bugs.documentfoundation.org/show_bug.cgi?id=56412 --- Comment #15 from QA Administrators --- Dear Lior Kaplan, 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 54494] improve cursor traversal of combined characters
https://bugs.documentfoundation.org/show_bug.cgi?id=54494 --- Comment #8 from QA Administrators --- Dear Caolán McNamara, 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 45147] right-to-left words appear in the wrong order in the CSV import dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=45147 --- Comment #14 from QA Administrators --- Dear Lior Kaplan, 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 39935] Disabled Asian or CTL language value should default to "None"
https://bugs.documentfoundation.org/show_bug.cgi?id=39935 --- Comment #11 from QA Administrators --- Dear Christophe Strobbe, 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 32531] Incorrect cursor key movement between table cells of different directionality
https://bugs.documentfoundation.org/show_bug.cgi?id=32531 --- Comment #30 from QA Administrators --- Dear Eyal, 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 129892] error loading a huge spreadsheet in ods format (no error in xlsx format)
https://bugs.documentfoundation.org/show_bug.cgi?id=129892 --- Comment #3 from QA Administrators --- Dear johannes.geest, 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 121584] Ctrl+LShift, Ctrl+RShift not setting direction in comments
https://bugs.documentfoundation.org/show_bug.cgi?id=121584 --- Comment #4 from QA Administrators --- Dear Eyal Rozenberg, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120615] Ctrl+LShift, Ctrl+RShift not setting direction in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=120615 --- Comment #8 from QA Administrators --- Dear Eyal Rozenberg, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120206] When switching keyboard layout, scrolling should not behave as though Scroll Lock was toggled
https://bugs.documentfoundation.org/show_bug.cgi?id=120206 --- Comment #12 from QA Administrators --- Dear Eyal Rozenberg, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 116828] edit comments are done in place when there are frozen columns, making it invisible
https://bugs.documentfoundation.org/show_bug.cgi?id=116828 --- Comment #6 from QA Administrators --- Dear pajaro, 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 146660] New: Applying paragraph styles resets some direct formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=146660 Bug ID: 146660 Summary: Applying paragraph styles resets some direct formatting Product: LibreOffice Version: 7.2.4.1 release Hardware: x86 (IA32) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: johnsmithbeat...@gmail.com Description: Create a document with the following text: ``` Lorem ipsum dolor sit amet Lorem ipsum dolor Lorem ipsum dolor Lorem ipsum dolor sit amet ``` Select the word "ipsum" in the 1st line and press Ctrl+B to apply "Bold" direct formatting to it. Put the cursor in the very **beginning** of the 2nd line, press Shift+End, and then Ctrl+B to make the whole line bold. Put the cursor in the very **end** of the 3rd line, press Shift+Home, and then press Ctrl+B to make this one line bold as well. The 2nd and 3rd lines are now bold, and the word "ipsum" in the first line is also bold. Now select the whole text (for example, by pressing Ctrl+A) and apply some paragraph style to it (for example, Text Body Indent). You will see that the second line is now regular, not bold. (And I think this is wrong from the user's perspective.) The 3rd line and the word "ipsum" on the 1st line are still bold. (Correct, this is what the user would expect, since applying paragraph styles is expected to not clear direct formatting.) Steps to Reproduce: - Actual Results: - Expected Results: - Reproducible: Always User Profile Reset: No Additional Info: - -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146659] Found scriptable element "script" in the uploaded SVG file.
https://bugs.documentfoundation.org/show_bug.cgi?id=146659 --- Comment #2 from davidak --- Created attachment 177404 --> https://bugs.documentfoundation.org/attachment.cgi?id=177404=edit exported svg -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146659] Found scriptable element "script" in the uploaded SVG file.
https://bugs.documentfoundation.org/show_bug.cgi?id=146659 --- Comment #1 from davidak --- Created attachment 177403 --> https://bugs.documentfoundation.org/attachment.cgi?id=177403=edit original file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146659] New: Found scriptable element "script" in the uploaded SVG file.
https://bugs.documentfoundation.org/show_bug.cgi?id=146659 Bug ID: 146659 Summary: Found scriptable element "script" in the uploaded SVG file. Product: LibreOffice Version: unspecified Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: bugs.documentfoundation.org+i...@davidak.de Description: When i try to upload an SVG file exported from LibreOffice Impress to Wikimedia Commons, i get the error: Found scriptable element "script" in the uploaded SVG file. The version is 7.1.7.2 which can't get selected from the list. Steps to Reproduce: 1. go to https://commons.wikimedia.org/wiki/Special:UploadWizard 2. upload file 3. get error Actual Results: error: Found scriptable element "script" in the uploaded SVG file. Expected Results: LibreOffice should be compatible with Wikipedia. Reproducible: Always User Profile Reset: No Additional Info: create compatible files -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146626] Calc crashes every time on font size operation, in a specific document
https://bugs.documentfoundation.org/show_bug.cgi?id=146626 Aron Budea changed: What|Removed |Added CC||ba...@caesar.elte.hu --- Comment #5 from Aron Budea --- No crash with LO 7.2.5.2 / macOS Monterey. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141869] Rephrase "Insert Reference To" items
https://bugs.documentfoundation.org/show_bug.cgi?id=141869 --- Comment #10 from Eyal Rozenberg --- (In reply to Jean-Baptiste Faure from comment #9) > 3/ Select Text under Type : the list of numbered formula appears in > Selection panel Do you mean select the "Figure" item under "Type"? > 4/ Mose the mouse pointer over one of the values in Selection list : the > extended tooltip appears and it says "Insert reference to" instead of "Refer > using" when you are pointing to a chapter header in the Selection list, > Headings being selected in Type list. I don't get any tooltip when my mouse is on the selection list. Perhaps if you could clarify the previous step? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146658] Libreoffice calc breaks file links when copy Spreadsheet to another folder
https://bugs.documentfoundation.org/show_bug.cgi?id=146658 fre...@wp.pl changed: What|Removed |Added Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED --- Comment #1 from fre...@wp.pl --- Although the path seemed absolute, the option was set to keep path relative. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146643] reload method applied to a subform with subforms fails to reload all when called from a macro
https://bugs.documentfoundation.org/show_bug.cgi?id=146643 Walter Werner changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146658] New: Libreoffice calc breaks file links when copy Spreadsheet to another folder
https://bugs.documentfoundation.org/show_bug.cgi?id=146658 Bug ID: 146658 Summary: Libreoffice calc breaks file links when copy Spreadsheet to another folder Product: LibreOffice Version: 7.2.4.1 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: fre...@wp.pl Description: Libreoffice calc breaks file links when copy Spreadsheet to another folder When linking to other spreadsheets, LO Calc stores something that seem like absolute path to the file. After I copy the Spreadsheet to other folder, and open the spreadsheet in a different location, the link seem broken. Created a simple test case: x:\LibO_test\Somefolder\Datasource\datasource.ods is my linked data source x:\LibO_test\Somefolder\Somespreadsheet.ods is my work spreadsheet where I do a database lookup. The URL is 'file:///X:/LibO_test/Somefolder/Datasource/datasource.ods' Now when I copy the Somespreadsheet.ods to x:\LibO_test\Somespreadsheet.ods , and open it in new location (x:\LibO_test instead of x:\LibO_test\Somefolder) I get broken URL: 'file:///X:/LibO_test/Datasource/datasource.ods' (note the missing "/Somefolder" in the path) Steps to Reproduce: 1. Detailed in description 2. 3. Actual Results: Result in broken file URL Expected Results: Expect to not break absolute file URLs Reproducible: Always User Profile Reset: No Additional Info: Version: 7.2.4.1 (x64) / LibreOffice Community Build ID: 27d75539669ac387bb498e35313b970b7fe9c4f9 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: pl-PL (pl_PL); UI: pl-PL Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146556] feature 'drag-mirror' is broken
https://bugs.documentfoundation.org/show_bug.cgi?id=146556 Noel Grandin changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146556] feature 'drag-mirror' is broken
https://bugs.documentfoundation.org/show_bug.cgi?id=146556 --- Comment #6 from Commit Notification --- Noel Grandin committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/4c4ce3dc2133199f0d804a686a1e0cd0c9124914 tdf#146556 feature 'drag-mirror' is broken It will be available in 7.4.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146556] feature 'drag-mirror' is broken
https://bugs.documentfoundation.org/show_bug.cgi?id=146556 Commit Notification changed: What|Removed |Added Whiteboard||target:7.4.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146648] Find and Replace doesn't restore last user position when opened
https://bugs.documentfoundation.org/show_bug.cgi?id=146648 Dave Barton changed: What|Removed |Added CC||da...@libreoffice.org --- Comment #4 from Dave Barton --- The results of my checks with Windows 10 and the "official" LibreOffice Linux installations are exactly the same as reported by V Stuart Foote in comment 3. Are you running a distro provided edition? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145919] LO73b1: Graphics test UI not fully localizable
https://bugs.documentfoundation.org/show_bug.cgi?id=145919 Gabor Kelemen (allotropia) changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |kelem...@ubuntu.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145919] LO73b1: Graphics test UI not fully localizable
https://bugs.documentfoundation.org/show_bug.cgi?id=145919 --- Comment #2 from Gabor Kelemen (allotropia) --- Created attachment 177402 --> https://bugs.documentfoundation.org/attachment.cgi?id=177402=edit How it looks after the proposed patch in qtz locale Proposed patch: https://gerrit.libreoffice.org/c/core/+/128087 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146648] Find and Replace doesn't restore last user position when opened
https://bugs.documentfoundation.org/show_bug.cgi?id=146648 V Stuart Foote changed: What|Removed |Added Keywords|needsUXEval | Severity|enhancement |normal OS|All |Linux (All) --- Comment #3 from V Stuart Foote --- OK, my fault. I'm so used to reading between the lines for issue intake I was over thinking it. However, can not confirm on Version: 7.2.5.1 (x64) / LibreOffice Community Build ID: 6d497ff5e83a906a307eb25cce314d40c0b8624f CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded WFM with each opening of the Find & Replace dialog, current session or on new LO launch, will be where it had last been moved to. On Windows at least, its positioning is on the full desktop--the LO application frame position and sizing has no impact. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146657] New: COUNTIF mismatches Text
https://bugs.documentfoundation.org/show_bug.cgi?id=146657 Bug ID: 146657 Summary: COUNTIF mismatches Text Product: LibreOffice Version: 7.1.4.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: hailholyqu...@gmx.de Created attachment 177401 --> https://bugs.documentfoundation.org/attachment.cgi?id=177401=edit Screenshot from the bug within Calc. Dear developers, I found this bug in the German version of LibreOffice Calc, but I presume it will be the same in any other translation. Try this in Calc: Format A1 and A2 as text. Enter in A1: 5 Enter in A2: 5+ (i.e. necessary when entering school grades in Germany) Enter in A3: =ZÄHLENWENN(A1:A2;"5") means: =COUNTIF(...) The result will be: "2". The "+" in A2 is not being noticed by the program. When you open the file in MS Excel, the correct result "1" is displayed. Thank you for your great work, you are creating a fabulous program! Yours sincerely Overlord -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146656] Table styles should update themselves according to the template
https://bugs.documentfoundation.org/show_bug.cgi?id=146656 John changed: What|Removed |Added Severity|normal |enhancement -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146656] New: Table styles should update themselves according to the template
https://bugs.documentfoundation.org/show_bug.cgi?id=146656 Bug ID: 146656 Summary: Table styles should update themselves according to the template Product: LibreOffice Version: 7.2.4.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: johnsmithbeat...@gmail.com Description: If you create 3 tables, apply Academic table style to each of them, then add the background color to the 3rd table, and then update Academic style according to the 3rd table, the background color will be added to the 1st and 2nd tables as well. This is great. But table styles are somewhat broken if you try to use them in your custom templates. Here is what I mean: 1. Create a custom template and save it in the LO templates directory. The template should contain a table with modified Academic style (you should add yellow background to it). Close that template. 2. Then create a document based on it, and save it somewhere. The document should contain 3 tables that are formatted by using the modified, "yellow", Academic style. Close it. 3. Open your template and change the background color of Academic style to green. Close it. 4. Open your document from the step 2. Although you will see the "Update styles / Keep Old Styles" window, the template styles won't be updates. So the "academic" tables in your documents will stay yellow, not green. Steps to Reproduce: - Actual Results: - Expected Results: - Reproducible: Always User Profile Reset: No Additional Info: - -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146650] EDITING FORMCONTROLS
https://bugs.documentfoundation.org/show_bug.cgi?id=146650 --- Comment #3 from PJF --- Created attachment 177400 --> https://bugs.documentfoundation.org/attachment.cgi?id=177400=edit Anchor alignment Is this correct? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125201] Scrolling down on Touchpad erratic (6.2.3.2 on Ubuntu 18.04)
https://bugs.documentfoundation.org/show_bug.cgi?id=125201 --- Comment #14 from nicolhill --- With regards to CSGO wagers, specialized help turns into a significant component in the foundation of each site. Some CSGO wagers administrations offer specialized help as a deferred ticket framework – this in itself isn't a disadvantage. Be that as it may, the best execution of a specialized emotionally supportive network is viewed as a web-based visit with a worker. It http://csgo-bets.org/csgo-spray-patterns/ is with the assistance of it that you can get exhortation as fast and effectively as conceivable in regards to any issue that has emerged connected with both the activity of the help and straightforwardly with your CSGO wagers. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146650] EDITING FORMCONTROLS
https://bugs.documentfoundation.org/show_bug.cgi?id=146650 --- Comment #2 from PJF --- Thank you so much for the feedback. Will do that. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 130431] Horrible drawinglayer dashed line performance
https://bugs.documentfoundation.org/show_bug.cgi?id=130431 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Resolution|--- |FIXED CC||79045_79...@mail.ru Status|NEW |RESOLVED --- Comment #5 from Roman Kuznetsov <79045_79...@mail.ru> --- I do not see the problem in Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 1be170d0629cf761f0ee4173007a3c021966546e CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL Let's close it as FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146650] EDITING FORMCONTROLS
https://bugs.documentfoundation.org/show_bug.cgi?id=146650 --- Comment #1 from Leslie --- This is caused by the anchor property of the text box. The text box is be aligned to the anchor point ergo the bottom of the text box is aligned to the bottom of the anchor point (in this case it looks to be paragraph). Change the text box anchor property to page and then the align to bottom will work as expected. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 81430] libreoffice-mysql-connector cannot create/edit tables without primary key
https://bugs.documentfoundation.org/show_bug.cgi?id=81430 --- Comment #12 from Julien Nabet --- At last, I finally succeeded at making the fields of table not readonly (pk or not pk case) There's still some work (at least really implementing alterColumnByName) but I had already to add a lot of things. So I'd like first to split it in several patches but I must find the right way to avoid breaking something. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146648] Find and Replace doesn't restore last user position when opened
https://bugs.documentfoundation.org/show_bug.cgi?id=146648 --- Comment #2 from R. Green --- We seem to be at cross purposes. I'm referring only to the position of the F dialogue in relation to the program window, i.e. how far to the left or right or up or down it is. Currently it always appears in the same position on the screen. If you move it to the side (to prevent it obscuring the document and other informational features) and close the dialogue, on reopening it reappears in the default position. It would be useful if I could move it to the optimum position and keep it there no matter how many times I open and close it – at least for the duration of the session. (I have no complaints about the search behaviour, i.e. how terms appear in the FIND field etc.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142493] FILEOPEN DOCX: Settings of character position and size changes in character style "Footnote Anchor"
https://bugs.documentfoundation.org/show_bug.cgi?id=142493 --- Comment #12 from Antonio --- I did the tests as required. Endnote anchor. Before the test, file ott. 1) Superscript 2) Rise / lower by: 45% 3) relative font size: 70% After testing, file docx 4) Superscript 5) Rise / lower by: automatic relative font size: 58% Best regards. Antonio -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146655] New: FORMATTING transfer format is applied to a wrong cell: below the cell, that was clicked
https://bugs.documentfoundation.org/show_bug.cgi?id=146655 Bug ID: 146655 Summary: FORMATTING transfer format is applied to a wrong cell: below the cell, that was clicked Product: LibreOffice Version: 7.2.3.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: stef...@michalek.de I choose a colored cell, click at the broom (left mouse click), click (left mouse click) at another cell (empty or filled), and then the cell _below_ the targeted cell is formatted (like the original cell was, e.g. colored). Expected behaviour would be: The cell, that was clicked, should get the format. I tested many times: the mouse click is correct when choosing cells, not when transferring the format. A further detail: It seems to happen, that the correct cell is affected, if (by zooming the cells big enough or by fine adjusting) the _whole_ mouse pointer is within the boundaries of the cell. The latter is not the case during normal work and especially when choosing cells. Normally, only the head of the mouse pointer arrow is relevant. While applying format transfer, however, the end of the arrow seems to be relevant. I even manage to get the cell below-and-right formatted, when clicking near the lower right corner (whith the pointer head still left and above the corner). Thanks, Steffen Version: 7.2.3.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: kf5 (cairo+wayland) Locale: de-DE (de_DE.UTF-8); UI: de-DE Ubuntu package version: 1:7.2.3-0ubuntu0.21.10.1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146556] feature 'drag-mirror' is broken
https://bugs.documentfoundation.org/show_bug.cgi?id=146556 --- Comment #5 from Noel Grandin --- fix here https://gerrit.libreoffice.org/c/core/+/128143 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146654] Imported tsv file saved as csv is saved as tsv.
https://bugs.documentfoundation.org/show_bug.cgi?id=146654 Mike Kaganski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG --- Comment #1 from Mike Kaganski --- There's no "TSV" file type in LibreOffice. CSV is a common name for any plain-text structured data imported into Calc, where import and export filter may use different separator characters and other settings. When you imported the tab-separated file, the import filter has saved the settings used for its import, to keep on export. That is reasonable, since *most of the time* users open files, make edits, and save, expecting the file structure to be kept, just the data be changed according to the edits. The use case that you describe is different, and it needs the export filter settings to be changed. For that, Save As dialog, where you define the file type, has "Edit filter settings" checkbox, checking which will open the filter settings after you click Save. There you may define comma as separator, to override the values stored from import. https://help.libreoffice.org/latest/en-US/text/scalc/guide/csv_files.html?DbPAR=CALC Closing NOTABUG. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146643] reload method applied to a subform with subforms fails to reload all when called from a macro
https://bugs.documentfoundation.org/show_bug.cgi?id=146643 Robert Großkopf changed: What|Removed |Added CC||rob...@familiegrosskopf.de --- Comment #2 from Robert Großkopf --- Look at table "selector". Value for "SearchString" will be set to '0' the whole time. oAusgabeAuswahl.Commit will say to the form: "I have a new value." oAusgabe.updateRow will write the form to the existing row. Won't work on new rows, but will woirk for your example. oAusgabeAuswahl.Parent.updateRow() is just the same, only seen from the position of the listbox up to the form, which contains the listbox. If this will solve your problem please set this bug to RESOLVED and NOTABUG. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102847] [META] Quick Find, Search and Replace
https://bugs.documentfoundation.org/show_bug.cgi?id=102847 V Stuart Foote changed: What|Removed |Added Depends on||146648 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=146648 [Bug 146648] Find and Replace doesn't restore last user position when opened -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146648] Find and Replace doesn't restore last user position when opened
https://bugs.documentfoundation.org/show_bug.cgi?id=146648 V Stuart Foote changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vstuart.fo...@utsa.edu Severity|normal |enhancement Keywords||needsUXEval Blocks||102847 --- Comment #1 from V Stuart Foote --- Positioning sense of Find & Replace (and I'd assume the Find Bar) is to follow the edit cursor. You can prove that with subsequent launch of the dialog using either the 'Find Next' or 'Find Previous'. Meaning the edit cursor is "the last set user position" and the anchor for Find & Replace "position" within the current document. Believe even the 'Find All' or 'Replace All' is relative to the current edit cursor. Not clear any other behavior would make sense. Could you please restate your use case and STR, thanks. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102847 [Bug 102847] [META] Quick Find, Search and Replace -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145114] TEMPLATES: Improve confirmation dialog "Update styles / Keep Old Styles" dialog + If the template has been detached, it is still specified in "File > Properties > Gener
https://bugs.documentfoundation.org/show_bug.cgi?id=145114 sdc.bla...@youmail.dk changed: What|Removed |Added Keywords||easyHack, skillCpp, skillUI -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146535] Mouse line goes missing when changing paragraph stile
https://bugs.documentfoundation.org/show_bug.cgi?id=146535 --- Comment #1 from ceki...@gmx.net --- can confirm this behaviour, here on KDE Neon (user profile reset) - additional information: mouse reappears after clicking with the right mouse button. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108747] [META] File properties/settings (meta data) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108747 sdc.bla...@youmail.dk changed: What|Removed |Added Depends on||145047 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=145047 [Bug 145047] Unchecking "Apply user data" => LO doesn't know if the template has been changed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103314] [META] Templates bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103314 sdc.bla...@youmail.dk changed: What|Removed |Added Depends on||145047 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=145047 [Bug 145047] Unchecking "Apply user data" => LO doesn't know if the template has been changed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145047] Unchecking "Apply user data" => LO doesn't know if the template has been changed
https://bugs.documentfoundation.org/show_bug.cgi?id=145047 sdc.bla...@youmail.dk changed: What|Removed |Added Blocks||103314, 108747 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103314 [Bug 103314] [META] Templates bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=108747 [Bug 108747] [META] File properties/settings (meta data) bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145047] Unchecking "Apply user data" => LO doesn't know if the template has been changed
https://bugs.documentfoundation.org/show_bug.cgi?id=145047 sdc.bla...@youmail.dk changed: What|Removed |Added CC||sdc.bla...@youmail.dk --- Comment #6 from sdc.bla...@youmail.dk --- Reproduced effect using STR in comment 3, plus additional steps 8. Open saved template and enable "Apply user data" (in File > Properties) 9. Save template 10. Open test file created in step 5 Result: Get expected warning about changed template. Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: e63fe68fb1d0915b64fdf63f7fa6eed866fa3a0d CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: da-DK (da_DK); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102847] [META] Quick Find, Search and Replace
https://bugs.documentfoundation.org/show_bug.cgi?id=102847 V Stuart Foote changed: What|Removed |Added Depends on||146647 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=146647 [Bug 146647] [UI] Reword for Match in the Find and Replace dialog -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146647] [UI] Reword for Match in the Find and Replace dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=146647 V Stuart Foote changed: What|Removed |Added Blocks||102847 CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vstuart.fo...@utsa.edu Severity|normal |enhancement Keywords||needsUXEval --- Comment #1 from V Stuart Foote --- The 'Match case' is a specific search filter-the entire line of check boxes is already labled/identified as applicable for the 'Find:' Don't believe we gain anything by adjusting the labels, and keep in mind the translation l10n requirement of the UI. -1 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102847 [Bug 102847] [META] Quick Find, Search and Replace -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145932] Lists: The formatting of the last word affect formatting of the number
https://bugs.documentfoundation.org/show_bug.cgi?id=145932 --- Comment #5 from John --- The workaround (for both "flavors" of this bug) is to finish a problematic list item with a space, and don't apply to this space any formatting. That is, if the text to left of this space is bold, the space should be regular, not bold; and if the text to the left side of the space is red, the space should be black, assuming that black is your primary text color. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 77419] Cannot align text to bottom of cell in row of table split over pages
https://bugs.documentfoundation.org/show_bug.cgi?id=77419 --- Comment #13 from R. Green --- Created attachment 177399 --> https://bugs.documentfoundation.org/attachment.cgi?id=177399=edit Writer file showing problem with bottom alignment in tables spanning pages Version: 7.1.5.2 / LibreOffice Community Build ID: 85f04e9f809797b8199d13c421bd8a2b025d52b5 CPU threads: 2; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-GB Calc: threaded This issue has still not been resolved after over 6 years! Open the attached writer file. Place the cursor in the blank cell and press "Align Bottom" (Table toolbar at botom of window). EXPECTED RESULT: Cursor should move to the bottom of the cell on the next page. ACTUAL RESULT: Cursor only moves to the bottom of the first page. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102847] [META] Quick Find, Search and Replace
https://bugs.documentfoundation.org/show_bug.cgi?id=102847 V Stuart Foote changed: What|Removed |Added Depends on||146651 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=146651 [Bug 146651] FIND AND REPLACE: difficult to recognize certain search/replace terms, enlarge the UI font (optionally) for clarity -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146651] FIND AND REPLACE: difficult to recognize certain search/replace terms, enlarge the UI font (optionally) for clarity
https://bugs.documentfoundation.org/show_bug.cgi?id=146651 V Stuart Foote changed: What|Removed |Added Blocks||102847 CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vstuart.fo...@utsa.edu Summary|FIND AND REPLACE: difficult |FIND AND REPLACE: difficult |to recognize certain|to recognize certain |search/replace terms|search/replace terms, ||enlarge the UI font ||(optionally) for clarity Keywords||needsUXEval --- Comment #1 from V Stuart Foote --- +1 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102847 [Bug 102847] [META] Quick Find, Search and Replace -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145932] Lists: The formatting of the last word affect formatting of the number
https://bugs.documentfoundation.org/show_bug.cgi?id=145932 --- Comment #4 from John --- I remember that I have had the same issue last week, but I cannot reproduce it right now. However, I can reproduce something very similar, and I'm sure that this is actually the same bug, just different "flavors": 1. Crete a new document based on the default Writer template. 2. Open the Styles pane (View > Styles) 3. Apply the "Numbering 123" to the first line and then type "This is foo". 4. Repeat the previous step for "This is bar" and "This is baz". So now you have the following list: ``` 1. This is foo 2. This is bar 3. This is baz ``` Put the cursor to the left side of the uppercase letter T in the "bar" line and then press Shift+End to select to its end. Then press Ctrl+B to make this selection bold. You will see that the number "2" is now also bold, even though it is outside the selection. I think this is wrong and "2" should stay "regular", not "bold". Version: 7.2.4.1 (x86) / LibreOffice Community Build ID: 27d75539669ac387bb498e35313b970b7fe9c4f9 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: default; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145047] Unchecking "Apply user data" => LO doesn't know if the template has been changed
https://bugs.documentfoundation.org/show_bug.cgi?id=145047 --- Comment #5 from Dieter --- (In reply to John from comment #3) > I can reproduce it with 7.2.4.1 => status NEW -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 88121] EDITING: When "Apply user data" unchecked, "Total editing time" And "Revision number" go blank
https://bugs.documentfoundation.org/show_bug.cgi?id=88121 Dieter changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||5047 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145047] Unchecking "Apply user data" => LO doesn't know if the template has been changed
https://bugs.documentfoundation.org/show_bug.cgi?id=145047 Dieter changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=88 ||121 Status|NEEDINFO|NEW --- Comment #4 from Dieter --- (In reply to John from comment #3) > I can reproduce it with 7.2.4.1 => status NEW -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107484] Non-english font names claim to be substituted in font name toolbar control
https://bugs.documentfoundation.org/show_bug.cgi?id=107484 Kevin Suo changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=61 ||134 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 61134] Font substitute name should appear in the font name combobox and in its tooltip
https://bugs.documentfoundation.org/show_bug.cgi?id=61134 Kevin Suo changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||7484 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107484] Non-english font names claim to be substituted in font name toolbar control
https://bugs.documentfoundation.org/show_bug.cgi?id=107484 Kevin Suo changed: What|Removed |Added CC||suokunl...@126.com --- Comment #6 from Kevin Suo --- This is still the case, and also for Chinese fonts. Steps to Reproduce: 1. Create a new ODT file in Simplified Chinese operating system language, where you have installed the font named "Source Han Sans CN". 2. Type some text, select the text, click the font dropdown, you find the localized font named "思源黑体 CN" (= "Source Han Sans CN") 3. Save and send the file to someone else who has the same font installed but may use an English language operating system. Now the font box shows italic, indicating that the font "思源黑体 CN" is missing. It is substituted to some other fonts, not the equivalent "Source Han Sans CN". 4. Create an ODT file in English system language, apply font "Source Han Sans CN". Now if you open this file in Chinese system language, then the font box indicates that the font "Source Han Sans CN" is missing. It is substituted to some other font, not the equivalent (localized) "思源黑体 CN". -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145047] Unchecking "Apply user data" => LO doesn't know if the template has been changed
https://bugs.documentfoundation.org/show_bug.cgi?id=145047 --- Comment #3 from John --- I can reproduce it with 7.2.4.1 The detailed workflow: 1. Create a new document based on the default Writer template 2. Click File, then Properties, and then clear the Apply User Data check box. 3. Change the color of the Text Body style to red 4. Save the file as a template and place it in the LibreOffice templates directory (on Windows, it is %AppData\LibreOffice\4\user\template). Close it. 5. Create a new document based on it and save it on the desktop (C:\Users\YourName\Desktop). Close it. 6. Open the template and change the color of the Text Body style from red to blue. Save and close the template. 7. Open your document. You **won't** see a warning that the temlate has changed. Version: 7.2.4.1 (x86) / LibreOffice Community Build ID: 27d75539669ac387bb498e35313b970b7fe9c4f9 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 83153] Implement UAA framework to support speech recognition and dictation support
https://bugs.documentfoundation.org/show_bug.cgi?id=83153 V Stuart Foote changed: What|Removed |Added CC||cr...@hotmail.com --- Comment #7 from V Stuart Foote --- *** Bug 146652 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 146652] Dictar por voz (Dictate by voice)
https://bugs.documentfoundation.org/show_bug.cgi?id=146652 V Stuart Foote changed: What|Removed |Added Summary|Dictar por voz |Dictar por voz (Dictate by ||voice) Resolution|--- |DUPLICATE CC||vstuart.fo...@utsa.edu Severity|normal |enhancement Status|UNCONFIRMED |RESOLVED --- Comment #1 from V Stuart Foote --- en gloss -- "It would be interesting, the possibility of being able to dictate by voice to writer, texts, through a microphone, if possible from the same program without having to depend on external programs." Situation remains as for duplicate bug 83153, an enhancement clearly beyond project scope. Each OS requires its own framework for speech recognition. That framework would then have to interact with the UNO Accessibility API via a native accessibility bridge (ATK, IAccessible2, or NS Accessibility). Unfortunately, as there is no "standard" for speech recognition, there is nothing for the project to implement. *** This bug has been marked as a duplicate of bug 83153 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146654] New: Imported tsv file saved as csv is saved as tsv.
https://bugs.documentfoundation.org/show_bug.cgi?id=146654 Bug ID: 146654 Summary: Imported tsv file saved as csv is saved as tsv. Product: LibreOffice Version: 7.2.4.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: bugzilla.rep...@johnandrea.ca Description: A tsv file opened then output via "save as" selecting format csv creates a tab delimited file rather than a comma delimited file. Steps to Reproduce: 1. create tsv example 2. open in calc 3. select "save as" csv format 4. open created file in text editor Actual Results: Output file has tabs, not commas Expected Results: Expected to have commas as field delimiters with quotes around fields containing commas Reproducible: Always User Profile Reset: No Additional Info: Should have created fields as expected. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146625] trying to open odp presentation, freezes LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=146625 Cor Nouws changed: What|Removed |Added CC||c...@nouenoff.nl --- Comment #2 from Cor Nouws --- (In reply to Aron Budea from comment #1) > There was a recent regression (from 2021-12-29) with this symptom, please > check with a newer build that contains the following revert: > https://cgit.freedesktop.org/libreoffice/core/commit/ > ?id=18444c2822e6561aa302f28f8166042b8dad0fe1 > > If the freeze still occurs, do reopen the bug report. Ah - do I find a moment to run a daily, am I hit by a bug that is fixed half a day later :p thnx for the reply of course :) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146398] Gtk3: crash when quickly switching between comments in sidebar after I edited the previous comment
https://bugs.documentfoundation.org/show_bug.cgi?id=146398 Kevin Suo changed: What|Removed |Added Version|7.4.0.0 alpha0+ Master |7.2.4.1 release -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102985] [META] Font bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102985 Kevin Suo changed: What|Removed |Added Depends on||146653 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=146653 [Bug 146653] Font rendering for localized "Source Han Sans CN" and "Source Han Serif CN" fonts (i.e. "思源黑体 CN" and "思源宋体 CN") is showing as bold rather than normal weight -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146653] Font rendering for localized "Source Han Sans CN" and "Source Han Serif CN" fonts (i.e. "思源黑体 CN" and "思源宋体 CN") is showing as bold rather than normal weight
https://bugs.documentfoundation.org/show_bug.cgi?id=146653 Kevin Suo changed: What|Removed |Added Blocks||102985 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102985 [Bug 102985] [META] Font bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146653] Font rendering for localized "Source Han Sans CN" and "Source Han Serif CN" fonts (i.e. "思源黑体 CN" and "思源宋体 CN") is showing as bold rather than normal weight
https://bugs.documentfoundation.org/show_bug.cgi?id=146653 Kevin Suo changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||4961 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146653] Font rendering for localized "Source Han Sans CN" and "Source Han Serif CN" fonts (i.e. "思源黑体 CN" and "思源宋体 CN") is showing as bold rather than normal weight
https://bugs.documentfoundation.org/show_bug.cgi?id=146653 Kevin Suo changed: What|Removed |Added Version|7.4.0.0 alpha0+ Master |6.0.0.3 release --- Comment #4 from Kevin Suo --- Bug already existed in Version: 6.0.0.0.alpha1+ Build ID: 6eeac3539ea4cac32d126c5e24141f262eb5a4d9 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 83066] [META] CJK (Chinese, Japanese, Korean, and Vietnamese) language issues
https://bugs.documentfoundation.org/show_bug.cgi?id=83066 Kevin Suo changed: What|Removed |Added Depends on||146653 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=146653 [Bug 146653] Font rendering for localized "Source Han Sans CN" and "Source Han Serif CN" fonts (i.e. "思源黑体 CN" and "思源宋体 CN") is showing as bold rather than normal weight -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146653] Font rendering for localized "Source Han Sans CN" and "Source Han Serif CN" fonts (i.e. "思源黑体 CN" and "思源宋体 CN") is showing as bold rather than normal weight
https://bugs.documentfoundation.org/show_bug.cgi?id=146653 Kevin Suo changed: What|Removed |Added Blocks||83066 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=83066 [Bug 83066] [META] CJK (Chinese, Japanese, Korean, and Vietnamese) language issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146653] Font rendering for localized "Source Han Sans CN" and "Source Han Serif CN" fonts (i.e. "思源黑体 CN" and "思源宋体 CN") is showing as bold rather than normal weight
https://bugs.documentfoundation.org/show_bug.cgi?id=146653 --- Comment #3 from Kevin Suo --- Created attachment 177398 --> https://bugs.documentfoundation.org/attachment.cgi?id=177398=edit test-non-localized-font-names.pdf Rendering result of the file "test-non-localized-font-names.odt" in an English language operating system. The text are correctly shown as non-bold for the 1st and 3rd paragraphs. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146653] Font rendering for localized "Source Han Sans CN" and "Source Han Serif CN" fonts (i.e. "思源黑体 CN" and "思源宋体 CN") is showing as bold rather than normal weight
https://bugs.documentfoundation.org/show_bug.cgi?id=146653 --- Comment #2 from Kevin Suo --- Created attachment 177397 --> https://bugs.documentfoundation.org/attachment.cgi?id=177397=edit test-non-localized-font-names.odt This should be open in a English system language for comparison. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145773] Section endnotes not collected at end of section
https://bugs.documentfoundation.org/show_bug.cgi?id=145773 David changed: What|Removed |Added Version|7.3.0.0 alpha0+ |7.3.0.0 beta1+ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146653] Font rendering for localized "Source Han Sans CN" and "Source Han Serif CN" fonts (i.e. "思源黑体 CN" and "思源宋体 CN") is showing as bold rather than normal weight
https://bugs.documentfoundation.org/show_bug.cgi?id=146653 --- Comment #1 from Kevin Suo --- Created attachment 177396 --> https://bugs.documentfoundation.org/attachment.cgi?id=177396=edit test-localized-font-name.pdf Rendering result of "test-localized-font-name.odt" in operating system of Simplified Chinese language. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145773] Section endnotes not collected at end of section
https://bugs.documentfoundation.org/show_bug.cgi?id=145773 David changed: What|Removed |Added Status|REOPENED|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145920] Applying a table style overwrites paragraph style within the table with paragraph direct formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=145920 --- Comment #9 from John --- (In reply to Dieter from comment #6) > (In reply to jsv from comment #3) > > Here is a simpler test. > > 1. Create a 3x3 table with no style. > > 2. Type "Foo" in the first cell. Apply the "Title" style to it. The text is > > now large. > > Thank you for test. Now I can reproduce the problem with > > Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community > Build ID: 9c95415de877af1430ab5b7123e11dedd0ea622c > CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: > win > Locale: de-DE (de_DE); UI: en-GB > Calc: CL > > If you open style inspector, you can see, that paragraph style is still > "Title" (paragraph style is also highlighted in style list), but there is > paragraph direct formatting and it's not possible to remove it with Strg+m. > => I changed bug summary a bit. It seems this bug is related to https://bugs.documentfoundation.org/show_bug.cgi?id=144638 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146653] New: Font rendering for localized "Source Han Sans CN" and "Source Han Serif CN" fonts (i.e. "思源黑体 CN" and "思源宋体 CN") is showing as bold rather than normal weight
https://bugs.documentfoundation.org/show_bug.cgi?id=146653 Bug ID: 146653 Summary: Font rendering for localized "Source Han Sans CN" and "Source Han Serif CN" fonts (i.e. "思源黑体 CN" and "思源宋体 CN") is showing as bold rather than normal weight Product: LibreOffice Version: 7.4.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: suokunl...@126.com Created attachment 177395 --> https://bugs.documentfoundation.org/attachment.cgi?id=177395=edit test-localized-font-names.odt The attached file named "test-localized-font-name.odt" uses "思源黑体 CN" (i.e., localized font name of "Source Han Sans CN") in the 1st paragraph, and uses "思源宋体 CN" (i.e., localized font name of "Source Han Serif CN") in the 3rd paragraph. The font weights are set to normal. When open this document in a Simplified Chinese desktop environment (so that when open in LibreOffice the localized font names can be correctly recognized), the 1st and the 3rd paragraphs are shown as bold weight. Steps to Reproduce: 1. Make sure you have "Source Han Sans CN" and "Source Han Serif CN" fonts installed. (on Fedora system, the packages names should be: adobe-source-han-sans-cn-fonts and adobe-source-han-serif-cn-fonts) 2. Switch your operating system language (not your LibreOffice language) to Simplified Chinese, then open the attached "test-localized-font-name.odt". (Note: If you do not switch your system language to Chinese then when you open the file the fonts are shown as italic, indicating that the font is not found, although you have already installed the font) Current Result: The text in the 1st and the 3rd paragraphs are wrongly shown as bold weight. Expected Result: They should show as normal weight. I attach the (wrong) rendering result in this step as "test-localized-font-name.pdf". 3. As a comparison, now switch your system to English language, then open the file named "test-non-localized-font-name.odt". In this file, the 1st and the 3rd paragraphs uses "Source Han Sans CN" and ""Source Han Serif CN" fonts, respectively, which are identical to the localized names as in the file in step 2 above. --> The text in the 1st and the 3rd paragraphs are correctly shown as normal weight. I attach the (correct) rendering result in this step as "test-non-localized-font-name.pdf". Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: a6415004630c28ac4c0a64b83d8f0fd5c77a6a31 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: zh-CN (zh_CN.UTF-8); UI: en-US Build Platform: Fedora34@X64, Branch:master, bibisect-linux-64-7.4-CN Calc: threaded Fedora 34 and Fedora 35. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146652] New: Dictar por voz
https://bugs.documentfoundation.org/show_bug.cgi?id=146652 Bug ID: 146652 Summary: Dictar por voz Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: cr...@hotmail.com Sería interesante, la posibilidad de poder dictar por voz a writer, textos, mediante un micrófono, a ser posible desde el mismo programa sin tener que depender de programas externos. Gracias. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146640] INSERT ROWS ABOVE INTO XLS DON'T COPY FORMULAS
https://bugs.documentfoundation.org/show_bug.cgi?id=146640 --- Comment #4 from marcel.deneumost...@gmail.com --- Sorry, I believe you are correct. With DROPBOX I am working on the same files from a PC that uses excel and another that uses "LibreOffice", that is confusion on my part. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146633] LibreOffice Draw does not detect Electronic Signature in PDF with valid skribble.com signature
https://bugs.documentfoundation.org/show_bug.cgi?id=146633 --- Comment #10 from tuxinator --- maybe somebody is on 7.2.2 like me and could also try? it is the most recent version on mageia at the moment i think, however will look at testing packages soon -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105122] LOCALHELP: write help page on Style themes
https://bugs.documentfoundation.org/show_bug.cgi?id=105122 Olivier Hallot changed: What|Removed |Added Depends on||90497 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=90497 [Bug 90497] Implementing document themes -- You are receiving this mail because: You are the assignee for the bug.
