<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>

<channel>
	<title>Precision Wordage</title>
	<atom:link href="http://www.precisionwordage.com/index.php/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.precisionwordage.com</link>
	<description>The Precision Wordage blog</description>
	<pubDate>Fri, 15 Jan 2010 16:05:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
	<language>en</language>
			<item>
		<title>Technical writing and the economy</title>
		<link>http://www.precisionwordage.com/articles/technical-writing-and-the-economy/</link>
		<comments>http://www.precisionwordage.com/articles/technical-writing-and-the-economy/#comments</comments>
		<pubDate>Fri, 22 Aug 2008 03:15:38 +0000</pubDate>
		<dc:creator>post</dc:creator>
		
		<category><![CDATA[Documentation]]></category>

		<category><![CDATA[Localization]]></category>

		<category><![CDATA[budget sensitive]]></category>

		<category><![CDATA[cut costs]]></category>

		<category><![CDATA[outsourcing]]></category>

		<category><![CDATA[precision wordage]]></category>

		<category><![CDATA[recession]]></category>

		<category><![CDATA[technical publications]]></category>

		<category><![CDATA[technical writers]]></category>

		<category><![CDATA[technical writing]]></category>

		<guid isPermaLink="false">http://www.precisionwordage.com/?p=60</guid>
		<description><![CDATA[The recession isn&#8217;t coming; it&#8217;s arrived. Companies are getting more and more budget sensitive, and looking for ways to cut costs. This is impinging on the field of technical documentation. I know of at least one major electronics company that asked its technical writers to take a pay cut. The writer I know there took [...]]]></description>
			<content:encoded><![CDATA[<p>The recession isn&#8217;t coming; it&#8217;s arrived. Companies are getting more and more budget sensitive, and looking for ways to cut costs. This is impinging on the field of technical documentation. I know of at least one major electronics company that asked its technical writers to take a pay cut. The writer I know there took it gladly, happy to have not been laid off completely like some of his co-workers.</p>
<p>But technical publications still need to be produced. As long as products are going to market, the technical documentation has to be there on how to use them.</p>
<p>Some companies are turning to off-shoring, but, in the words of one former client who was forced by upper echelons to go that route, &#8220;It&#8217;s a challenge since English is not the first language of the writers&#8230; things &#8230; need to be sacrificed along the way.&#8221;</p>
<p>Is there another solution? You betcha.</p>
<p><em>On-shore</em> outsourcing.</p>
<p>At Precision Wordage, we&#8217;ve been taking only outsource projects now for about 15 years. The projects we work on minimize client costs because the client pays only for the actual writing project (and gets a high quality product in the process). No overhead, no paid vacations, no severance packages when the project is over.</p>
<p>If your company is looking for ways to cut costs, consider using an outsource company. Crunch the numbers and you&#8217;ll discover that technical writing from an outsource vendor will deliver the most bang for the buck, especially if you can negotiate a flat bid or not-to-exceed deal.</p>
<p>And if the writer is American, chances are the technical communication <em>will </em>actually communicate.</p>
<p>- Su</p>
]]></content:encoded>
			<wfw:commentRss>http://www.precisionwordage.com/articles/technical-writing-and-the-economy/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Your manual seem not understand?</title>
		<link>http://www.precisionwordage.com/articles/engrish/</link>
		<comments>http://www.precisionwordage.com/articles/engrish/#comments</comments>
		<pubDate>Fri, 08 Feb 2008 04:58:46 +0000</pubDate>
		<dc:creator>post</dc:creator>
		
		<category><![CDATA[Documentation]]></category>

		<category><![CDATA[Localization]]></category>

		<category><![CDATA[Proofing]]></category>

		<category><![CDATA[document]]></category>

		<category><![CDATA[manual]]></category>

		<category><![CDATA[precision wordage]]></category>

		<category><![CDATA[tech writers]]></category>

		<category><![CDATA[translation]]></category>

		<guid isPermaLink="false">http://www.precisionwordage.com/index.php/articles/your-manual-seem-not-understand/</guid>
		<description><![CDATA[Have you ever opened a manual and wondered what planet the writers lived on? It probably wasn&#8217;t localized.
Localization means adaptation of the language in a document or software to a new culture or region. This could be as simple as changing the spelling from British English to American English (for example, &#8220;colour&#8221; to &#8220;color&#8221;) or [...]]]></description>
			<content:encoded><![CDATA[<p>Have you ever opened a manual and wondered what planet the writers lived on? It probably wasn&#8217;t localized.</p>
<p><em>Localization</em> means adaptation of the language in a document or software to a new culture or region. This could be as simple as changing the spelling from British English to American English (for example, &#8220;colour&#8221; to &#8220;color&#8221;) or it could be much more complex.</p>
<p>Sometimes, when manuals are written in foreign languages (particularly East Asian languages) and translated to English, things are somewhat less than intelligible. And hijinks ensue. We writers affectionately refer to such abominations as &#8220;Engrish&#8221; or perhaps &#8220;Chinglish&#8221; in the case of a certain well-known language.</p>
<p>The problem arises when the translation is done by machine &#8220;translators&#8221; (which are mostly little more than word substituters) or persons who are barely literate in English. Underneath that, the quality of the original manual in the foreign language may not have been particularly good. The result is often a very confusing (and sometimes highly amusing) set of instructions.</p>
<p>&#8220;The luxuring wireless remote controlling stretches out and draws back the door&#8221; (translation: &#8220;Deluxe Wireless Remote Controlled Retractable Gate&#8221;) may be hilarious, but it doesn&#8217;t exactly put across the right concept.</p>
<p>But what does one do about it?</p>
<p>That&#8217;s where competent tech writers come in. We can take the most garbled manual and turn it into a sparkling jewel of clarity and usefulness. A good tech writer has a &#8220;knack&#8221; for deciphering what the original-language writer was trying to say, however goofy the translation, and re-expressing it in English that <em>can</em> be understood.</p>
<p>- David</p>
]]></content:encoded>
			<wfw:commentRss>http://www.precisionwordage.com/articles/engrish/feed/</wfw:commentRss>
		</item>
		<item>
		<title>How does a technological society survive?</title>
		<link>http://www.precisionwordage.com/articles/how-does-a-technological-society-survive/</link>
		<comments>http://www.precisionwordage.com/articles/how-does-a-technological-society-survive/#comments</comments>
		<pubDate>Tue, 08 Jan 2008 05:08:41 +0000</pubDate>
		<dc:creator>post</dc:creator>
		
		<category><![CDATA[Documentation]]></category>

		<category><![CDATA[instruction]]></category>

		<category><![CDATA[precision wordage]]></category>

		<category><![CDATA[procedures]]></category>

		<category><![CDATA[reduces support]]></category>

		<category><![CDATA[technologies]]></category>

		<category><![CDATA[technology]]></category>

		<category><![CDATA[written information]]></category>

		<guid isPermaLink="false">http://www.precisionwordage.com/index.php/articles/how-does-a-technological-society-survive/</guid>
		<description><![CDATA[In simpler times, knowledge and proficiency were passed on through apprenticeship. Skills such as metal craft, wood working, even farming were transferred directly from person to person. This was also true of the arts, where greats like Michelangelo would take on apprentices for such mundane tasks as stretching canvases, mixing paints and priming walls for [...]]]></description>
			<content:encoded><![CDATA[<p>In simpler times, knowledge and proficiency were passed on through apprenticeship. Skills such as metal craft, wood working, even farming were transferred directly from person to person. This was also true of the arts, where greats like Michelangelo would take on apprentices for such mundane tasks as stretching canvases, mixing paints and priming walls for frescoes, and those apprentices would, in turn, become a new generation of professionals.</p>
<p>In today&#8217;s fast-paced information age, we rarely have the luxury of hands-on instruction. In fact, technologies change so fast, and the amount of technology needed to survive in this society expands so rapidly, that one-on-one learning has become nonviable.</p>
<p>So how do we keep on top of these shifting technologies? And how do we make it possible for others to follow at a speed that makes production practical?</p>
<p>Through documentation.</p>
<p>Information is gold. Badly written information is lead. Accurate data clearly presented drives sales, reduces support, increases employee efficiency, opens new opportunities.</p>
<p>Technologies are lost only when they are not clearly and effectively communicated. Products are under- or incorrectly utilized only when the user does not have quick access to easy-to-follow procedures.</p>
<p>Investing in documentation is the way to ensure that your product or activities actually do survive into the future.</p>
<p>Get your technology documented.</p>
<p>- Su</p>
]]></content:encoded>
			<wfw:commentRss>http://www.precisionwordage.com/articles/how-does-a-technological-society-survive/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Template in a teacup</title>
		<link>http://www.precisionwordage.com/articles/template-teacup/</link>
		<comments>http://www.precisionwordage.com/articles/template-teacup/#comments</comments>
		<pubDate>Wed, 21 Nov 2007 04:09:58 +0000</pubDate>
		<dc:creator>post</dc:creator>
		
		<category><![CDATA[Documentation]]></category>

		<category><![CDATA[Templates]]></category>

		<category><![CDATA[brand recognition]]></category>

		<category><![CDATA[corporate image]]></category>

		<category><![CDATA[documents]]></category>

		<category><![CDATA[FrameMaker]]></category>

		<category><![CDATA[image]]></category>

		<category><![CDATA[InDesign]]></category>

		<category><![CDATA[page layout]]></category>

		<guid isPermaLink="false">http://www.precisionwordage.com/index.php/articles/template-teacup/</guid>
		<description><![CDATA[In publishing software, a template is a set of design specifications. This would include page layout (margins, number of columns, how graphics should be positioned in relation to text), which fonts are to be used and when, line spacing, table formatting and myriad other little details that add up to a professional, easy-to-read document.
The idea [...]]]></description>
			<content:encoded><![CDATA[<p>In publishing software, a template is a set of design specifications. This would include page layout (margins, number of columns, how graphics should be positioned in relation to text), which fonts are to be used and when, line spacing, table formatting and myriad other little details that add up to a professional, easy-to-read document.</p>
<p>The idea is to have a common set of rules that can be used across different documents.</p>
<p>And why would we want this?</p>
<p>Most businesses have a corporate image. This can include one or more logos, specific colors and specific type faces. As part of a company&#8217;s brand recognition, using templates in your documents allows for a continuity of image throughout all publications.</p>
<p>Another reason is speed. With a well-designed template, a document can be formatted to top-quality professional appearance quickly and easily. If every document published had to be formatted manually to match a common style, publishing costs would go up faster than the price of real estate in SoCal.</p>
<p>The process is simple: A document is either created directly from within a template, in which case the correct formatting can be applied as it is authored; or the document, already authored, has the template attributes applied to it.</p>
<p>Updates or refinements to your brand image are also easy to make with a template (another cost savings). Instead of making changes to every document, you can change the template and let the changes cascade through your documents automatically.</p>
<p>Invest in good template design for your publications department, whether you use Microsoft® Word, Adobe® FrameMaker®, Adobe InDesign®, or any other publishing tools, and ensure that your templates include instructions on how to use them!<br />
The problems our clients can create for themselves when they don&#8217;t use templates range from comic to incredibly expensive, but that&#8217;s another blog on another day.</p>
<p>- David</p>
]]></content:encoded>
			<wfw:commentRss>http://www.precisionwordage.com/articles/template-teacup/feed/</wfw:commentRss>
		</item>
		<item>
		<title>&#8220;Two sets of eyes, minimum&#8221;</title>
		<link>http://www.precisionwordage.com/articles/two-sets/</link>
		<comments>http://www.precisionwordage.com/articles/two-sets/#comments</comments>
		<pubDate>Sat, 20 Oct 2007 21:09:26 +0000</pubDate>
		<dc:creator>post</dc:creator>
		
		<category><![CDATA[Documentation]]></category>

		<category><![CDATA[Proofing]]></category>

		<category><![CDATA[Chicago Manual of Style]]></category>

		<category><![CDATA[diagramming]]></category>

		<category><![CDATA[grammar]]></category>

		<category><![CDATA[Microsoft Manual of Style for Technical Writing]]></category>

		<category><![CDATA[precision wordage]]></category>

		<category><![CDATA[proof job]]></category>

		<category><![CDATA[proofreading]]></category>

		<category><![CDATA[snytax]]></category>

		<category><![CDATA[spell checkers]]></category>

		<category><![CDATA[Strunk and White's Elements of Style]]></category>

		<category><![CDATA[style]]></category>

		<category><![CDATA[writing]]></category>

		<guid isPermaLink="false">http://www.precisionwordage.com/wordpress/index.php/articles/two-sets-of-eyes-minimum/</guid>
		<description><![CDATA[If I had a quarter for every time I&#8217;ve been asked, &#8220;Why do you charge as much for proofreading as you do for writing?&#8221; I couldn&#8217;t retire. But I could fill a swear jar.
At Precision Wordage, we follow the rule &#8220;two sets of eyes, minimum.&#8221; No matter how good the writer, no matter how clean [...]]]></description>
			<content:encoded><![CDATA[<p>If I had a quarter for every time I&#8217;ve been asked, &#8220;Why do you charge as much for proofreading as you do for writing?&#8221; I couldn&#8217;t retire. But I could fill a swear jar.</p>
<p>At Precision Wordage, we follow the rule &#8220;two sets of eyes, minimum.&#8221; No matter how good the writer, no matter how clean a draft, whether you write it or we do, an author cannot proof his own work.</p>
<p>What skill set does it take to do a good proof job?</p>
<p>The most vital skill is the ability to spell. Spell checkers can catch flagrant misspellings, but won&#8217;t catch those nasty homonymic errors. &#8220;He road the hoarse across the open rode, ignoring his horse cough.&#8221; You see what I mean.</p>
<p>The next skill is grammar. When I was a kid, I used to diagram sentences for fun. It came as a shock to discover that diagramming hasn&#8217;t been taught for decades. Makes me feel old. The PWI team knows their syntax (the rules for forming words into correct sentences) cold.</p>
<p>Then there&#8217;s style. The basic bible for publishing is <em>The Chicago Manual of Style</em>. But then there&#8217;s the <em>Microsoft Manual of Style for Technical Writing</em>, and who knows how many other upstart new publications to cover the morass of media rules, regs, recks and refusals on grammar relating to technology, not to mention classics like Strunk and White&#8217;s <em>Elements of Style</em>. Our guys know `em all. And then some.</p>
<p>A proofer has to be able to think. For example, we deal with a lot of new technology, with scores of words that didn&#8217;t exist twenty years ago. If the proofer hits a term that&#8217;s spelled inconsistently in a client&#8217;s document, he&#8217;ll go online and search until he finds the most common usage, and recommend that the client use it that way. And he&#8217;ll stick it in the style notes for the job. If the client wants to spell a word differently, that&#8217;ll go in the style notes as well. And the proofer will know that with client A he always uses &#8220;dingles,&#8221; but client B expects &#8220;Dingles&#8221; to always be capitalized.</p>
<p>In proofreading, like most things in life, there are no absolutes. But we come close when it comes to catching those pesky little errors that detract from a document&#8217;s polish.</p>
<p>- Su</p>
]]></content:encoded>
			<wfw:commentRss>http://www.precisionwordage.com/articles/two-sets/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
