[en] Suggest replacing "..." with "…" (symbol)

Development
1

Hello!

A few months ago, Tiago Santos implemented the subject rule into Portuguese.

Could someone do it too for English since it is very important?

Thanks!

2

@Mike_Unwalla @Yakov

Could someone insert this rule into English?:

   <rule id="ELLIPSIS" name="Smart ellipses (…)">
	<!-- Rule by Tiago F. Santos -->
	<!-- Localised to English by Marco A.G.Pinto, 2017-05-22 -->
      <pattern>
          <token>.</token>
          <token>.</token>
          <token>.</token>
      </pattern>
      <message>Use the typeface ellipsis instead of: <suggestion>…</suggestion>.</message>
      <example correction="…">This is important <marker>. . .</marker> as far as I know.</example>
      <example>This is important – as far as I know.</example>
      <example correction="…">This is important<marker>...</marker> as far as I know.</example>
    </rule>

Thanks!

3

@marcoagpinto
Thank you for valuing this rule and taking your time to localize it.
I haven’t looked at it for a long time, and I would only prefer that it would be used with less false positives in enumerations. A simple solution can be with an antipattern.

   <rule id="ELLIPSIS" name="Smart ellipses (…)">
	<!-- Rule by Tiago F. Santos -->
	<!-- Localised to English by Marco A.G.Pinto, 2017-05-22 -->
    </rule>
      <antipattern>
          <token>.</token>
          <token>.</token>
          <token>.</token>
          <token>.</token>
          <token>.</token>
      </antipattern>
      <pattern>
          <token>.</token>
          <token>.</token>
          <token>.</token>
      </pattern>
      <message>Use the typeface ellipsis instead of: <suggestion>…</suggestion>.</message>
      <example correction="…">This is important <marker>. . .</marker> as far as I know.</example>
      <example>This is important – as far as I know.</example>
      <example correction="…">This is important<marker>...</marker> as far as I know.</example>
      <example>1. Introduction .................................... 3</example>
    </rule>
4

Rule id=“ELLIPSIS” is already in English.

I added the antipattern ([en] Improve ELLIPSIS · languagetool-org/languagetool@e712bee · GitHub).

5

When was it added?

I have tried:
"This is a test … " and I got no suggestion from LanguageTool.
LanguageTool-20170519-snapshot.oxt

6

I’ve taken a quick look. You need to explicitly enable it.

7

can’[quote=“SkyCharger001, post:6, topic:1676, full:true”]
I’ve taken a quick look. You need to explicitly enable it.
[/quote]

Can’t it be on by default since it is an important rule?

8

@marcoagpinto @Mike_Unwalla
All rules from line
14775
to
15045

were localized and tweaked from English. I will add individual rule comments, in the coming days.
The things are becoming big, and I no longer remember everything.

9

Depends on how faulty the implementation is.
For example, it could mistake the enter-three-digit-value/ID-here for an ellipsis and screw up the inventory template. (three separate dots= three spots for one digit each, ellipsis = can you write microscopic digits?)

on the side: I’ve already have ellipsis set up as an autoCorrect in OpenOffice, which makes it (for me, at least) easier to avoid improper use of it

10

I am not sure I understand the logic.
You mean that it is preferable to replace automatically, then to activate a rule requiring you to explicitly tell you want those changes?

How many more false positives would that create in comparison with other, already active, rules?

11

Tiago is right.

12

A. Neither the regular spellchecker or LT allows you to choose ignore-specific-case-always, leading (for me) to too many false positives that distract from the real issues.
The autoCorrect of OpenOffice (in the typing-only mode I use it) requires that the character-string associated with ELLIPSIS is typed separately from anything else. (means I have to manually remove the ‘leading’ space afterwards, but that is a price I’m willing to pay),
B. Is merely a theoretical example.

13 
<antipattern>
<token>:</token>
<token>.</token>
<token>.</token>
<token>.</token>
</antipattern>

Try this.