The Problem (Q-score 5, ranked #22nd of 32 in the Word VBA archive)
The scenario as originally posted in 2009
I’m wondering how you clean the special characters that MS Word as, such as m- and n-dashes and curly quotes?
I often find myself copying content from clients from Word and pasting into a static HTML page, but the content ends up with weird characters because the special characters are not converted to their correct ACSII codes and therefore show up as garbled text. (For these basic websites, I’m using Dreamweaver.)
I have seen a lot of similar problems when clients copy content from Word into text only fields (mostly textareas). When I put this into a PDF (through PHP) or it shows up on the page it too has garbled text.
How do you deal with this? Is there a cleaning service or program you use?
Why community consensus is tight on this one
Across 32 Word VBA entries in the archive, the accepted answer here holds solid answer (above median) status — meaning voters are unusually aligned on the right fix.
The Verified Solution — solid answer (above median) (+7)
4-line Word VBA pattern (copy-ready)
With regards to clients posting copy/pasted text from Word in textareas:
The most reliable way to ensure that the client sends you text in any particular encoding (thus hopefully doing any conversion from CP-1252 [or whatever Word uses] for you), is to add the accept-charset="..." attribute to all your <form>s. E.g.:
<form ... accept-charset="UTF-8">
...
</form>
Most browsers will obey that and make sure any “Word-specific” characters are converted to the appropriate character set before it gets to your website.
Once invalid text gets to your website, there’s very little you can do to fix it reliably, so it’s best to simply check all input for being valid in whatever character set you use, and discard any requests that have invalid text. This is necessary even with accept-charset, because undoubtedly there are some clients out there that will ignore it.
When to Use It — vintage (14+ years old, pre-2013)
Ranked #22nd in its category — specialized fit
This pattern sits in the 63% tail relative to the top answer. Reach for it when your scenario closely matches the question title; otherwise browse the Word VBA archive for a higher-consensus alternative.
What changed between 2009 and 2026
The answer is 17 years old. The Word VBA object model has been stable across Office 2013, 2016, 2019, 2021, 365, and 2024/2026 LTSC, so the pattern still compiles. Changes that might affect you: 64-bit API declarations (use PtrSafe), blocked macros in downloaded files (Mark-of-the-Web), and the shift toward Office Scripts for web-first workflows.