Bug 154049 - *.-operator-endowed autocorr entries do not check for other *.-endowed entries around them.
Summary: *.-operator-endowed autocorr entries do not check for other *.-endowed entrie...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.5.1.2 release
Hardware: All All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: AutoCorrect-Complete
  Show dependency treegraph
 
Reported: 2023-03-07 21:26 UTC by JoJo Tuinstra
Modified: 2025-07-06 03:10 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description JoJo Tuinstra 2023-03-07 21:26:02 UTC
Description:
for example, if I have .*`euro`.* autocorrect to €, .*`a_acute`.* to á, and .*`e_acute`.* to é, `euro``a_acute``e_acute` does not correct to €áé as desired but `euro`á`e_acute`.

Steps to Reproduce:
N/A

Actual Results:
N/A

Expected Results:
N/A


Reproducible: Always


User Profile Reset: No

Additional Info:
N/A
Comment 1 Julien Nabet 2023-03-08 07:13:49 UTC
On which LO version and on which env are you (macOS, Linux, Windows) ?
Last stable one is 7.4.5. If you don't use it, please give it a try.
Comment 2 JoJo Tuinstra 2023-05-22 21:06:18 UTC
Hi, sorry for the late response. I think I would have been on 7.5.1 at the time, on 7.5.3.2 now, x86_64 Windows 11, my current build is 25357.
Comment 3 QA Administrators 2023-05-23 03:14:29 UTC Comment hidden (obsolete)
Comment 4 Buovjaga 2023-07-06 12:56:11 UTC
Reproduced, but not sure if this is a limitation in the use of regular expressions.

Arch Linux 64-bit, X11
Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: e5e324a3420fc74fc147601bb125421e87060d93
CPU threads: 8; OS: Linux 6.4; UI render: default; VCL: kf5 (cairo+xcb)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 6 July 2023
Comment 5 Buovjaga 2023-07-06 13:22:18 UTC
Double checked in #libreoffice-dev - let's set this to NEW
Comment 6 QA Administrators 2025-07-06 03:10:43 UTC
Dear JoJo Tuinstra,

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