Normalization

It must be an ellipsis character (OSX: ⌥;).
It must be surrounded by valid whitespace …
… except for a trailing ellipsis.

Valid whitespace is a normal space or a non-break-space (literal (OSX: ⌥space) or via [output,nbsp]).

The only exception is that the initial space has to be a normal space (non-break-space there would imply formatting or partial phrase, ick).

Rationale

We want to be simple, consistent, and clear.

CLDR has 3 simple location based rules:
```
  initial:…{0}
  medial:{0}…{1}
  final:{0}…
```
Yet, English provides many more rules based on location in the text, purpose (show an omission, indicate a trailing off for various purposes), context (puntuation before or after?), and author’s whim.

Some are exact opposites and yet still valid either way.

So lets keep it simple.
We are unlikely to be omitting things from a quote:
```
   The server said, “PHP […] is like training wheels without the bike.”.
```
Can be added later if necessary.
We are unlikely to be implying a continuing thought:
```
   What can you do, you know how he is ….
```
Even if we were this form is still valid. So lets keep it consistent.
We are not writing literature.

So lets keep it simple.
The CLDR version leaves room for ambiguity:
```
   I drove the car…
```
Is that the first part of “I drove the car to the store.” or “I drove the carpet home and installed it.”?

So lets keep it clear.

Tip: If you’re doing a single word(e.g. to indicate an action is happening) you might consider doing a non-break-space to the left of it:

    'Loading …' # i.e. Loading(OSX: ⌥-space)…

    'Loading[output,nbsp]…' # visually explicit

possible violations

None

possible warnings

multiple period/comma instead of ellipsis character

We want an ellipsis character instead of 3 periods (or 2 periods, 4 or 5 periods, or commas (yes I’ve seen translators do ‘..’, ‘,,,,’, etc and after inquiring ‘…’ was the correct syntax)).

These will be turned into an ellipsis character.

initial ellipsis should be preceded by a normal space