1. The "Replace Dashes" section of: https://help.libreoffice.org/7.2/en-US/text/shared/01/06040100.html gives a table of what dash replacements should occur. 2. Using Tools > AutoCorrect > Apply, two of items in the table do not work. A--B (A, minus, minus, B) A --B (A, space, minus, minus, B) 3. The others work, and all work if tested with "While Typing" Test conducted as follows: 1. Tools > AutoCorrect > AutoCorrect Options - Options tab uncheck all [T] fields. Uncheck all [M] fields, except for "Replace dashes" 2. Make sure to work in Default Paragraph Style 3. Enter the items in the table in a New Document. 4. Tools > AutoCorrect > Apply Question: Is the Help page wrong (and should be changed)? Or is this an implementation problem?
I am seeing similar results with the "autocorrect while typing" function, although it's actually worse than the OP--none of the replacements work in this instance. Note that I am running a slightly earlier version, v7.0.4.2, which is the latest packaged release available for Fedora 33. Test conducted as follows: 1. Tools > AutoCorrect > AutoCorrect Options - Options tab uncheck all [M] fields. Uncheck all [T] fields, except for "Replace dashes" 2. Make sure to work in Default Paragraph Style 3. Enter the items in the table in a New Document. Results: None of the replacements are made as listed in the table in the help file referenced in the OP. Specifically, these are the first though fourth and the seventh; the fifth & sixth don't result in any change, which is expected behavior. System information: Version: 7.0.4.2 Build ID: 00(Build:2) CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: en-US (en_US.utf8); UI: en-US Calc: threaded Kernel 5.10.15-200.fc33.x86_64 on Fedora 33
(In reply to Brian Young from comment #1) > Results: None of the replacements are made as listed in the table in the > help file referenced in the OP. @Brian - you did not mention if Tools > Options > While Typing is enabled? If not, then none of the replacements should be made.
(In reply to sdc.blanco from comment #2) > (In reply to Brian Young from comment #1) > > Results: None of the replacements are made as listed in the table in the > > help file referenced in the OP. > @Brian - you did not mention if Tools > Options > While Typing is enabled? > If not, then none of the replacements should be made. @sdc.blanco, I think you mean Tools > AutoCorrect > While Typing, yes? I do have that option ticked, so the replacements should be made as expected. Thanks for checking. I did find subsequently that the replacements *do* happen if I press [Enter] rather than [Space], as described in this bug report: https://bugs.documentfoundation.org/show_bug.cgi?id=140445
(In reply to Brian Young from comment #3) > @sdc.blanco, I think you mean Tools > AutoCorrect > While Typing, yes? Yes. > I did find subsequently that the replacements *do* happen if I press > [Enter] rather than [Space], as described in this bug report: > https://bugs.documentfoundation.org/show_bug.cgi?id=140445 Ok. Please note that this bug report is about "Apply" only, not about "While Typing".
I have this bug also. In order to get a leading em dash before a word, I used to have to type "a--word," hit the spacebar, and then LO would convert the two minuses to an em dash, and I could delete the leading "a" (dummy character). Awkward, but not too bad. Spellcheck wants you to have an em dash only between two words. In Spanish, for example, we use it instead of quote marks, and so it has to be at the beginning of a paragraph also. Now even that does not work. I have to do all the same things, and then wait for autocorrect to draw a blue line under the dash, and right-click. The option given is "en dash or em dash." I can then change the two minuses to an em dash manually. This is new since about the 6.0 release. I have deleted my profile. That does not work. I thought maybe it was because I was working on some documents created several years ago. It applies even in a brand new document. I also have gone into Spell Check Options and reset everything. That did not work. I tried specifying that two minuses are to convert to an em dash. That was the default anyway, and it did not work.
Repro already with 3.3.0 Arch Linux 64-bit Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: 41b012767feb8552b60a68c7be18d80c403304bf CPU threads: 8; OS: Linux 5.17; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Jumbo Built on 28 April 2022
Reproduced in recent master build: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 9fc0b2b9b96d87eb642a3b29e9dcb5d6273265eb CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded I tested it for both Default Paragraph and Body Text styles.
*** Bug 156542 has been marked as a duplicate of this bug. ***
Reproduced on: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1ec2e39cf4d5fe0a592bc783fd8bcdc4345c8cbd CPU threads: 6; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded
Dear sdc.blanco, 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
I have just tested with LibreOffice Writer 25.2.6.2 and first impression is that the issue is resolved. I will try and do some better testing and give another update, but a quick-and-dirty check looks good.
Indeed, Tools > AutoCorrect > Apply now works for the two mentioned examples from comment 0 Arch Linux 64-bit Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d0e936765b1b68d614271642629df6c615c7e9ae CPU threads: 8; OS: Linux 6.17; UI render: default; VCL: gtk3 Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: CL threaded Built on 8 October 2025