At it's core, blogging is an exercise in writing.  Newcomers to the activity are frequently inclined to do that writing using an application that is most familiar and then pasting the result into the blog authoring software. 

My development activities frequently involve working with user generated content, and judging from my observations, there is a substantial portion of the user community that is using a word processor create posts.

Although a fairly straightforward operation, using a rich text word processor like Microsoft Word is not something that I would recommend as a blogging best practice.  Here are some of the reasons:
  1. Lost in the Translation: Rich text created with a word processor doesn't always translate cleanly into HTML.  Between your word processor and the web broswer lies the system clipboard, and the interaction with that clipboard depends on the applications involved.  Things like spatial formatting might get butchered along the way.
  2. Character Assassination: Some word processors have auto-replace features that convert your keystrokes into completely different characters.  The most common of these is Microsoft Word's Smart Quote feature, which converts the standard double quotation mark into directional quotes.  Sometimes, these special characters rely on character encodings that are specific to the platform you composing on.  These characters may not display properly on all browsers.  At best, you reader might see question marks; at worst, your reader might see gibberish.
  3. Fugitive Fonts: Yes, I'm sure that post sure does look rather fetching when set in 12 point Exotica, but unless your reader has identical typographical tastes as you and has configured his or her computer in the same way, that font won't be seen.  A web browser usually only can render fonts that are installed on the system.  If the font isn't present, a browser will substitute a different font, and it might be rather ugly. 
  4. Call the Style Police: Even if the font is displayable by the browser, the font may not match the look of the blog's style sheet.  If every blogger in the organization is using a different font and size, the compended blogs tend to take a ramshackle appearance because the uniform look of the page's style sheet is routinely being overridden.
  5. Proprietary Pitfalls:  Sometimes a word processor will put HTML on the clipboard for a browser to accept, but the HTML isn't standards compliant.  It may have attributes that are vendor specific.  I've seen some very strange things, including HTML style attributes that had properties specific to Office and HTML tags that were prefixed with XML namespace identifiers.  Very few of these things wind up looking good in all browsers.
Taken together, these points make for a compelling case to use Compendium's built-in blog post software.  Our rich editor stores your content as HTML thereby maximizing the likelhood that what you enter is truly what you'll get.  Moreover, it already supports many of the styling features that are supported in HTML.  There's no worry that your formatting will be degraded.