Posting to your blog – A tip.

I am totally going to do this right now in order to claim the movie rights.

@userx, if a commentor writes/cuts/pastes from MS Word; then you’ll have the same issues. Word likes to convert double hyphens, apostrophes and quotation marks (possibly others as well) into Micro$quish’s “pretty format” which changes the encoding on those characters and hence they don’t display correctly once they’ve been posted.

It sounds like we are talking apples and oranges.

If the person is using Word or any other word processor to create code, then they are in for some problems without serious customizing their word processor (see below). And NEVER use Word’s (et al) save as or export as a web page and put that code anywhere, especially in a web page of any kind, without major cleaning and rennovation. It’s horrid.

But simply writing the post and then copying and pasting it into the Write screen, if done right, why not? After all, WordPress does not include spell check, though I’ve heard there is now a spell check plugin but it doesn’t work for everyone, and spelling is one of my biggest whines about blogs, and web pages in general.

For those, like me, who write their long posts in a word processor, and you have a word processor, like WordPerfect, that allows you to customize the snot out of it, you can do this.

Turn off all quick correct spelling fixers and changers that will influence your code. In WordPerfect, this is found under Tools > Quick Correct and Quick Words. In Word, Tools > Auto Correct Options. Specific items to turn off:

* Turn off Auto hyperlinks

* Stylized normal open and closing quotes to generic quotes (stylized means the ones with curlies opening and closing around the quoted material – you want the straight up and down ones)

* Stylized single quotes changed to straight apostrophees

* Hypen codes to plain dash (Control+hypen creates it for me)

When writing the post, make sure there is a space (line break or hard return) between paragraphs if you like that kind of spacing, avoid use of tabs, and make sure your html code within your post is clean, well-written, and contains no curly quotes.

I’ve been doing this for years so I can ensure my articles and posts are spell checked and, if necessary, grammatikally purfect, and then pasting them into the html page or post. But you got to make sure you fix the boogers first.

I <3 WP editor 🙂

While I understand the basis of this post…I’ve had errors occur during posting when I’ve typed my post right in the admin panel, which I find terribly ironic.

Word?

It’s already been said, but I also stick my hand up in class and say “No miss”.

The closest I would allow Word (or any other editor that was not straight/plain text) would be as a pre-amble to a plain text editor.

In other Words (marvellous pun eh?) if I were worried about smelling, becuase I knew I was likely to need some smelling support, for example when an artikle includes some complecs words that I am less familliar with, then yes, I might use Word for the first stage. But I would always paste into a plain text editor, then select-all-copy-paste from the plain text editor before I pasted into the post (which sounds like a rhyme: Peter pasted into the post {and picked a pepper?}).

Sorry if a little flippancy mixed in with my strong rejection of Word-to-WP posts annoys – please accept my apologies for flippancy low calorie humour .

Actually, Dear Moose man, I adored your wonderful monologue because it created a fabulous and much needed dialog.