Steps to reproduce:
1. With a default user profile type three or more hyphens (-) and then press enter
The hyphens remain
LibreOffice draws a line because in a default setting the option "apply border" in "Tools - AutoCorrect Options - Options" is activated.
The reason this behaviour occurs is that the upper option in the "replacement table" (replace - by _) spoils it. It immediately replaces --- with _-- and then the "apply border" function won't go.
It takes a lot of time to figure this out and remove the upper issue from the "replacement table".
Operating System: All
Last worked in: 184.108.40.206 release
*** Bug 80824 has been marked as a duplicate of this bug. ***
Can confirm this.
Wasn't this discussed on the Dutch user list?
What would be your suggestion to solve this? Remove the autoreplacement option?
Exactly, it was discussed on the Dutch mailinglist. At least I brought it in on may fourth 2014 (vreemde samenloop). But it seemed more productive to create a bug of it.
I haven't tested if the bug occurs only in the Dutch version of LO.
A possible solution could be to not make autoreplace work if three or more dashes ( --- ) stand behind each other. Who would want it to work in such circumstances?
It's only a suggestion.
I see the version field is set 220.127.116.11, but the comment says it last works in 18.104.22.168. which version exactly does it not work?
I also see in Bug 80824 that the version which does not work should be 22.214.171.124. If that is true:
* Please upgrade to 4.1.6, which is the latest stable version. If it works in 4.1.6, the status should be WORKSFORME.
* If it doed not work in 4.1.6, the status should be WONTFIX, because 4.1.6 is EOL. You should either use a workaround or upgrade to 4.2.*.
hi there. the triple hyphen is again a possible source of autocorrect issues.
some people (including me) tried to use it as a replacement for "em-dash" and have seen autocorrect conflicts with concurrent double-hyphen as a replacement of "en-dash" (see the long discussion at bug 55292)
anyway I wonder why a "replace - by _" has been introduced in the Dutch version... can anybody explain me? I'm curious...
In my italian keyboard layout the hyphen and underscore are in the same key and can easily switched using the shift. is the situation different in the Dutch layout?
I totally agree. I may be not a real power user but I never had the need to replace "-" by "_". To do this automatically in my vision fills a non existing need or worse: it is confusing.
I totally agree with you... I wonder what's the rationale of a "-" by "_" replacement which I see is only present in the autocorrect list for Nederland languages like acor_nl-NL.dat and acor_nl-BE.dat (edited summary notes)
I'd like to hear feedback from Cor Nouws.
I think that such an autocorrect replacement like that should be removed (and it would be a very easy hack) but I need to know the opinion of a Dutchman first.
(In reply to comment #8)
> I'd like to hear feedback from Cor Nouws.
> I think that such an autocorrect replacement like that should be removed
> (and it would be a very easy hack) but I need to know the opinion of a
> Dutchman first.
Thanks Tommy. BTW: Pieter is Dutch too...
I don't have a problem to remove that autocorrect item at all. But do we know why it was added (always a good question before attempting to remove something :) )
Maybe Lázsló knows this ??
I knew Pieter is Dutch and he already said he doesn't see the reason for that "-" to "_" replacements. I asked your advise to hear a second opinion from a well known member of the Dutch community.
anyway I have inspected the acor_nl-NL.dat file which contains the autocorrect replacements for your language and I see that the replacement is not exactly "-" to "_" (hyphen -> underscore) like Pieter wrote but rather "-" to "–" (hyphen -> en-dash)
I have no knowledge of Dutch grammar and which are the cases you need an hyphen rather than an en-dash in your language, anyway that kind of autocorrect replacement still looks to me as a source of potential conflicts.
as far as I know, there's no keyboard layout including the en-dash character "–" and the trend to obtain that is to set a double hyphen to en-dash autocorrect entry like "--" to "–" (see also Bug 55292).
the current Dutch replacement seems unwise to me because it basically remaps the hyphen key to an en-dash and it makes basically impossible for a dutch to type a discreet hyphen " - " in a document... moreover has Peter noticed, it has conflicts with the triple hyphen pattern to draw an horizontal border.
this "hyphen to en-dash" Dutch autocorrect entry is not a new thing... I can trace it back to LibO 3.3.3 and OOo 3.3.0 as well so it's inherited from OOo and I think that Lazlo Nemeth has nothing to do with it (BTW is he Dutch? I thought he was Hungarian).
so my suggestion is to adopt the "double hyphen to en-dash" rule in Dutch locale as well to mimic what has already been done in other languages as well (I see that replacement already in French, Spanish, English and German autocorrect lists).
that would probably avoid conflict and make the Dutch autocorrect consistent with other languages as well.
my opinion and that we need to uniform the autocorrect entries for special characters like en-dash, em-dash etc. etc. in all languages as well.
please discuss this with other members of the Ducth and Belgian community, since that replacement is present in acor_nl-NL.dat and acor_nl-BE.dat files.
another Dutch autocorrect collision due to the "hyphen to en-dash" replacement is that when you type --> instead of the expected conversion to → you will get –->
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INVALID
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
This issue is still present in version 126.96.36.199.
bug was confirmed a lot of time ago, hence status is NEW
I think the Dutch team should get rid of that autocorrect entry which is causing the problem
(In reply to tommy27 from comment #10)
> so my suggestion is to adopt the "double hyphen to en-dash" rule in Dutch
> locale as well to mimic what has already been done in other languages as
> well (I see that replacement already in French, Spanish, English and German
> autocorrect lists).
They just removed it from the autocorrect list?
those other language never had such illogic "replace - by _" autocorrect entry
only dutch locales have it from OOo era, I don't know why.
(In reply to tommy27 from comment #16)
> those other language never had such illogic "replace - by _" autocorrect
> only dutch locales have it from OOo era, I don't know why.
It's not about replacing a dash with a under score.
It is about replacing a dash with a em-dash.
ok whatever... anyway as other language do, use 2 dash to obtain an em-dash
the single dash replacement causes conflicts
We could add the option to the tab "Localized options" ??
A tab for localized options could be good. But what this bug is about is not a localized option but an erratic option that serves no purpose and simply should be removed.
I agree with previous comment.
it would be easier to remove that "hyphen" to "en-dash" autocorrect entry from the dutch and belgian autocorrect lists rather than implementing a new localized options.
CC'ing Sophie Gautier
would you please tell us who's the localization maintainer of the nl-NL and nl-BE locales?
as said in previous comments this bug would be easily fixed by just removing the "hyphen" to "en-dash" autocorrect entry from the dutch and belgian default autocorrect lists which are still shipped into LibO (tested with LibO 5.1 alpha too)
** 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 on a currently supported version of LibreOffice
(5.1.5 or 5.2.1 https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the version of LibreOffice and
your operating system, and any changes you see in the bug behavior
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave
a short comment that includes your version of LibreOffice and Operating System
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)
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: http://webchat.freenode.net/?channels=libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
fixed as side effect of the committ that solved Bug 83037
thanks again Caolan, your patch fixed 3 bugs at a time (Bug 55292 too).
backport to 5.2.x would be appreciated.