<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	>
<channel>
	<title>Comments on: MIF to the rescue</title>
	<atom:link href="http://www.itauthor.com/2007/05/04/mif-to-the-rescue/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.itauthor.com/2007/05/04/mif-to-the-rescue/</link>
	<description>Stuff about technical writing and software</description>
	<lastBuildDate>Wed, 01 Sep 2010 14:58:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Michael MÃ¼ller-Hillebrand</title>
		<link>http://www.itauthor.com/2007/05/04/mif-to-the-rescue/comment-page-1/#comment-15</link>
		<dc:creator>Michael MÃ¼ller-Hillebrand</dc:creator>
		<pubDate>Sat, 05 May 2007 09:01:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.itauthor.com/wordpress/2007/05/04/mif-to-the-rescue/#comment-15</guid>
		<description>Disclaimer: I am a FrameMaker consultant.

So you want to do single-sourcing and want to have decent layout in PDF files? How dare you... :-)

For single-source workflows I always recommend to start with a classic DTP application including page layout features. It is *a lot* easier to convert such documents into any HTML-based online format (by throwing away all those &#039;keep with next/previous paragraph&#039;, &#039;start a new page here&#039;, &#039;make a discretionary hyphen there&#039; stuff) than the other way. Even the most advanced XSL-FO programming cannot forsee the intricate layout restrictions of a fixed page size (admitted: unless the layout is highly regular).

So, going from RoboHelp, Flare, or other online-help creation tools to print publishing is harder than going from FrameMaker (or Word) to HTML.

I am not surprised,

- Michael</description>
		<content:encoded><![CDATA[<p>Disclaimer: I am a FrameMaker consultant.</p>
<p>So you want to do single-sourcing and want to have decent layout in PDF files? How dare you... :-)</p>
<p>For single-source workflows I always recommend to start with a classic DTP application including page layout features. It is *a lot* easier to convert such documents into any HTML-based online format (by throwing away all those 'keep with next/previous paragraph', 'start a new page here', 'make a discretionary hyphen there' stuff) than the other way. Even the most advanced XSL-FO programming cannot forsee the intricate layout restrictions of a fixed page size (admitted: unless the layout is highly regular).</p>
<p>So, going from RoboHelp, Flare, or other online-help creation tools to print publishing is harder than going from FrameMaker (or Word) to HTML.</p>
<p>I am not surprised,</p>
<p>- Michael</p>
]]></content:encoded>
	</item>
</channel>
</rss>
