title: Making Microsoft Word behave (for sysadmins) link: https://onemoretech.wordpress.com/2009/06/17/making-microsoft-word-behave-for-sysadmins/ author: lembobro description: post_id: 310 created: 2009/06/17 14:11:36 created_gmt: 2009/06/17 14:11:36 comment_status: open post_name: making-microsoft-word-behave-for-sysadmins status: publish post_type: post

Making Microsoft Word behave (for sysadmins)

One of the annoying facts of life is that non-technical people, and some technical ones, have this love affair with Microsoft Word. And Excel. And PowerPoint.

Despite evidence that MS Office can kill, those of us more accustomed to the rock solid stable and infinitely customizable vi editor, still have to generate some documentation in Microsoft Word for others.

I’m not going to digress into my decades long war with Word’s spell and grammar checkers. You don’t need seven years of postgraduate study and over two decades of professional writing experience to know that they’re completely and utterly inadequate (and sometimes outright wrong).

No, in this post I’m going to focus on a single issue that is a constant thorn in the side of anyone who has ever had to copy and past code snippets or format log output into a Word document.

Initial caps. Or, as Microsoft terms it: “Correct TWo INitial CApitals” and “Capitalize first letter of _s_entences”.

Oh yeah. “TWo INitial…”. Very cute. What are we, in high school?

To fix this all you have to do is go into Word and click Tools… AutoCorrect Options. Then just clear the checkbox for these two demonic “features”.

That’s it. End of story.

Copyright 2004-2019 Phil Lembo