﻿<?xml version="1.0" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<!-- http://validator.w3.org/feed/ -->

<channel>
<title>TechScribe software documentation</title>
<link>http://www.techscribe.co.uk/</link>
<description>Things you need to know when you commission or produce software documentation, and the latest news from TechScribe.</description>
<image>
    <title>TechScribe software documentation</title>
    <url>http://www.techscribe.co.uk/images/techscribe-web-logo.png</url>
    <link>http://www.techscribe.co.uk/</link>
</image>
<language>en-gb</language>
<copyright>TechScribe</copyright>
<managingEditor>mike@techscribe.co.uk (Mike Unwalla)</managingEditor>
<webMaster>mike@techscribe.co.uk (Mike Unwalla)</webMaster>
<docs>http://validator.w3.org/feed/docs/rss2.html</docs> <!-- RSS 2.0 specification -->
<category>technical communication</category>
<category>technical writing</category>
<category>technical authoring</category>
<category>software documentation</category>
<category>software development</category>
<category>writing</category>
<atom:link href="http://www.techscribe.co.uk/feed.xml" rel="self" type="application/rss+xml" />


<item>
<title>Microsoft Manual of Style: a review</title>
<link>http://www.techscribe.co.uk/ta/microsoft-manual-of-style-fourth-edition.htm</link>
<description>The Microsoft Manual of Style contains "best practices for writing content for the web, optimizing for accessibility, and communicating to a worldwide audience". I am specially interested in these guidelines, and I review the three applicable chapters after I discuss some general problems with the Microsoft Manual of Style.</description>
<author>mike@techscribe.co.uk (Mike Unwalla)</author>
<category>style guide</category>
<category>technical documentation</category>
<category>technical publications</category>
<category>terminology</category>
<category>terms</category>
<guid isPermaLink="true">http://www.techscribe.co.uk/ta/microsoft-manual-of-style-fourth-edition.htm</guid>
<pubDate>14 Apr 2012 06:00:00 GMT</pubDate>
</item>



<item>
<title>ISTC online groups, winter 2011</title>
<link>http://www.techscribe.co.uk/ta/istc-winter-2011.htm</link>
<description>ISTC members discuss: the approval of documents; terms for the use of touch-screens; the ratio of software developers to technical communicators.</description>
<author>mike@techscribe.co.uk (Mike Unwalla)</author>
<category>document approval</category>
<category>software developers</category>
<category>technical communicators</category>
<category>terms</category>
<category>touch-screens</category>
<guid isPermaLink="true">http://www.techscribe.co.uk/ta/istc-winter-2011.htm</guid>
<pubDate>26 Mar 2012 09:00:00 GMT</pubDate>
</item>


<item>
<title>Technical writing newsletter 45: March 2012</title>
<link>http://www.techscribe.co.uk/techw/newsletter-45.htm</link>
<description>The latest news from TechScribe. Issue 45 is about a new training module (how to write for international readers), ISTC's Communicator in the PDF file format, and English that uses only words that have an Old English source.</description>
<author>mike@techscribe.co.uk (Mike Unwalla)</author>
<category>accessibility checker</category>
<category>international English</category>
<category>Communicator</category>
<category>Old English</category>
<guid isPermaLink="true">http://www.techscribe.co.uk/techw/newsletter-45.htm</guid>
<pubDate>13 Jan 2012 09:00:00 GMT</pubDate>
</item>




</channel>
</rss>

