TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
> -----Original Message-----
> From: Gilda_Spitz -at- markham -dot- longview -dot- ca
> [SMTP:Gilda_Spitz -at- markham -dot- longview -dot- ca]
>
> 1. The reason I asked the original question is because we currently
> distribute that document in rtf format, so that each System Admin can use
> Word or WordPad to add details specific to his or her own organization.
> But
> I HATE having to use Word to create that rtf file. We tried creating it in
> Frame, as we do all our other documents, and then saving as rtf, but it
> didn't work. Is there a special trick to making the conversion work
> properly?
>
FrameMaker supports a tonne of formatting and capability beyond what RTF has
so . . . no . . . the conversion is probably working properly but what you
get is limited by the limitations of RTF.
How about having each Sysadmin provide you RTF or Word documents that you
import by reference into your FrameMaker doc? That way, the Sysadmin can
update the document using their tool and the updates are automatically
reflected in FrameMaker.
