Normally, the insertion of two regular dashes "--", (HTML --) when the previous character is part of a regular word will result in the two regular dashes automatically being converted to an "em" dash--the long dash used in English to set off long tangential components of the sentence, such as this one--after another word and a space is inserted. If, however, the previous character is a closing parenthesis, the em-dash is not formed. In other words, typing asdf--asdf<space> will cause the two dashes to become an em dash, but typing some stuff (I guess)--asdf<space> will not trigger the conversion. This is a bug and Microsoft Word has correctly converted the dash in the latter situation for some time now. Thank you for your attention, please let me know if more detail is required.
Not reproduced. Linux-only, perhaps. Will have to test later. Win 7 Pro 64-bit, Version: 5.0.2.2 (x64) Build ID: 37b43f919e4de5eeaca9b9755ed688758a8251fe Locale: fi-FI (fi_FI)
Just found an additional condition. There has to already be an em dash present in the document, or something along those lines. To reproduce, type: asdf--as df)--asdf<space> The first one should become an em dash but not the second. Sorry for the misleading first report.
Thanks, could repro. Win 7 Pro 64-bit, Version: 5.0.2.2 (x64) Build ID: 37b43f919e4de5eeaca9b9755ed688758a8251fe Locale: fi-FI (fi_FI) 4.3.0.1
issue reproducible under Win8.1 x64 too, using LibO 5.3.0.0.alpha0+ Build ID: e2f6c7f0d0cc14f851d7028ff846c5dc658a81c6 CPU Threads: 4; OS Version: Windows 6.29; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2016-10-10_23:08:02 Locale: it-IT (it_IT); Calc: group you need to have "Autocorrect\Autocorrect Options...\Options\Replasce dashes" setting on to see the bug. a workaround is to use wildcard autocorrection and set this entry: Replace .*)--.* with: em dash that should overcome the issue with closing parenthesis. another workaround is to disable "Replace dashes" at all and use an even simpler autocorrect rule such as: Replace .*--.* with: em dash some people however would prefer to use: .*--.* for en dash and .*---.* for em dash
** 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
Dear Bruno Beltran, 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
Just commenting in response to the auto-QA bot, this bug is still present in the latest libreoffice for arch Version: 7.0.4.2 Build ID: 00(Build:2) CPU threads: 16; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US 7.0.4-3 Calc: threaded Cheers, Bruno
I am using Ubuntu Hirsute, LO 7.2. I observe the same behavior. Two minuses to em-dash used to require: a) a leading word or character b) a space to end the trailing word. The first requirement is not acceptable in Spanish. We use leading em dashes as quote marks. I am in an English locale, but I often use a Spanish keyboard. Now, since about the 6.0 release, AutoCorrect does not function properly. It flags the two minuses as an error, and forces me to manually choose "en dash or em dash" using right-click. Resetting the spell check options has no effect. Thanks.
Just started using new Writer version. This feature stopped working. I believe the troggering event was an ending quotation mark. Once the auto-em flipped off, I can't get it flipped back on! And the two -- looks very weird now, too.
That was already the case in OOo 3.3, so it is inherited: (a)--a<enter> would work (a a)--a<enter> wouldn't However, it is now fixed in: Version: 7.6.0.0.beta1 (X86_64) / LibreOffice Community Build ID: be55b15d98c5f059483845a183fcb5ea8023d27c CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Tested with the string: (a a)--a<enter> Fix bibisected with linux-64-7.6 repo to commit 075ecc1c31199d0fd0f930cf1b803b04a3b17ce8, so marking as duplicate of bug 155407. Thanks everyone! (Coburn and spikeof65: I marked your comments as "off-topic", as the issue described here is quite specific and should remain focused. If you have other issues with the "Replace dashes" autocorrect option, please see if it was already reported in https://bugs.documentfoundation.org/showdependencytree.cgi?id=103341&hide_resolved=1 and if not, create a new report. Thank you!) *** This bug has been marked as a duplicate of bug 155407 ***