[Libreoffice-bugs] [Bug 151040] Logo in Start Center initially shows correctly but then only shows some pixels after returning from a LibreOffice application.
https://bugs.documentfoundation.org/show_bug.cgi?id=151040 --- Comment #16 from Hussam Al-Tayeb --- (In reply to Stéphane Guillou (stragu) from comment #15) > Can't reproduce on Ubuntu 20.04 with GNOME 3.36.8, Adwaita, and lo 7.5.2.2. > The steps are very similar to bug 143673, which was fixed in 7.5.0. Thanks. I fixed the title so that it better represents the issue. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151040] Logo in Start Center initially shows correctly but then only shows some pixels after returning from a LibreOffice application.
https://bugs.documentfoundation.org/show_bug.cgi?id=151040 Hussam Al-Tayeb changed: What|Removed |Added Summary|Logo in Start Center only |Logo in Start Center |shows some pixels |initially shows correctly ||but then only shows some ||pixels after returning from ||a LibreOffice application. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147953] Autosize text frame stops working
https://bugs.documentfoundation.org/show_bug.cgi?id=147953 Panos Stokas changed: What|Removed |Added Status|NEW |UNCONFIRMED Ever confirmed|1 |0 --- Comment #11 from Panos Stokas --- This is the same issue with bug 151728. I have posted some useful info on recovering a document in that bug on a comment there. Pasting text from such applications (including even LO's formula code editor!) will switch LO to a broken compatibility mode. I don't know TDF's policy on marking duplicates but it's pretty certain that either bug must be marked as a duplicate. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151728] Pasting text from various programs forces Writer in a broken mode without the possibility of undoing it
https://bugs.documentfoundation.org/show_bug.cgi?id=151728 --- Comment #7 from Panos Stokas --- The issue in the description can be reproduced by replacing LO's formula editor with: Word Character Map an old 8085 emulator Sticky Notes The only way to fix the broken format is save the document as a flat XML file and manually edit the settings specified in my previous post: https://bugs.documentfoundation.org/show_bug.cgi?id=151728#c2 It's a pretty big issue I think. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151728] Pasting text from various programs forces Writer in a broken mode without the possibility of undoing it
https://bugs.documentfoundation.org/show_bug.cgi?id=151728 Panos Stokas changed: What|Removed |Added Summary|Pasting formula code under |Pasting text from various |a heading is breaking all |programs forces Writer in a |heading styles without |broken mode without the |possibility of undoing it |possibility of undoing it -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151728] Pasting formula code under a heading is breaking all heading styles without possibility of undoing it
https://bugs.documentfoundation.org/show_bug.cgi?id=151728 --- Comment #6 from Panos Stokas --- (In reply to lomacar from comment #5) > There are strange similarities to bug 147953 which I am waiting to get > fixed. https://bugs.documentfoundation.org/show_bug.cgi?id=147953 > > This bug and 147953 can both be triggered by pasting in any text from MS > Word or the Windows character map. It's the same issue. I've just copied a character from charmap.exe and my headings broke the same way. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154487] Enhancement Request: Allow LibreOffice Mail Merge to use default e-mail client
https://bugs.documentfoundation.org/show_bug.cgi?id=154487 --- Comment #10 from Michael Weghorn --- (In reply to Stuart Simon from comment #8) > [...] To personalize > the e-mail AND the attached certificate, both of which have their personal > name, would be a great feature to have. Feel free to open another enhancement request for this. I haven't used that feature myself, but the WollMux extension ( https://github.com/LibreOffice/WollMux ) provides the feature to have both a personalized document and a personalized email message for each recipient. WollMux might also be a helpful example for an extension that that does LO mail merge and provides additional features, e.g. when planning to create an extension that provides the feature to support sending the emails via specific email clients. > I'm wondering if there can be an extension to support popular e-mail client > integrations for mail merge (maybe separate ones for Outlook and > Thunderbird). Outlook does not use the same format to store mail messages as > most other e-mail clients (Outlook format is MSG, general format is EML). > But we don't need hundreds of mail-client Compose windows either. The > Word/Adobe integration does not actually open Outlook. It places messages in > Outlook's primary Outbox. The messages are sent only when the user opens > Outlook manually if it is not already open. Thanks for the explanation, that makes it much clearer. So IIUC, the Word/Adobe integrations do not really interact with Outlook via any API, but by placing the relevant files into the Outlook app data directory that are processed by Outlook the next time it is opened. I agree that opening a lot of compose windows doesn't sound like a great idea. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154815] UI: Cell cursor width has increased
https://bugs.documentfoundation.org/show_bug.cgi?id=154815 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #1 from m.a.riosv --- Please attach the info in Menu/Help/About LibreOffice (there is an icon to copy) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154683] XML Form Document: Named folder "Instance 1" appears as "Instance" before chosen.
https://bugs.documentfoundation.org/show_bug.cgi?id=154683 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154528] FILEOPEN PPTX: some bullet points show smaller than in PowerPoint
https://bugs.documentfoundation.org/show_bug.cgi?id=154528 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 145251] Hunspell produces non-valid compounding results (for Dutch)
https://bugs.documentfoundation.org/show_bug.cgi?id=145251 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 154503] XML Form Document: Creating of Bindings by Mouseclick on Instance Elements only shown after reopening document
https://bugs.documentfoundation.org/show_bug.cgi?id=154503 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 154487] Enhancement Request: Allow LibreOffice Mail Merge to use default e-mail client
https://bugs.documentfoundation.org/show_bug.cgi?id=154487 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154511] In holehonnuru twon panchayth office we use property tax calaculator now we are not able to login to the property tax calaculator we want update the taxes by 3% so we n
https://bugs.documentfoundation.org/show_bug.cgi?id=154511 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 154498] blind selected checkbox colours in configuration dialogue listboxes
https://bugs.documentfoundation.org/show_bug.cgi?id=154498 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 154519] When in Xmind app i export powerpoint file , and i open it in impress remote dont work good , and the powerpoint distroyed.
https://bugs.documentfoundation.org/show_bug.cgi?id=154519 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 154487] Enhancement Request: Allow LibreOffice Mail Merge to use default e-mail client
https://bugs.documentfoundation.org/show_bug.cgi?id=154487 --- Comment #9 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153777] FLUID page number indication option: on / off
https://bugs.documentfoundation.org/show_bug.cgi?id=153777 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151555] Save As PDF fails
https://bugs.documentfoundation.org/show_bug.cgi?id=151555 --- Comment #4 from QA Administrators --- Dear nik, 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 153777] FLUID page number indication option: on / off
https://bugs.documentfoundation.org/show_bug.cgi?id=153777 --- Comment #5 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150978] Calc randomly replacing Chart Data Ranges with Data Tables
https://bugs.documentfoundation.org/show_bug.cgi?id=150978 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151231] Change tracking formatting can't be modified
https://bugs.documentfoundation.org/show_bug.cgi?id=151231 --- Comment #3 from QA Administrators --- Dear Mike, 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 150978] Calc randomly replacing Chart Data Ranges with Data Tables
https://bugs.documentfoundation.org/show_bug.cgi?id=150978 --- Comment #3 from QA Administrators --- Dear didrey, 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 142066] Writer crashes if attempt to open insert special characters
https://bugs.documentfoundation.org/show_bug.cgi?id=142066 --- Comment #5 from QA Administrators --- Dear Kris Roberts, 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 92164] FILESAVE XLS Excessive number of rows warning (see comment 10)
https://bugs.documentfoundation.org/show_bug.cgi?id=92164 --- Comment #37 from QA Administrators --- Dear gmarco, 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 99025] [FORMATTING, FILESAVE] Table's Column break-After is not properly exported as .doc/.docx
https://bugs.documentfoundation.org/show_bug.cgi?id=99025 --- Comment #6 from QA Administrators --- Dear Nicolas Mailhot, 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 90939] Editing: Footnote (only one in the doc) inserted on last line of last column in section is not visible without extra editing
https://bugs.documentfoundation.org/show_bug.cgi?id=90939 --- Comment #8 from QA Administrators --- Dear Gordo, 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 45386] Column formatting not honored saving to .doc/.docx (probably because TOC is a section?)
https://bugs.documentfoundation.org/show_bug.cgi?id=45386 --- Comment #14 from QA Administrators --- Dear Vadim Rutkovsky, 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 90031] Sidebar: Tab icons do not change size based on preference
https://bugs.documentfoundation.org/show_bug.cgi?id=90031 --- Comment #11 from QA Administrators --- Dear Nikos Platis, 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 141029] Unable to delete form in form browser if it contain hidden field
https://bugs.documentfoundation.org/show_bug.cgi?id=141029 --- Comment #7 from QA Administrators --- Dear Matheod, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134702] Additional page added after pressing undo, not there upon reopen
https://bugs.documentfoundation.org/show_bug.cgi?id=134702 --- Comment #7 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 126239] Option “Sidebar icon size” has no Effect on Several Icons of the Sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=126239 --- Comment #9 from QA Administrators --- Dear Harald Koester, 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 123729] User information (name / picture) missing
https://bugs.documentfoundation.org/show_bug.cgi?id=123729 --- Comment #12 from QA Administrators --- Dear Nicolas Christener, 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 108240] Selection line around one cell invisible when cell has a black background color
https://bugs.documentfoundation.org/show_bug.cgi?id=108240 --- Comment #14 from QA Administrators --- Dear Kevin, 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 154499] we are write two or more word local or other language word example(amma appa )in LibreOffice ignore at a time
https://bugs.documentfoundation.org/show_bug.cgi?id=154499 Nehru changed: What|Removed |Added Summary|Accept consecutive words|we are write two or more |with spaces aka phrases in |word local or other |spellchecker|language word example(amma ||appa )in LibreOffice ignore ||at a time -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154506] some fonts are removed from the system after installations (updates) of Libre Office
https://bugs.documentfoundation.org/show_bug.cgi?id=154506 --- Comment #2 from خالد حسني --- If this issue is seen since 6.x then it is probably unrelated to my xhanges. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151728] Pasting formula code under a heading is breaking all heading styles without possibility of undoing it
https://bugs.documentfoundation.org/show_bug.cgi?id=151728 --- Comment #5 from loma...@gmail.com --- There are strange similarities to bug 147953 which I am waiting to get fixed. https://bugs.documentfoundation.org/show_bug.cgi?id=147953 This bug and 147953 can both be triggered by pasting in any text from MS Word or the Windows character map. I found this bug on Google by searching for "FrameAutowidthWithMorePara" which seems to be the culprit in 147953. Not sure why it would be applicable here though, since this is an issue with headings and indents, not frames. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154817] New: Direct paragraph formatting using Paragraph dialog always adds 'Fill Gradient Name' and 'Fill Hatch Name' to paragraph direct formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=154817 Bug ID: 154817 Summary: Direct paragraph formatting using Paragraph dialog always adds 'Fill Gradient Name' and 'Fill Hatch Name' to paragraph direct formatting Product: LibreOffice Version: 7.3.0.0 alpha0+ Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rayk...@gmail.com Steps to reproduce: 1. Open a new text document 2. Open the Styles Inspector Ctrl+Alt+6 or Menu > View > Sidebar > Styles Inspector 3. Type a word or sentence, perhaps 'Lorem ipsum dolor' 4. Add a paragraph direct format property by using the Paragraph dialog Menu > Format > Paragraph... 5. Change a property in the Paragraph dialog then press OK Results: The Styles Inspector shows 'Fill Gradient Name' and 'Fill Hatch Name' under Paragraph Direct Formatting whenever a paragraph property is changed using the Paragraph dialog. Prior to commit 3f6797c29e9672eba354400f24a669244fd746c0 'Fill Gradient Name' and 'Fill Hatch Name' were not added. Author: Justin Luth Date: Mon Jun 21 16:56:04 2021 +0200 tdf#132776 sw UI: make unique names for custom hatch and gradient -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154037] MySQL/MariaDB direct connection: Deleted tables won't be deleted in content.xml, when deleted directly in MySQL
https://bugs.documentfoundation.org/show_bug.cgi?id=154037 --- Comment #2 from flywire --- https://ask.libreoffice.org/t/possible-synch-error-between-mysql-and-base/88846/14 > AndrewBase 2.2.4 speaks precisely about this issue. There is a workaround > listed > there, which I have slightly modified, and it seems to be working > just fine: sub refreshTables() dim dbURL as string: dbURL = ConvertToURL(“C:\filename.odb”) dim oBaseContext as object: oBaseContext = CreateUnoService(“com.sun.star.sdb.DatabaseContext”) dim oDB as object: oDB = oBaseContext.getByName(dbURL) dim oDoc as object: oDoc = oDB.DatabaseDocument dim oDisp as object: oDisp = createUnoService(“com.sun.star.frame.DispatchHelper”) dim oFrame as object: oFrame = oDoc.getCurrentController().getFrame() oDisp.executeDispatch(oFrame, “.uno:DBRefreshTables”, “”, 0, Array()) end sub Download AndrewBase from https://www.pitonyak.org/database/ - 2.2.4 Refresh the tables -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108253] [META] Calc cell formula bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108253 Bug 108253 depends on bug 138220, which changed state. Bug 138220 Summary: calc: calculation: roundup: rounddown: fail in 7.1 alpha https://bugs.documentfoundation.org/show_bug.cgi?id=138220 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154703] META Export DOCX flies with framePr instead of DrawingDML
https://bugs.documentfoundation.org/show_bug.cgi?id=154703 --- Comment #12 from Commit Notification --- Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/e07d5c089ab2e8fe8a5cfa2a11cef3f1cf3afab3 tdf#154703 docx export framePr: export xAlign/yAlign It will be available in 7.6.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152827] Distance between symbol and index adjustable
https://bugs.documentfoundation.org/show_bug.cgi?id=152827 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Whiteboard| QA:needsComment| OS|Windows (All) |All --- Comment #1 from Stéphane Guillou (stragu) --- It's true that Format > Spacing, using the Indexes Category, does not allow changing the horizontal spacing. Does using csub help? E.g.: T csub g -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153370] Language drop down menu obscured in Review panel in References screen in Collabora on iPad
https://bugs.documentfoundation.org/show_bug.cgi?id=153370 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Whiteboard| QA:needsComment| Resolution|--- |MOVED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Stéphane Guillou (stragu) --- Hi Roger As this is specific to the Collabora app (TDF does not currently provide an iPad version), please report it on their GitHub issue tracker: https://github.com/CollaboraOnline/online/issues Thank you! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99648] [META] Improve Layer Handling
https://bugs.documentfoundation.org/show_bug.cgi?id=99648 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||153432 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153432 [Bug 153432] Add buttons to toggle layer visibility and locked state -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99648] [META] Improve Layer Handling
https://bugs.documentfoundation.org/show_bug.cgi?id=99648 Bug 99648 depends on bug 153432, which changed state. Bug 153432 Summary: Add buttons to toggle layer visibility and locked state https://bugs.documentfoundation.org/show_bug.cgi?id=153432 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153432] Add buttons to toggle layer visibility and locked state
https://bugs.documentfoundation.org/show_bug.cgi?id=153432 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Blocks||99648 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||3439 Version|unspecified |Inherited From OOo CC||stephane.guillou@libreoffic ||e.org Resolution|--- |WORKSFORME --- Comment #4 from Stéphane Guillou (stragu) --- There is now a toggle for layer visibility in the context menu, starting in LO 7.6 (see bug 113439). I imagine this is the most commonly used setting, and it's the one Rainer wanted easier access to. Along with the shortcuts Regina provided, I think this can be closed as "works for me", but feel free to set back to "new" if you disagree. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=99648 [Bug 99648] [META] Improve Layer Handling -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153936] Start Center application filter has missed Databases
https://bugs.documentfoundation.org/show_bug.cgi?id=153936 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks|61914 | See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=80 | |934 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=61914 [Bug 61914] [META] Start Center bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 61914] [META] Start Center bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=61914 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on|153936 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153936 [Bug 153936] Start Center application filter has missed Databases -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 61914] [META] Start Center bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=61914 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||153936 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153936 [Bug 153936] Start Center application filter has missed Databases -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 61914] [META] Start Center bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=61914 Bug 61914 depends on bug 153936, which changed state. Bug 153936 Summary: Start Center application filter has missed Databases https://bugs.documentfoundation.org/show_bug.cgi?id=153936 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151803] StartCenter: Filter for shown applications - missing Databases and Formula documents
https://bugs.documentfoundation.org/show_bug.cgi?id=151803 Stéphane Guillou (stragu) changed: What|Removed |Added CC||jcs...@libreoffice.org --- Comment #3 from Stéphane Guillou (stragu) --- *** Bug 153936 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 153936] Start Center application filter has missed Databases
https://bugs.documentfoundation.org/show_bug.cgi?id=153936 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||61914 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=80 ||934 Status|UNCONFIRMED |RESOLVED Priority|medium |low Whiteboard| QA:needsComment| Resolution|--- |DUPLICATE Severity|enhancement |trivial CC||heiko.tietze@documentfounda ||tion.org, ||stephane.guillou@libreoffic ||e.org --- Comment #1 from Stéphane Guillou (stragu) --- Thank you JC. Already reported in bug 151803. *** This bug has been marked as a duplicate of bug 151803 *** Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=61914 [Bug 61914] [META] Start Center bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144237] Enforce a sane minimum width on Linux
https://bugs.documentfoundation.org/show_bug.cgi?id=144237 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #6 from Stéphane Guillou (stragu) --- I think we can mark this as a duplicate of bug 97894: having a minimum window size on Linux should fix the issue described here. Please set back to "new" if you disagree. *** This bug has been marked as a duplicate of bug 97894 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97894] LibreOffice windows should have a minimum size
https://bugs.documentfoundation.org/show_bug.cgi?id=97894 Stéphane Guillou (stragu) changed: What|Removed |Added CC||adalbert.hans...@gmx.de --- Comment #18 from Stéphane Guillou (stragu) --- *** Bug 144237 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 153911] Warning when opening files with other files already open
https://bugs.documentfoundation.org/show_bug.cgi?id=153911 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #9 from m.a.riosv --- Does it happen opening files in other folders? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151040] Logo in Start Center only shows some pixels
https://bugs.documentfoundation.org/show_bug.cgi?id=151040 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||3673 CC||stephane.guillou@libreoffic ||e.org --- Comment #15 from Stéphane Guillou (stragu) --- Can't reproduce on Ubuntu 20.04 with GNOME 3.36.8, Adwaita, and lo 7.5.2.2. The steps are very similar to bug 143673, which was fixed in 7.5.0. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148647] LO pastes previously copied content instead of what was last copied from other app (Windows 10; see comment 11)
https://bugs.documentfoundation.org/show_bug.cgi?id=148647 Stéphane Guillou (stragu) changed: What|Removed |Added CC||sbnsj...@gmail.com --- Comment #15 from Stéphane Guillou (stragu) --- *** Bug 154520 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 154520] Paste function fails to work after 20 or so pastings from other programs
https://bugs.documentfoundation.org/show_bug.cgi?id=154520 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|--- |DUPLICATE CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |RESOLVED --- Comment #2 from Stéphane Guillou (stragu) --- Thank you, K. I assume you are on Windows. If that's the case, I am pretty confident this is a duplicate of bug 148647. Please see the comments there, especially comment 10. It might be related to opening another app while working on the document. Feel free to set back to unconfirmed if you think it's not the same issue. *** This bug has been marked as a duplicate of bug 148647 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154790] Copy and paste alter all Heading paragraph styles throughout the remainder of the document
https://bugs.documentfoundation.org/show_bug.cgi?id=154790 --- Comment #4 from ajlittoz --- This bug report is a follow-on of https://ask.libreoffice.org/t/stop-automatically-adding-a-tab-at-the-start-of-every-line-with-a-heading-style/90406/6 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154813] BUG in simple Division !!!
https://bugs.documentfoundation.org/show_bug.cgi?id=154813 --- Comment #11 from ady --- See: https://help.libreoffice.org/latest/en-US/text/scalc/guide/relativ_absolut_ref.html Although I think this should not be done as a general rule, I am posting the following link in order to hint others that they should not report "bugs" before some minimal web search. https://support.microsoft.com/en-us/office/switch-between-relative-absolute-and-mixed-references-dfec08cd-ae65-4f56-839e-5f0d8d0baca9 Please next time perform a web search, or go to https://ask.libreoffice.org This site is for bug reports. Thank you. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154534] Can't view the Main menu bar, while choosing the sub design menu.
https://bugs.documentfoundation.org/show_bug.cgi?id=154534 Dieter changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||dgp-m...@gmx.de --- Comment #1 from Dieter --- Priyanka, do you have the same problem also with actual version LO 7.5? => NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154813] BUG in simple Division !!!
https://bugs.documentfoundation.org/show_bug.cgi?id=154813 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG --- Comment #10 from Stéphane Guillou (stragu) --- (In reply to stefan from comment #7) > Dear Support Team, > Thank you for the quick response. I can live with conclusion of using "$" > but I must admit, that the MS-(exivalanet/evil/as-you-like-to-call-it) is > somewhat more intuitive. > I will still keep with LibreOffice (thank you so > mutch), but some people might be confused like me in the first try. You will find that MS Excel behaves the same: dragging that cell down will update relative references, resulting in the same values. Closing as "not a bug". Thank you both! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154816] New: Can't refresh control after selecting it with mouse click
https://bugs.documentfoundation.org/show_bug.cgi?id=154816 Bug ID: 154816 Summary: Can't refresh control after selecting it with mouse click Product: LibreOffice Version: 7.5.2.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: lowell_frie...@live.com Description: I have a form with multiple subforms, some of which are linked to tables that are used to populate dropdown boxes in other subforms. After adding another record into a tables, I need to hit "Refresh Control" in order for the new record to appear in the drop down box and to be able to select it. So far, so good. However, even when I have selected a column or cell in a subform that I want to refresh the control for, the refresh control button is grayed out. I often have to click around several times in several different subforms on my form before I can refresh the control I want to refresh. I'm not certain this is as much a problem with the refresh control button as it is a general problem having to do with mouse clicks not appropriately selecting what the click is intended to select. My mouse clicks *appear* to select what I want them to, but then I can't do what I want to do in that cell on the form. Sometimes I will have selected a cell to type something into but the text I type gets entered into a cell on the subform I was previously working in. Steps to Reproduce: 1.Enter data into a cell in a subform. 2.Select a cell in another subform. 3.Attempt to refresh control. Actual Results: The refresh control button remains greyed out. Expected Results: The refresh control button should be available to hit refresh. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.5.2.2 (X86_64) / LibreOffice Community Build ID: 50(Build:2) CPU threads: 12; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: en-CA (en_CA.UTF-8); UI: en-US Ubuntu package version: 4:7.5.2~rc2-0ubuntu0.22.04.1~lo1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154781] Keyboard input un-does paste (if cell was previously empty)
https://bugs.documentfoundation.org/show_bug.cgi?id=154781 --- Comment #9 from Jim Avera --- @ady I think we are talking past each other. What you said about edit mode is clear. The problem I see is that the initial paste does not enter edit mode, but typing does. They should (IMO) be handled the same. For example, if user clicks once and types "A", the "A" replaces existing content; fine. If the user then types "B", it is appended and does not erase the "A", and so-forth. In the same way, if the user clicks once and pastes "A", it replaces existing content; fine. But the next user input erases the "A" when it should append. What I am saying is that pasting should have *exactly* the same effects as typing the same content on the keyboard. Everywhere. -Jim -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154813] BUG in simple Division !!!
https://bugs.documentfoundation.org/show_bug.cgi?id=154813 --- Comment #9 from ste...@klerx4u.de --- Created attachment 186677 --> https://bugs.documentfoundation.org/attachment.cgi?id=186677=edit confusing Row "drag" calc -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154813] BUG in simple Division !!!
https://bugs.documentfoundation.org/show_bug.cgi?id=154813 --- Comment #8 from ste...@klerx4u.de --- Yust to make my confusion clear- pls see attaches screenshot -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154815] New: UI: Cell cursor width has increased
https://bugs.documentfoundation.org/show_bug.cgi?id=154815 Bug ID: 154815 Summary: UI: Cell cursor width has increased Product: LibreOffice Version: 7.4.0.0 alpha0+ Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: flklb-b...@t-online.de Since 7.4.0.0 I noticed an increased frame thickness of the selected cell cursor (2px -> 3px), which looks a bit odd to me; it also makes some cells harder to read. Can the thickness be configured somewhere? I cannot seem to find a setting for this. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154813] BUG in simple Division !!!
https://bugs.documentfoundation.org/show_bug.cgi?id=154813 --- Comment #7 from ste...@klerx4u.de --- Dear Support Team, Thank you for the quick response. I can live with conclusion of using "$" but I must admit, that the MS-(exivalanet/evil/as-you-like-to-call-it) is somewhat more intuitive. > I will still keep with LibreOffice (thank you so mutch), but some people might be confused like me in the first try. PLS keep up the good work. Kind Regards S.Klerx -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154814] New: Animated items display in wrong order when returning to previous slide
https://bugs.documentfoundation.org/show_bug.cgi?id=154814 Bug ID: 154814 Summary: Animated items display in wrong order when returning to previous slide Product: LibreOffice Version: 7.4.6.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rtrink...@icloud.com Created attachment 186676 --> https://bugs.documentfoundation.org/attachment.cgi?id=186676=edit Test file demonstrating animation problems when returning from previous slide When in presentation mode, animated items such as bulleted text do not display in the correct order when the user returns to a previous slide. Expected behavior: when returning to a previous slide by pressing backspace or left arrow, the previous slide should appear in its "final" state, with all animations having completed. In my case, that means that all bulleted items should appear. In the attached sample file, the only animations are bulleted text items that should enter individually one at a time, one per click. Current behavior: when returning to a previous slide by pressing backspace or left arrow, some animated items appear but some do not. When I proceed to press backspace again, animated items do not disappear in order and some items. Please see the attached file as an example. I know that this sounds like a duplication of another bug (#137454), but that other bug is listed as solved yet the problem persists in 7.4.6.2. To reproduce: 1. Open attached test file. 2. Navigate to third (last) slide. 3. Enter presentation mode with this slide (shift-F5) 4. Press backspace. The previous slide appears, but the top bullet does not display. 5. Press backspace again. Two bullets disappear. Only the bottom bullet should disappear. 5. Press backspace again. All bullets disappear. At this point, only two bullets were visible, so the third (bottom visible) should disappear, leaving the second visible. The first bullet is never visible, but of course it should be. This behavior happens on most of my Impress files. As a teacher who often needs to return to previous slides, I experience this bug daily. (Thanks to devs for their hard work!) My system: LO 7.6.4.2, Ubuntu Linux 22.10 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154813] BUG in simple Division !!!
https://bugs.documentfoundation.org/show_bug.cgi?id=154813 --- Comment #6 from ste...@klerx4u.de --- OK got some "hint"- in Row H -> the usage of "$" solves the issue in some way: =$H$1/[scaling]. But the behavior is strange, as the tool does not recognize the reference point and that every 2nd line is "0" is also irretating. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154813] BUG in simple Division !!!
https://bugs.documentfoundation.org/show_bug.cgi?id=154813 --- Comment #5 from Rafael Lima --- The problem here is simple. You're always dividing H1 by the values in column C, but the value of H1 is fixed. When you drag down the formula, H1 gets updated downwards (H2, H3, H4...) as well as column C (C3, C4, C5...). But in the case of column H, since you want to keep it fixed in H1, you need to lock it. For that, replace H1 in the formula by $H$1, which locks the column/row. Closing this as NAB. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154813] BUG in simple Division !!!
https://bugs.documentfoundation.org/show_bug.cgi?id=154813 --- Comment #4 from ste...@klerx4u.de --- Created attachment 186675 --> https://bugs.documentfoundation.org/attachment.cgi?id=186675=edit screenshow - weired results -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154813] BUG in simple Division !!!
https://bugs.documentfoundation.org/show_bug.cgi?id=154813 --- Comment #3 from ste...@klerx4u.de --- As I could not reply to the request I try to fill this form (unconveinient). Reply was: Sure--- try this file an drag down colum H (h3 down to h17) - you should immedialtly see the problem. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154386] [META] XML Form
https://bugs.documentfoundation.org/show_bug.cgi?id=154386 Bug 154386 depends on bug 154734, which changed state. Bug 154734 Summary: XML Form Document: All binded fields will be shown as fields with wrong content - except fields, which have wrong content. https://bugs.documentfoundation.org/show_bug.cgi?id=154734 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154813] BUG in simple Division !!!
https://bugs.documentfoundation.org/show_bug.cgi?id=154813 --- Comment #2 from ste...@klerx4u.de --- Created attachment 186674 --> https://bugs.documentfoundation.org/attachment.cgi?id=186674=edit simple statistic chart -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154813] BUG in simple Division !!!
https://bugs.documentfoundation.org/show_bug.cgi?id=154813 Rafael Lima changed: What|Removed |Added CC||rafael.palma.l...@gmail.com --- Comment #1 from Rafael Lima --- Can you share a file with a more concrete example of what the problem is? With your description I cannot reproduce the problem. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154813] New: BUG in simple Division !!!
https://bugs.documentfoundation.org/show_bug.cgi?id=154813 Bug ID: 154813 Summary: BUG in simple Division !!! Product: LibreOffice Version: 7.5.2.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ste...@klerx4u.de Description: Dear Libre Office Team, I found a strange behavior in when calculating a simple statistic, with a division. When filling a Calc Chart with values and try to use a division to get results like / power per time -> and be dragging down on a valid formula, every second value is calculates wrong. -> dooing this cell-by-cell works, but is not very user frendly for a bigger number of values. Kind Regards, S.Klerx Actual Results: With manual cell-by-cell it works, but it is not userfrendly ! Expected Results: Dragging down on a valid formula shows the correct values. Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: de Module: SpreadsheetDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: yes -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154766] management of ellipsis variants
https://bugs.documentfoundation.org/show_bug.cgi?id=154766 --- Comment #8 from toddwar...@duck.com --- (Note, I didn't file a bug. I filed an RFE.) Anyway . . . I am just adding this bit to clear things up though I see this as being dismissed, but someone may find it educational someday. 1. I keep typoing. Grr. AP-style (Associated Press) is what I meant. That's the style guide that drove the 3-dots, no-spacing-between formatting, even though the other is more common. Coincidentally, APA-style (largely only used by the shrink community) also adopted that style. Regardless . . . 2. I see how you're fundamentally not understanding this now. You see an ellipsis as three dots in a row. Which it isn't. For example, at the end of a sentence your eyes may see 4 dots, but that's not what is happening. It's an ellipsis and a period. An ellipsis is treated as a word. An unbreakable, single-character word. Grammar and spell checkers and word counters see it as a word. A word that has a meaning: an ellipsis. As I said, I was just hoping there was a better workaround than changing up the auto-correct to dish out a .[NBSP].[NBSP]. but perhaps I was hoping for too much. Maybe the Unicode community will solve this for us. Have a great weekend, folks. -t -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154756] Vertical text direction results in rotation, not vertical text direction
https://bugs.documentfoundation.org/show_bug.cgi?id=154756 --- Comment #8 from Eyal Rozenberg --- (In reply to Regina Henschel from comment #7) > LibreOffice renders it in one way, when you set the text direction. Thereby > the text direction is often inherit from the layout environment of an object. I'm not sure I understand this sentence. > If you need a different glyph orientation for a portion of text, you can use > the settings in the 'Position' tab of the character properties. I need LO to do what I told it to do, which is render my English text in vertical writing mode. Now, given the information at the links - if the larger-piece-of-text is in a CJK language/script but contains a smaller-piece-of-text in Western script, or even in a Western language - then it would be acceptable for LO to diverge from literal conformance to the settings made. But even then, the default should probably be some kind of reasonable heuristic. An override of the heuristic should not necessitate setting a value for each and every stretch of Western-script text in a CJK document - that is very cumbersome. > Implementation of a "stacked" writing-mode for paragraphs and for frames is > missing. If you want such, please write an enhancement request. LO claims to offer vertical writing mode, and instead rotates. Fixing this is fixing a bug, not making an enhancement. It is also may be considered kind of a bug to conflate rotation of stretches of text with the writing direction, but I don't have a strong opinion on that. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154790] Copy and paste alter all Heading paragraph styles throughout the remainder of the document
https://bugs.documentfoundation.org/show_bug.cgi?id=154790 --- Comment #3 from Dale --- See attachments for a sample of what happens when the user pastes from Sql Server Management Studio -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154790] Copy and paste alter all Heading paragraph styles throughout the remainder of the document
https://bugs.documentfoundation.org/show_bug.cgi?id=154790 --- Comment #2 from Dale --- Created attachment 186672 --> https://bugs.documentfoundation.org/attachment.cgi?id=186672=edit Document prior to the paste -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154812] New: Unable to click on the left side of a formula when it is centered in a cell
https://bugs.documentfoundation.org/show_bug.cgi?id=154812 Bug ID: 154812 Summary: Unable to click on the left side of a formula when it is centered in a cell Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rafael.palma.l...@gmail.com When you open a formula that is centered in a cell and it extends beyond the column width, it is not possible to click the formula text to the left of the cell. It is however possible to click the text to the right of the cell. Steps to reproduce: 0) Create a blank Calc document 1) Enter a long formula text on a cell, f.i. =SUMPRODUCT(C10:C16;D10:D16)-SUMPRODUCT(F11:F15;G11:G15) 2) Do not change its alignment for now... simply double-click the cell and notice that the formula text will align to the left edge of the column where it is located, and all formula text is clickable (this is OK). 3) Now click outside the cell to stop editing the formula. Use the toolbar to center the cell contents 4) Double-click the cell. The formula text will be centered and the formula text that goes beyond the left column edge is not clickable (Not OK). The formula text to the right is clickable as expected. >From my testing, it happens in gtk3, kf5 and gen. System info Version: 7.5.2.2 (X86_64) / LibreOffice Community Build ID: 50(Build:2) CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Ubuntu package version: 4:7.5.2~rc2-0ubuntu0.22.10.1~lo1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154790] Copy and paste alter all Heading paragraph styles throughout the remainder of the document
https://bugs.documentfoundation.org/show_bug.cgi?id=154790 --- Comment #1 from Dale --- Created attachment 186671 --> https://bugs.documentfoundation.org/attachment.cgi?id=186671=edit Document state after the paste from SSMS -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154202] Annoying extension icon (MultiSave) on standard toolbar (Win8.1)
https://bugs.documentfoundation.org/show_bug.cgi?id=154202 --- Comment #8 from teodorko...@yahoo.com --- Okay, thanks! You can close the issue. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143754] No Help page for Tools > Options… > Language settings > English Sentence Checking
https://bugs.documentfoundation.org/show_bug.cgi?id=143754 --- Comment #14 from Olivier Hallot --- This English Sentence Checking feature is actually a set of python regex run by LightProof grammar checker, and are part of the bundled extensions released with LibreOffice. https://cgit.freedesktop.org/libreoffice/lightproof The English set of rules is configurable in the dialog. However, other languages such as pt-BR has another set of rules and the settings dialog is different, with some ad-hoc linguistic rules and different grammar checking. The Sentence checking is in the dictionaries/ submodule. Since the grammar checking varies per language, I find strange to create a Help page translatable with Portuguese rules on a English UI. But the dialog created by the extension could have a Help button to open a wiki page with the rules explained in the user or document language. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154756] Vertical text direction results in rotation, not vertical text direction
https://bugs.documentfoundation.org/show_bug.cgi?id=154756 --- Comment #7 from Regina Henschel --- LibreOffice renders it in one way, when you set the text direction. Thereby the text direction is often inherit from the layout environment of an object. If you need a different glyph orientation for a portion of text, you can use the settings in the 'Position' tab of the character properties. The preview icon can be improved. Implementation of a "stacked" writing-mode for paragraphs and for frames is missing. If you want such, please write an enhancement request. We should use this bug report to improve the misleading preview icon. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151624] Fix "Formula Object" tool in the Tabbed UI
https://bugs.documentfoundation.org/show_bug.cgi?id=151624 --- Comment #3 from Rafael Lima --- Hi Andreas, this bug has been assigned to you for about 5 months. Are you still working on this issue? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113285] [META] Crash report system bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=113285 Bug 113285 depends on bug 113286, which changed state. Bug 113286 Summary: Crash report url/link should be clickable in Crash Report dialog https://bugs.documentfoundation.org/show_bug.cgi?id=113286 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154792] Calc Round Down is Rounding Up for some values.
https://bugs.documentfoundation.org/show_bug.cgi?id=154792 Eike Rathke changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |er...@redhat.com |desktop.org | Status|NEW |ASSIGNED Summary|Calc Round Down is Rounding |Calc Round Down is Rounding |Up |Up for some values. --- Comment #9 from Eike Rathke --- There is no decimal representation in binary floating point hence any decimal "nth digit" does not exist for values other than multiples of powers of two. Period. (In reply to NOYB from comment #8) > If the user want's it rounded down to 2 digits then 0.93 > is the correct answer/result for a value of 0.9395. It is not if that 0.9395 is a result of the calculation of 8.94-8 because the exact number 0.94 is not representable in binary floating point and the nearest value is 0.939946709294817992486059665679931640625 and the user expects a ROUNDDOWN(8.94-8;2) to be ROUNDDOWN(0.94;2) to equal 0.94 (which it never is). I don't say we can't have a better implementation, I just state the complexities. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154734] XML Form Document: All binded fields will be shown as fields with wrong content - except fields, which have wrong content.
https://bugs.documentfoundation.org/show_bug.cgi?id=154734 Julien Nabet changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |serval2...@yahoo.fr |desktop.org | --- Comment #5 from Julien Nabet --- (In reply to Buovjaga from comment #4) > Bibisected with linux-64-7.3 to 14cfff500e93f0d6cbf8412065feea85c01ea81d > Pass context and resource string down to boost::locale separately Great job! I've submitted a patch here: https://gerrit.libreoffice.org/c/core/+/150433 It was unrelated to decimal separator. With this fix, fields show as valid but as soon as you play with decimal containing numbers different of 0 after decimal sep, it fails. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132704] Draw freezes when creating a new style
https://bugs.documentfoundation.org/show_bug.cgi?id=132704 --- Comment #5 from BogdanB --- (In reply to Regina Henschel from comment #3) > It is not functional. LibreOffice freezes not totally, 'Save as' and context > menu work, for example. But the edit area does not allow to deselect the > shape. > > I have tested it with Version: 7.0.0.0.alpha0+ (x64) > Build ID: e3517eefed2d4767648cb52d4a9863908cadc3d8 > CPU threads: 8; OS: Windows 10.0 Build 18362; UI render: Skia/Vulkan; VCL: > win; > Locale: de-DE (en_US); UI-Language: en-US > Calc: threaded Retested. The same now Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: f92721bf182952be88b0349a17e46b684d630c29 CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154796] Weird things (don't) happen when trying to create a "New" Presentation Style
https://bugs.documentfoundation.org/show_bug.cgi?id=154796 Regina Henschel changed: What|Removed |Added Ever confirmed|0 |1 CC||rb.hensc...@t-online.de Status|UNCONFIRMED |NEW --- Comment #1 from Regina Henschel --- Clearly a bug in the UI. The "New" item must not exist in the presentation style category if a text box is selected. Tested with Version: 7.5.2.2 (X86_64) / LibreOffice Community Build ID: 53bb9681a964705cf672590721dbc85eb4d0c3a2 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97881] Freeze when selecting style for drop cap
https://bugs.documentfoundation.org/show_bug.cgi?id=97881 --- Comment #6 from BogdanB --- No problem for me, please retest Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: f92721bf182952be88b0349a17e46b684d630c29 CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154766] management of ellipsis variants
https://bugs.documentfoundation.org/show_bug.cgi?id=154766 --- Comment #7 from V Stuart Foote --- (In reply to toddwarner from comment #6) > Note: This bugzilla is not asking how to insert a U+2026. That's not the > issue. It's that the U+2026 is an APA-styled ellipsis (three dots, no > spacing between). Most other styles require and ellipsis formatted as three > dots, spaced between. I hope that wasn't confused. Anyway . . . > Hmm, APA calls for 3 dot, or 4 dot when ending a sentence. So technically using the Unicode U+2026 HORIZONTAL ELLIPSIS should not be used at all ;-) Just remove, or modify, the autocorrect substitution to meet your preference. While other CSL that call for spaces, allow either NBSP or NNBSP between the dots. Point is LibreOffice already support all those variations, and that you've made no case nor justified a work flow that is not supported. IMHO => NAB -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 89263] Fit object to paper format does not work when changing orientation to landscape
https://bugs.documentfoundation.org/show_bug.cgi?id=89263 --- Comment #9 from BogdanB --- Repro also with Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: f92721bf182952be88b0349a17e46b684d630c29 CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154766] management of ellipsis variants
https://bugs.documentfoundation.org/show_bug.cgi?id=154766 --- Comment #6 from toddwar...@duck.com --- Note: This bugzilla is not asking how to insert a U+2026. That's not the issue. It's that the U+2026 is an APA-styled ellipsis (three dots, no spacing between). Most other styles require and ellipsis formatted as three dots, spaced between. I hope that wasn't confused. Anyway . . . Can someone comment who has written for traditional publication, please? Maybe that is no one. Dunno. What you shared is 100% a workaround. Well, except for this, which doesn't even rise to that level: "Not seeing an issue. U+2026 with OpenType stylistic alternative for the opened spacing of the ellipsis is already supported--UI is the Character dialog." That only works if you use a typeface that will support it (none do that I know of, and not Times New Roman) and only if you know how to trigger it. 99.999% of the users do not. I have long had LibreOffice autocorrect to .[NBSP].[NBSP].. That is definitely a workaround and not an end solution. That is also what everyone largely does, or they just use three spaced-out dots and individually deal with the resulting word wrap and formatting issues. This is fine-ish. But it is a brute-force, non-ideal solution. Plus, it breaks the grammar-checker and other things since LibreOffice doesn't see an ellipsis. Whatever. My RFE was a stab in the dark. I expected this response pretty much since no one from the word-processing world has resolved it. It'll take the Unicode community to make it a reality, I am sure. In the meantime, I hope I triggered someone to think about it. Cheers. -t P.S. The two dashes '--' that you used above instead of an emdash '—' is also no longer a "workaround" if you are publishing professionally. An actual emdash is expected. Thank goodness that's available. Maybe someday the Chicago/MLA/etc-style ellipsis will be as well. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154799] The ODF partitioning of scripts/languages into "Western", "RTL + CTL" and "Asian" is invalid
https://bugs.documentfoundation.org/show_bug.cgi?id=154799 --- Comment #4 from Eyal Rozenberg --- (In reply to Eyal Rozenberg from comment #3) > I didn't say the definition was unclear, I said it was invalid. Wait, I take that back. I said I "couldn't find an answer". So, there is a definition, but it doesn't answer what makes a script complex, it just says which scripts are defined to be complex. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138220] calc: calculation: roundup: rounddown: fail in 7.1 alpha
https://bugs.documentfoundation.org/show_bug.cgi?id=138220 Eike Rathke changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |er...@redhat.com |desktop.org | Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154597] FILEOPEN DOCX image position wrong on page with vertical text direction
https://bugs.documentfoundation.org/show_bug.cgi?id=154597 --- Comment #2 from BogdanB --- In the DBG version of LibreOffice I get this warnings at opening the file: warn:sfx.dialog:286858:286858:sfx2/source/dialog/filtergrouping.cxx:359: already have an element for WordPerfect warn:sfx.dialog:286858:286858:sfx2/source/dialog/filtergrouping.cxx:359: already have an element for writerweb8_writer_template warn:sfx.dialog:286858:286858:sfx2/source/dialog/filtergrouping.cxx:359: already have an element for writerglobal8 warn:oox:286858:286858:oox/source/drawingml/shapecontext.cxx:127: ShapeContext::onCreateContext: unhandled element: 4007 warn:legacy.osl:286858:286858:oox/source/helper/storagebase.cxx:67: StorageBase::StorageBase - missing base input stream Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: f92721bf182952be88b0349a17e46b684d630c29 CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154795] Font selection pane offers choice of "language" - which isn't.
https://bugs.documentfoundation.org/show_bug.cgi?id=154795 Regina Henschel changed: What|Removed |Added CC||rb.hensc...@t-online.de --- Comment #1 from Regina Henschel --- The field there sets a language/country pair. If you select "English(Israel)" you get fo:language="en" and fo:country="IL". You need this information, for example, to select the appropriate dictionaries, thesauri, hyphenation rules, and AutoCorrect entries. (In reply to Eyal Rozenberg from comment #0) > > Also, with the inflation of choices, we have a dozen kinds of English which > aren't about a different language - mostly a waste of space, and making it > easier to make choices with misleading/invalid information. Same goes for > Arabic in the RTL/CTL group: 15 different kinds or so. Are you sure there exists items, which are not considered somewhere? For example, you can define your own AutoCorrect entries for each of the items in this 'Language' drop-down list. -- You are receiving this mail because: You are the assignee for the bug.
