StringMash.com

… is a broken ellipsis

Your text was saved as UTF-8 and read as Windows-1252. Paste it below and it's put right.

23 characters
Updates as you type

Correct text is left as it is

Show the steps
  1. Each garbled run was turned back into the bytes Windows-1252 showed, then read as UTF-8, as it should have been.
  2. … → … (U+2026): bytes E2 80 A6
Printable chart

What … means

… is a broken ellipsis (…): your text was saved as UTF-8 but read as Windows-1252. It's the ellipsis, …, a single character for three dots that many programs substitute when you type three full stops. In UTF-8 it's E2 80 A6, and Windows-1252 shows those bytes as â, € and ¦.

WHY IT HAPPENS

Byte by byte

… (U+2026) in UTF-8, and what Windows-1252 makes of each byte
ByteIn UTF-8Windows-1252 shows
E2lead byte: 3 bytes in allâ
80continuation byte€
A6continuation byte¦

Broken twice, or on a Mac

Other ways … gets garbled, and whether this page's fixer undoes them
What happenedWhat you seeFixed here?
Saved as UTF-8, read as Windows-1252 (this page)…Yes
The same mistake made twice…Yes
Saved as UTF-8, read as Mac OS Roman…No

Where you probably saw it

Interface text and messages such as "Loading…" or "Read more…".

Text typed on a phone or in a word processor, which often swaps three dots for the single ellipsis character.

Subject lines and previews in emails.

Related sequences

Text broken this way rarely has just one problem. — is a broken em dash, ’ is a broken apostrophe, “ is a broken opening quote. The mojibake fixer repairs all of them at once, and its table lists the rest.

Questions

What is …?

A broken ellipsis. The single ellipsis character … is E2 80 A6 in UTF-8, shown by Windows-1252 as â, € and ¦.

Should I use … or three dots?

Either is fine in most writing. Three full stops are plain ASCII, so they can never break this way.

Does the fixer change three dots into …?

No. Three full stops stay three full stops.

What does … mean?

It's the ellipsis broken twice. Text already showing … was saved as UTF-8 again and misread again, so each of those characters turned into two or three more. The fixer above repeats the repair until nothing is left to undo, so it fixes this too.

What about …?

That's the ellipsis read by older Mac software, which used the Mac OS Roman character set instead of Windows-1252. The same UTF-8 bytes come out as different characters. The fixer here only undoes the Windows-1252 mistake, so for this one open the file again as UTF-8, or retype the ellipsis.

Sources

Added . Last updated and reviewed . What's new