Ellipses instead of ... in UI

[janeforshort]

In places where we use [...] to indicate that there's more content, we should use ellipses instead of three periods.

grepped for "..." and replaced what I found being outputted with "…"

Line 47 of formatting.php should not change. Some occurrences of ... should be replaced with a period. The ones in wp-login.php, for example. Some error message need to be reworded. "Error in deleting..." for one.

Also, there seems to be a preference for numbered rather than named entities, so ... should probably be replaced with …

bumping to 2.9, since patch needs to be refreshed

Similar patch as before, uses numeric entities, ellipses are removed from certain phrases where they shouldn't exist and the 3 periods are left unchanged on line 47 of formatting.php.

Possible for 3.1?

Is the latest patch good to go? It's embarrassing that this little thing still hasn't been fixed. I didn't mention it in the original ticket, but this flaw was called out by Chris Messina when he was a participant in 2.7 testing.

Ellipses should either be part of a translated string (as many are here), or if used as part of text, should be __( '…' ) for translators. (We currently do '…' for translators, but we can standardize either way.)

Agreed, best to be either one or the other. Also worth mentioning that we shouldn't use HTML entities in JS strings like the translated strings in script-loader.

Semi-Related #7098 (attachment:ticket:7098:8230-to-hellip.patch​)

Working on a refresh.

Mostly standardizes …, some whitespacing in affected blocks

After ​some discussion in IRC, settled on … over … and '...' as it was already pretty widely used in Core. Refreshed patch attached.

Looks good. We need to audit these though, for context (making sure they aren't escaped, for example).

Should probably avoid changing 8230 to hellip if only to not break all of those strings.

Replying to nacin:

Should probably avoid changing 8230 to hellip if only to not break all of those strings.

Nacin, this ticket was created 3 years ago. I think that if we already addressing the issue, we should fix the 8230 as well.

Patch is stale. Can someone refresh it?

Excluded changes to &#8230

Excluded pluggable.php

Breaking strings in an update is to be expected when the fix is text related. Since this just got punted again, when it goes in eventually, let's not not water it down.

Fixed a couple of misses in class-wp-xmlrpc-server.php and formatting.php

Closed #17608 as a duplicate.

Related: #7098, #9030, #13341, #14225

Skipped the changes in wp-admin/network.php, didn't look good in the <code> tag.

wp-includes/deprecated.php should probably also be skipped.

Agree on skipping wp-includes/deprecated.php.

The ones at the ends of error messages should probably change to single periods (as Ryan noted up at comment 3).

Lastly don't we need to avoid using named entities in an XML context?

Agreed with no ellipses at the end of error messages.

Don't agree on skipping wp-includes/deprecated.php.

Skipping depricated strings will only make more simmilar strings and make the transtation file larger.

(Related: #18218, #14039, #7098 and many more)

Replying to markjaquith:

Lastly don't we need to avoid using named entities in an XML context?

For ​polyglot markup, yes, and note the W3C Recommendation that ​numbered entities SHOULD use the hexadecimal form when it exists.

Replying to ramiy:

Skipping depricated strings will only make more simmilar strings and make the transtation file larger.

The strings in question are not translatable, see lines 1707 and 1734:
http://core.trac.wordpress.org/browser/tags/3.5.1/wp-includes/deprecated.php#L1707

8714.7.diff​ miraculously still applies cleanly. Seems like the consensus is that this should happen early in a cycle so maybe punt (again) to 3.7 early?

It is downright embarrassing that something like this should take us ten versions to do. Chris Messina has mocking rights on me/us for the rest of eternity; I told him back in 2008 that we'd get this fixed before we launched 2.7 (he discovered it during usability testing before beta).

Replying to jenmylo:

It is downright embarrassing that something like this should take us ten versions to do.

*Rubs Eyes*...

*Chokes*...

[Caugh! Caugh!]

*Pinches himself... Looks around...*

Did you actually write that, Jane? :-D

Moving back to 3.6 per the ​IRC chat.

Refreshed in 8714.8.diff​:

1. Skipped deprecated.php and "Hello World" post content.
2. Changed the instances in error messages to single periods, per comment:27.
3. Used numeric entities in XML content, also per comment:27.

In 24207:

Use ellipsis instead of three dots. props tjsingleton, jordie23, wojtek.szkutnik, DrewAPicture, SergeyBiryukov. see #8714.