<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Documentation&gt;DocBook</title>	<link>http://tc.eserver.org/dir/Articles/Documentation/DocBook</link>
	<description>A listing of the most recently indexed works about Articles and Documentation and DocBook in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Articles&gt;Documentation&gt;DocBook</title>
		<link>http://tc.eserver.org/dir/Articles/Documentation/DocBook</link>
	</image>
	<item>
		<title>DocBook to DITA Conversion Automation - Improving the Yield?</title>
		<link>http://tc.eserver.org/35041.html</link>
		<guid>http://tc.eserver.org/35041.html</guid>
		<description>With DITA implementations on the rise, and an entrenched DocBook community already in place, the resulting market interest has spurred interest in automated DocBook to DITA conversion. So I would expect offerings of automated DocBook to DITA conversion scripts to emerge in the next 6-10 months. This article addresses the real questions, &quot;What should I expect from automated tools?&quot; and &quot;Will they work for me?&quot; from the viewpoint of live experience with numerous DocBook to DITA conversions. The answers to these questions are not usually obvious.</description>
	</item>
	<item>
		<title>Producing Documentation and Reusing Information in XML, Part 1: Document Publishing Using XML</title>
		<link>http://tc.eserver.org/35017.html</link>
		<guid>http://tc.eserver.org/35017.html</guid>
		<description>XML provides a way to identify data items and subcomponents within any structured data set, but has its roots in documentation development and production. Robust, open standards for XML document markup and a rich set of freely available tools for XML document parsing and format conversion make it easy to install and configure a complete documentation development and formatting environment on any UNIX® or Linux® system.</description>
	</item>
	<item>
		<title>Producing Documentation and Reusing Information in XML, Part 2: Reuse Information in XML Documentation</title>
		<link>http://tc.eserver.org/35018.html</link>
		<guid>http://tc.eserver.org/35018.html</guid>
		<description>Discover simple solutions to reuse information in XML documentation, such as how to use XInclude to include other documents at a given point in a document and how to use XPointer to include small document fragments from other documents or a similar pool of information in XML format. Also, get tips for structuring XML documentation to simplify information reuse, and learn how to maintain stand-alone documents that you can incorporate into larger documents.</description>
	</item>
	<item>
		<title>Producing Documentation and Reusing Information in XML, Part 3: Creating Multi-Target XML Documents</title>
		<link>http://tc.eserver.org/35019.html</link>
		<guid>http://tc.eserver.org/35019.html</guid>
		<description>XML is an optimal format for writing documentation that you can use with many different documentation software packages and production environments. In this third article in the series, discover how to create single-source documents that can produce output in a variety of different output formats.</description>
	</item>
	<item>
		<title>What a Technical Writer Should Know About DocBook?</title>
		<link>http://tc.eserver.org/34784.html</link>
		<guid>http://tc.eserver.org/34784.html</guid>
		<description>DocBook is a set of tools for implementing XML (Extended Markup Language)-based structured documentation. It is developed back in 1991 and is widely used today by those technical writers who generate single-sourced documentation. It is especially well suited for software, hardware and networking documentation.</description>
	</item>
	<item>
		<title>Modular Docs Part 2: DITA vs. DocBook</title>
		<link>http://tc.eserver.org/34486.html</link>
		<guid>http://tc.eserver.org/34486.html</guid>
		<description>When IBM decided to focus on topic-oriented documentation, it created the Darwin Information Typing Architecture (DITA), even though there was already a huge investment in DocBook. Moving to a new architecture was a decidedly non-trivial undertaking--both technically and politically--so it is worth an inquiry as to the reasons for making that move.</description>
	</item>
	<item>
		<title>DocBook versus DITA: Will the Real Standard Please Stand Up?</title>
		<link>http://tc.eserver.org/33968.html</link>
		<guid>http://tc.eserver.org/33968.html</guid>
		<description>More than a decade ago DocBook became the standard for the few brave souls forging ahead in XML publications. DocBook offered a cheaper and more efficient way to publish to multiple formats. Single-sourcing became a reality for hardware and software companies. However, in recent years, many in technical documentation publications have proclaimed DITA as the standard for XML documentation. DITA offered architecture in which to create and publish structured content.&#xD;&#xD;Are these two seemingly rival standards really that different? This article from Teresa Mulvihill answers this question with comparative examples, and allows you, the audience, to decide for yourselves.</description>
	</item>
	<item>
		<title>DocBook or DITA?</title>
		<link>http://tc.eserver.org/32087.html</link>
		<guid>http://tc.eserver.org/32087.html</guid>
		<description>XML is the future. You hear it at every conference you go to, in every magazine you pick up, in every article you read on-line. For technical writers, right now that future comes down to two products—DocBook or DITA. But what exactly are they, and which one should you choose? They are schemas for creating XML.</description>
	</item>
	<item>
		<title>DocBook for the Masses</title>
		<link>http://tc.eserver.org/31161.html</link>
		<guid>http://tc.eserver.org/31161.html</guid>
		<description>Having new DocBook standards in place may do little to push adoption. An important factor in driving user adoption is the availability of software that implements the standard. It would be interesting to see whether big software companies would jump on the bandwagon...Unless the open-source community comes to the rescue!</description>
	</item>
	<item>
		<title>Getting Started with the DocBook XML Dialect</title>
		<link>http://tc.eserver.org/27740.html</link>
		<guid>http://tc.eserver.org/27740.html</guid>
		<description>Gets you started with DocBook, an SGML/XML dialect that describes the content of technical articles and other documents. David discusses the benefits of using DocBook, and then describes how to plan and modularize a large document conversion project.</description>
	</item>
	<item>
		<title>DocBook Demystification Howto</title>
		<link>http://tc.eserver.org/26373.html</link>
		<guid>http://tc.eserver.org/26373.html</guid>
		<description>This howto attempts to clear the fog and mystery surrounding the DocBook markup system and the tools that go with it. It is aimed at authors of technical documentation for open-source projects hosted on Linux, but should be useful for people composing other kinds on other Unixes as well.</description>
	</item>
	<item>
		<title>Using DocBook to Generate WebHelp</title>
		<link>http://tc.eserver.org/26309.html</link>
		<guid>http://tc.eserver.org/26309.html</guid>
		<description>A brief tutorial on creating cross-platform WebHelp (similar to that produced by RoboHelp) using DocBook.</description>
	</item>
	<item>
		<title>Moving to DocBook</title>
		<link>http://tc.eserver.org/26308.html</link>
		<guid>http://tc.eserver.org/26308.html</guid>
		<description>DocBook is a powerful tool for creating and maintaining documentation. However, there are a  number of factors you should consider before you move your documentation to DocBook. This article discusses reasons for and against making the switch to DocBook.</description>
	</item>
	<item>
		<title>Using XML for Document Authoring and Management</title>
		<link>http://tc.eserver.org/26310.html</link>
		<guid>http://tc.eserver.org/26310.html</guid>
		<description>An introduction to XML (Extensible Markup Language) and how technical writers can use it to create and manage their documentation.</description>
	</item>
	<item>
		<title>DocBook Conversions with XFC</title>
		<link>http://tc.eserver.org/26306.html</link>
		<guid>http://tc.eserver.org/26306.html</guid>
		<description>There are a number of tools available for transforming DocBook XML documents to various formats. All of these tools have strengths, as well as some noticeable weaknesses and drawbacks. This article looks at the benefits of using the XMLmind FO Converter, a graphical, highly configurable, and cross-platform application designed to transform DocBook XML files to any supported output format.</description>
	</item>
	<item>
		<title>Docbook Frequently Asked Questions</title>
		<link>http://tc.eserver.org/26193.html</link>
		<guid>http://tc.eserver.org/26193.html</guid>
		<description>This is a collation of some Frequently Asked questions regarding Docbook. The initial focus will be on the XML version of the DTD, and the XSLT based stylesheets.</description>
	</item>
	<item>
		<title>Get Going With DocBook</title>
		<link>http://tc.eserver.org/26197.html</link>
		<guid>http://tc.eserver.org/26197.html</guid>
		<description>A tutorial on writing documentation that will be used in a particular project.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Documentation/DocBook.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>