Description: Try to make a auutocorerction rule for greek language was hard: pattern `υυ change to U774 (COMBINING BREVE) works only if type it at space. if type some word and place `υυ - nothing chages, inserting pattern in a word - also nothing changes. Same happens with Russian default autocorrections : pattern <-> - works fine only after space. if pattern types after word - char '<' leave after word, and only '->' will be corrected. Steps to Reproduce: 1.set russian language on text, and turn on autocorrection on type 2. type some word with <-> like гыгыг<-> you get autocorrection гыгыг<→ 3. set text language greek. 4. add to greek autocorrection rules `υυ change to U774 (COMBINING BREVE) 5. type after space `υυ here you got U774 character after change 6. type some letter and `υυ - like ο`υυ no autocorrection here Actual Results: autocorrection works only at begining of word, and it changes only when some space delimiter enter (space, tab, enter) Expected Results: expectis normal autocorrection during word type: first char of a entered pattern must normaly take into account. expects normal autocorrection exactly after pattern recognize - when all chars of pattern typed, not only after space/tab/enter Reproducible: Always User Profile Reset: No Additional Info: bug has explored on libreoffice 6.0.5 on win8.1 (x64)
release 6.1 also same bug
I've tried on 6.1.1.2 but it doesn't result, can you send me some other infos please? I moved this bug with status: NEEDINFO
>Eugenio zoppè Well, i try new version v6.1.2.1 with same results. Maybe significant that i use russian windows 8.1 and russian build of LibreOffice? this bug reproduces even on English US language: by default english autocorrection dictionary have rule about "<->" 1) type " <-> " - this leads autocorrection -> ↔ 2) type " a<-> " - this produces " a<→ " 3) type " a<->." - this produces " a<→." 4) type " a<->/" - this nothing chages So, you see: - any letter before autocoreection pattern breacs first char. - autocorrection works only on whole word. pattern word must be noted with space or delimiters. contrary, MS windows autocorrection works perfecty - pattern triggers in any position of typed text, and replaces directly on typing.
Repro. In 3.3.0, it did not even produce the last arrow, so looks like someone changed something after it. Let's still call it inherited. Arch Linux 64-bit Version: 6.3.0.0.alpha0+ Build ID: e77beebb0d839f5dc0d4f9c4fd7cc9b7ccfd0175 CPU threads: 8; OS: Linux 4.20; UI render: default; VCL: gtk3; Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US Calc: threaded Built on 16 February 2019
Dear alexrayne, 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
autocorrection is still like shit in LO7.1 : used russian language, have set autocorrection on type. default rules have: 1) -- : – --> : → -+ : ± ok, try type --> , and on '>' it corrects two first chars, so have --> : –> expects that will bw used longer rule so --> should change to → if type a-->, it keep char after letter, so have a--> : a–→ it not better if try to enter -+ - it not autocorrects. So looks like autocorrect on -+ mulfunction completely.
Dear alexrayne, 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