# Why do apostrophes so often get screwed up on the WWW?

**URL:** <https://boards.straightdope.com/t/why-do-apostrophes-so-often-get-screwed-up-on-the-www/372132>\
**Category:** Factual Questions\
**Created:** [September 10, 2006, 7:33am UTC](https://boards.straightdope.com/t/why-do-apostrophes-so-often-get-screwed-up-on-the-www/372132 "2006-09-10T07:33:18Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Baraqiyal](https://avatars.discourse-cdn.com/v4/letter/b/ecccb3/32.png) [@Baraqiyal](https://boards.straightdope.com/u/Baraqiyal)\
**Post date:** [September 10, 2006, 7:33am UTC](https://boards.straightdope.com/t/why-do-apostrophes-so-often-get-screwed-up-on-the-www/372132/1 "2006-09-10T07:33:18Z")

</div>

I’ve noticed this phenomenon for many years. Apostrophes get replaced with a string of random characters, and it seems to be a completely different set of weird characters every time. What causes this, and how has this problem not been fixed? (I’m seen it with even more frequency in recent months). I also have to wonder how it’s not caught before it’s published.

Here are a few examples: [Here](http://www.archive.org/details/ThePowerOfNightmares), [here](http://www.boston.com/yourlife/health/other/articles/2006/08/31/in_uruguay_the_president_also_reads_mammograms/), [here](http://www.digg.com/tech_news/Google_Partners_with_XM_Satellite_Radio_2).

---

<div class="post-metadata">

**Author:** ![naita](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/naita/32/5862_2.png) [@naita](https://boards.straightdope.com/u/naita)\
**Post date:** [September 10, 2006, 9:35am UTC](https://boards.straightdope.com/t/why-do-apostrophes-so-often-get-screwed-up-on-the-www/372132/2 "2006-09-10T09:35:02Z")

</div>

> [@Baraqiyal](#):
>
> I’ve noticed this phenomenon for many years. Apostrophes get replaced with a string of random characters, and it seems to be a completely different set of weird characters every time. What causes this, and how has this problem not been fixed? (I’m seen it with even more frequency in recent months). I also have to wonder how it’s not caught before it’s published.
> 
> Here are a few examples: [Here](http://www.archive.org/details/ThePowerOfNightmares), [here](http://www.boston.com/yourlife/health/other/articles/2006/08/31/in_uruguay_the_president_also_reads_mammograms/), [here](http://www.digg.com/tech_news/Google_Partners_with_XM_Satellite_Radio_2).

Encoding. It looks good on whatever tool you’re using, and possibly even in your browser when you view it locally, but turns into junk when viewed in whatever encoding the actual web-site tells the browser to use. It can also actually have been turned into junk by having steps from your editing to the finished file that can’t handle the original encoding.

---

<div class="post-metadata">

**Author:** ![Lobelia\_Overhill](https://avatars.discourse-cdn.com/v4/letter/l/54ee81/32.png) [@Lobelia\_Overhill](https://boards.straightdope.com/u/Lobelia_Overhill)\
**Post date:** [September 10, 2006, 10:56am UTC](https://boards.straightdope.com/t/why-do-apostrophes-so-often-get-screwed-up-on-the-www/372132/3 "2006-09-10T10:56:24Z")

</div>

you can press alt and 0145 on your numeric keypad to get a ‘ which looks like an apostrophe and doesn’t cause those problems…

---

<div class="post-metadata">

**Author:** ![Johanna](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/johanna/32/8318_2.png) [@Johanna](https://boards.straightdope.com/u/Johanna)\
**Post date:** [September 10, 2006, 11:12am UTC](https://boards.straightdope.com/t/why-do-apostrophes-so-often-get-screwed-up-on-the-www/372132/4 "2006-09-10T11:12:39Z")

</div>

There was a thread with detailed techie information on this question a couple years ago.

> **[Quote mark coding - why quote marks are changed into different characters](https://boards.straightdope.com/sdmb/showthread.php?t=266210)**
>
> You see this a lot on the internet, in E-mail and news stories, etc. Double quote marks aren’t always displayed right when text is reproduced on a different application from the one it was created on. Sometimes the quote marks are changed into...

---

<div class="post-metadata">

**Author:** ![Sublight](https://avatars.discourse-cdn.com/v4/letter/s/439d5e/32.png) [@Sublight](https://boards.straightdope.com/u/Sublight)\
**Post date:** [September 10, 2006, 11:46am UTC](https://boards.straightdope.com/t/why-do-apostrophes-so-often-get-screwed-up-on-the-www/372132/5 "2006-09-10T11:46:20Z")

</div>

The same encoding problems crop up when you go between applications, operating systems or character sets of different langauges sometimes. Whenever we take text written on a PC in English Microsoft Word and drop it into a layout designed on a Mac in Japanese Illustrator, charaters like smart quotes, bullet points and long dashes often come out mis-coded.

---

<div class="post-metadata">

**Author:** ![Napier](https://avatars.discourse-cdn.com/v4/letter/n/ce73a5/32.png) [@Napier](https://boards.straightdope.com/u/Napier)\
**Post date:** [September 10, 2006, 1:26pm UTC](https://boards.straightdope.com/t/why-do-apostrophes-so-often-get-screwed-up-on-the-www/372132/6 "2006-09-10T13:26:35Z")

</div>

I think what motivates these problems is that some software tries to use only a basic character set, more specifically the ASCII characters represented by the binary 0000000 to 1111111 (7 bits), and some other software tries to use fancier characters with longer representations. The ASCII character set includes a singlequote and a doublequote, and these are the same whether it’s the beginning or the end of the quoted phrase. Some software tries to figure out which end of the quoted phrase each of these is on and substitute different singlequotes or doublequotes accordingly.

This is also weird if you deal with programming text or work with the customary symbols for feet and inches, because in this context they aren’t for quoting and the distinction between starting and stopping a quotation doesn’t apply.

---

<div class="post-metadata">

**Author:** ![AHunter3](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/ahunter3/32/368_2.png) [@AHunter3](https://boards.straightdope.com/u/AHunter3)\
**Post date:** [September 10, 2006, 3:49pm UTC](https://boards.straightdope.com/t/why-do-apostrophes-so-often-get-screwed-up-on-the-www/372132/7 "2006-09-10T15:49:12Z")

</div>

Blame it on Microsoft Word. People copy from Word and paste into web browser form. Word doesn’t play nicely with much of anyththing (other applications, other versions of itself, its own users, etc) and wreaks havoc with upper-ASCII characters.

OK, in all fairness to MS, it appears that they are finally going to support open standards for file format in upcoming versions of Word. Be nice if it’s true. Overdue but nice. Let’s hope they mean the open standard file format will be the default format for saving Word files and not just an obscure “Save As” option.

---

<div class="post-metadata">

**Author:** ![Duckster](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/duckster/32/1244_2.png) [@Duckster](https://boards.straightdope.com/u/Duckster)\
**Post date:** [September 10, 2006, 5:09pm UTC](https://boards.straightdope.com/t/why-do-apostrophes-so-often-get-screwed-up-on-the-www/372132/8 "2006-09-10T17:09:07Z")

</div>

> [@Baraqiyal](#):
>
> Here are a few examples: [Here](http://www.archive.org/details/ThePowerOfNightmares), [here](http://www.boston.com/yourlife/health/other/articles/2006/08/31/in_uruguay_the_president_also_reads_mammograms/), [here](http://www.digg.com/tech_news/Google_Partners_with_XM_Satellite_Radio_2).

The first example has no required [doctype](http://alistapart.com/stories/doctype/) so the browser flounders attempting to render the page. More importantly, the actual code is poorly written contributing to the morass.

The second one is a coding error, either with the CMS used or human error.

The third appears to bre human error caused by the contributor.

In all of the above the pre- and post-quality checks appear to be missing.

---

<div class="post-metadata">

**Author:** ![Chronos](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/chronos/32/134_2.png) [@Chronos](https://boards.straightdope.com/u/Chronos)\
**Post date:** [September 10, 2006, 6:30pm UTC](https://boards.straightdope.com/t/why-do-apostrophes-so-often-get-screwed-up-on-the-www/372132/9 "2006-09-10T18:30:29Z")

</div>

For the specific problem of an apostrophe being replaced by something random, I think the other posters have it. You can also end up with text missing, though, since the coding for some software assumes that an apostrophe is a single-quote, and may treat text in single-quotes in some special manner. Likewise for double-quotes. For instance, a few versions ago, vBulletin couldn’t handle double-quotes in thread titles. The thread title was stored in double-quotes in the database, and if there was a " somewhere in the title, it would assume that meant that was the end of the title. So, for instance, if I posted a thread asking

Why is " the symbol for inches?

The database would contain

“Why is " the symbol for inches?”

and when the rendering software would try to render that, it would think that the title ended at the second ", and you’d see

Why is

as the title of the thread. Similar things can happen with apostrophes, if that’s what the software is using.

---

<div class="post-metadata">

**Author:** ![naita](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/naita/32/5862_2.png) [@naita](https://boards.straightdope.com/u/naita)\
**Post date:** [September 10, 2006, 8:10pm UTC](https://boards.straightdope.com/t/why-do-apostrophes-so-often-get-screwed-up-on-the-www/372132/10 "2006-09-10T20:10:13Z")

</div>

To follow up on that tangent… I once submitted a joke poem to a poetry contest at [poetry.com](http://poetry.com) (yeah, the scammers) with the title \<no title\> . It was accepted into the database, but broke [poetry.com](http://poetry.com)’s index.

---

<div class="post-metadata">

**Author:** ![elmwood](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/elmwood/32/3060_2.png) [@elmwood](https://boards.straightdope.com/u/elmwood)\
**Post date:** [September 12, 2006, 2:21pm UTC](https://boards.straightdope.com/t/why-do-apostrophes-so-often-get-screwed-up-on-the-www/372132/11 "2006-09-12T14:21:12Z")

</div>

One thing I’ve noticed on the Internet ,is that on many message boards and blogs ,and occasionally email ,people often leave a space _before_ a comma ,not after. I’ve never encountered it in handwriting ,typed and printed correspondence ,or any other media. Why is this practice so prevalent online?
