.\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28)
.\"
.\" Standard preamble:
.\" ========================================================================
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
..
.de Vb \" Begin verbatim text
.ft CW
.nf
.ne \\$1
..
.de Ve \" End verbatim text
.ft R
.fi
..
.\" Set up some character translations and predefined strings.  \*(-- will
.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
.\" double quote, and \*(R" will give a right double quote.  \*(C+ will
.\" give a nicer C++.  Capital omega is used to do unbreakable dashes and
.\" therefore won't be available.  \*(C` and \*(C' expand to `' in nroff,
.\" nothing in troff, for use with C<>.
.tr \(*W-
.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
.ie n \{\
.    ds -- \(*W-
.    ds PI pi
.    if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
.    if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\"  diablo 12 pitch
.    ds L" ""
.    ds R" ""
.    ds C` ""
.    ds C' ""
'br\}
.el\{\
.    ds -- \|\(em\|
.    ds PI \(*p
.    ds L" ``
.    ds R" ''
.    ds C`
.    ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
.\" entries marked with X<> in POD.  Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.\"
.\" Avoid warning from groff about undefined register 'F'.
.de IX
..
.nr rF 0
.if \n(.g .if rF .nr rF 1
.if (\n(rF:(\n(.g==0)) \{
.    if \nF \{
.        de IX
.        tm Index:\\$1\t\\n%\t"\\$2"
..
.        if !\nF==2 \{
.            nr % 0
.            nr F 2
.        \}
.    \}
.\}
.rr rF
.\" ========================================================================
.\"
.IX Title "Locale::Maketext::Utils::Phrase::Norm::Ellipsis 3"
.TH Locale::Maketext::Utils::Phrase::Norm::Ellipsis 3 "2014-11-18" "perl v5.16.3" "User Contributed Perl Documentation"
.\" For nroff, turn off justification.  Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.nh
.SH "Normalization"
.IX Header "Normalization"
.IP "\(bu" 4
It must be an ellipsis character (\s-1OSX:\s0 ⌥;).
.IP "\(bu" 4
It must be surrounded by valid whitespace …
.IP "\(bu" 4
… except for a trailing ellipsis.
.PP
Valid whitespace is a normal space or a non-break-space (literal (\s-1OSX:\s0 ⌥space) or via [output,nbsp]).
.PP
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).
.SS "Rationale"
.IX Subsection "Rationale"
We want to be simple, consistent, and clear.
.IP "\(bu" 4
\&\s-1CLDR\s0 has 3 simple location based rules:
.Sp
.Vb 3
\&  initial:…{0}
\&  medial:{0}…{1}
\&  final:{0}…
.Ve
.Sp
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.
.Sp
Some are exact opposites and yet still valid either way.
.Sp
So lets keep it simple.
.IP "\(bu" 4
We are unlikely to be omitting things from a quote:
.Sp
.Vb 1
\&   The server said, “PHP […] is like training wheels without the bike.”.
.Ve
.Sp
Can be added later if necessary.
.IP "\(bu" 4
We are unlikely to be implying a continuing thought:
.Sp
.Vb 1
\&   What can you do, you know how he is ….
.Ve
.Sp
Even if we were this form is still valid. So lets keep it consistent.
.IP "\(bu" 4
We are not writing literature.
.Sp
So lets keep it simple.
.IP "\(bu" 4
The \s-1CLDR\s0 version leaves room for ambiguity:
.Sp
.Vb 1
\&   I drove the car…
.Ve
.Sp
Is that the first part of “I drove the car to the store.” or “I drove the carpet home and installed it.”?
.Sp
So lets keep it clear.
.PP
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:
.PP
.Vb 1
\&    \*(AqLoading …\*(Aq # i.e. Loading(OSX: ⌥\-space)…
\&
\&    \*(AqLoading[output,nbsp]…\*(Aq # visually explicit
.Ve
.SH "possible violations"
.IX Header "possible violations"
None
.SH "possible warnings"
.IX Header "possible warnings"
.IP "multiple period/comma instead of ellipsis character" 4
.IX Item "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)).
.Sp
These will be turned into an ellipsis character.
.IP "initial ellipsis should be preceded by a normal space" 4
.IX Item "initial ellipsis should be preceded by a normal space"
The string is modified with a corrected version.
.IP "initial ellipsis should be followed by a normal space or a non-break-space (in bracket notation or character form)" 4
.IX Item "initial ellipsis should be followed by a normal space or a non-break-space (in bracket notation or character form)"
The string is modified with a corrected version.
.IP "final ellipsis should be preceded by a normal space or a non-break-space (in bracket notation or character form)" 4
.IX Item "final ellipsis should be preceded by a normal space or a non-break-space (in bracket notation or character form)"
The string is modified with a corrected version.
.IP "final ellipsis should be followed by a valid punctuation mark or nothing" 4
.IX Item "final ellipsis should be followed by a valid punctuation mark or nothing"
The string is modified with a corrected version.
.IP "medial ellipsis should be surrounded on each side by a parenthesis or normal space or a non-break-space (in bracket notation or character form)" 4
.IX Item "medial ellipsis should be surrounded on each side by a parenthesis or normal space or a non-break-space (in bracket notation or character form)"
The string is modified with a corrected version.