Created attachment 139981 [details] test case for replacement bug I've removed the three dots replacement (`.*...` -> `…`) in the Write autocorrect replacement list. This works as expected - if I open a new document and type three dots (and space), the three dots are not replaced. However, there is a pecular exception; if I paste into the same document certain text, and type three dots (and space), the three dots are now replaced. I've attached what I believe is the minimal test case for reproducing the problem. In order to reproduce the error: - remove the three dots replacement from Writer autocorrect options - open the attached document - type three dots (and space) The three dots will be replaced.
System information: - XUbuntu x86-64 16.04 Libreoffice information: Version: 6.0.1.1 Build ID: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk2; Locale: en-US (en_US.UTF-8); Calc: group
Created attachment 140435 [details] Even more minimal test case I reproduce. I removed the table of contents by editing the content.xml and re-zipped and I can still reproduce the behaviour. Here are the replacement rules for testers wanting to add them back after deleting from the rule list (they are near the end of the list after all the emojis): .*... … Arch Linux 64-bit Version: 6.1.0.0.alpha0+ Build ID: 856c57f20f9b07c686a854e0ccbb6ee3b0ee4791 CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on March 7th 2018
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Bug still present on v6.1.5.2.
Dear saverio.pub2, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
It turns out that this is not a bug. I've previously filed another bug for related reasons, and I got a clarifying answer. The reason is that replacements are per-locale, and documents have an associated locale; therefore, the removal of the replacement must be performed on the document locale, not on the default one. This is a bit confusing due to locale being multilayered; in the case of the minimal test case, it can be observer via `Tools` -> `Language` -> `For selection`, which will show `Italian (Italy)`. Removing the triple-dot from the replacement table for the `Italian (Italy)` language will yield the desired effect.