Bug 140906 - Autocorrect fails on :---:
Summary: Autocorrect fails on :---:
Status: RESOLVED DUPLICATE of bug 134940
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.1.0.3 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-09 07:49 UTC by Mark Coetsee
Modified: 2021-03-23 07:46 UTC (History)
1 user (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 Mark Coetsee 2021-03-09 07:49:37 UTC
Description:
Autocorrect: on typing :---: I now have to leave a space after the last word typed e.g. "...typed :---: " and then hit return before the autocorrect works, which also introduces a new line, which is very inconvenient... 

Steps to Reproduce:
1. As above...
2.
3.

Actual Results:
As above...

Expected Results:
Immediate autocorrect to m dash...


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Immediate autocorrect to m dash...
Comment 1 Xisco Faulí 2021-03-22 14:39:08 UTC
I can't reproduce it in

Version: 7.2.0.0.alpha0+ / LibreOffice Community
Build ID: 5262a9e88037decc26da84e7fa62f2955d4cdb85
CPU threads: 4; OS: Linux 5.7; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 2 [REDACTED] 2021-03-22 22:24:16 UTC
No repro using

Version: 7.1.1.2 / LibreOffice Community
Build ID: fe0b08f4af1bacafe4c7ecc87ce55bb426164676
CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: kf5
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 3 [REDACTED] 2021-03-22 22:28:09 UTC
Can't reproduce using

Version: 7.0.5.2
Build ID: 64390860c6cd0aca4beafafcfd84613dd9dfb63a
CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: kf5
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 4 Xisco Faulí 2021-03-23 07:46:17 UTC
I believe this is a duplicate of bug 134940

*** This bug has been marked as a duplicate of bug 134940 ***