<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Document Design&gt;Information Design&gt;Adobe FrameMaker</title>	<link>http://tc.eserver.org/dir/Articles/Document-Design/Information-Design/Adobe-FrameMaker</link>
	<description>A listing of the most recently indexed works about Articles and Document Design and Information Design and Adobe FrameMaker in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-10 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;Document Design&gt;Information Design&gt;Adobe FrameMaker</title>
		<link>http://tc.eserver.org/dir/Articles/Document-Design/Information-Design/Adobe-FrameMaker</link>
	</image>
	<item>
		<title>Unstructured Documents in Structured FrameMaker</title>
		<link>http://tc.eserver.org/33522.html</link>
		<guid>http://tc.eserver.org/33522.html</guid>
		<description>A few days ago, there was a thread on the Framers mailing list regarding working in the structured FrameMaker environment. Someone commented that editing unstructured documents in the structured interface does not affect the unstructured documents. I found this to be untrue recently.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Document-Design/Information-Design/Adobe-FrameMaker.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>