<!DOCTYPE html PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN'>
<html><head><meta http-equiv="Content-Type" content="text/html;charset=utf-8">
<style>BODY{font:10pt Tahoma, Verdana, sans-serif}</style></head><body>
I believe what Winfried says is correct. The purpose of the integration provided in TCS is to give a "live" connection between your FM book and RoboHelp, so that if the book contents change, RH knows about it. In that case your RH project is *linked* to the FM book. Without TCS, you simply import the book into RH and forego the dynamic link that TCS gives.<br><br>I applaud your desire to single-source. You should also look at alternative solutions such as WebWorks ePublisher, Flare, and MIF2Go, as well as the TCS. TCS includes other applications that you may or may not want to spend money on. <br><br>HTH!<br>Roger<br><br>Roger Shuttleworth<br>Technical Documentation<br>AV-BASE Systems Inc.<br>1000 Air Ontario Drive, Suite 200<br>London, Ontario<br>N5V 3S4<br>Tel. 519 691-0919 ext. 330<br><blockquote style="padding-left: 5px; margin-left: 5px; border-left: #0000ff 2px solid; margin-right: 0px"><hr><b>From:</b> Reng, Dr. Winfried [mailto:wreng@tycoint.com]<br><b>To:</b> John Sgammato [mailto:jsgammato@IMPRIVATA.com], Thomas Scalise [mailto:Thomas.Scalise@CrossMatch.com], framers@lists.frameusers.com [mailto:framers@lists.frameusers.com]<br><b>Sent:</b> Thu, 04 Aug 2011 02:52:44 -0400<br><b>Subject:</b> AW: FrameMaker 10 and RoboHELP 9<br><br><div class="WordSection1"><p class="MsoNormal"><span style="color:#1F497D">Hi,</span></p><p class="MsoNormal"><span style="color:#1F497D"> </span></p><p class="MsoNormal"><span style="color:#1F497D">I don‘ t have RoboHelp or the TCS. However, as far as I know </span></p><p class="MsoNormal"><span style="color:#1F497D">RoboHelp can process FrameMaker books whether it’s integrated</span></p><p class="MsoNormal"><span style="color:#1F497D">in the TCS or not. The only advantage of the TCS is that you can </span></p><p class="MsoNormal"><span style="color:#1F497D">start the conversion from within FrameMaker.</span></p><p class="MsoNormal"><span style="color:#1F497D">Otherwise you must manually direct RoboHelp to the folder with</span></p><p class="MsoNormal"><span style="color:#1F497D">the FrameMaker book.</span></p><p class="MsoNormal"><span style="color:#1F497D"> </span></p><p class="MsoNormal"><span style="color:#1F497D">Best regards</span></p><p class="MsoNormal"><span style="color:#1F497D"> </span></p><p class="MsoNormal"><span style="color:#1F497D">Winfried</span></p><p class="MsoNormal"><span style="color:#1F497D"> </span></p><div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"><div><div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"><p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Von:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a href="mailto:framers-bounces@lists.frameusers.com">framers-bounces@lists.frameusers.com</a> [mailto:<a href="mailto:framers-bounces@lists.frameusers.com">framers-bounces@lists.frameusers.com</a>] <b>Im Auftrag von </b>John Sgammato<br><b>Gesendet:</b> Mittwoch, 3. August 2011 21:10<br><b>An:</b> Thomas Scalise; <a href="mailto:framers@lists.frameusers.com">framers@lists.frameusers.com</a><br><b>Betreff:</b> RE: FrameMaker 10 and RoboHELP 9</span></p></div></div><p class="MsoNormal"> </p><p class="MsoNormal"><span style="color:#1F497D">The full integration works only within TCS. If you have FM10 and you have RH9, but not TCS, then you don’t have the integration. </span></p><p class="MsoNormal"><span style="color:#1F497D">When you have the TCS integration, you can write in FM and then click Publish to go directly to your RH outputs. The RH projects must be set up ahead of time, of course, which is not a trivial step, but you would have to do that in any event. So TCS3 is not a magic wand, but it is a time saver and error-reducer.</span></p><p class="MsoNormal"><span style="color:#1F497D">Ymmv</span></p><p class="MsoNormal"><span style="color:#1F497D">john </span></p><p class="MsoNormal"><span style="color:#1F497D"> </span></p><div><div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"><p class="MsoNormal"><b><span>From:</span></b><span> <a href="mailto:framers-bounces@lists.frameusers.com">framers-bounces@lists.frameusers.com</a> [mailto:<a href="mailto:framers-bounces@lists.frameusers.com">framers-bounces@lists.frameusers.com</a>] <b>On Behalf Of </b>Thomas Scalise<br><b>Sent:</b> Wednesday, August 03, 2011 1:26 PM<br><b>To:</b> <a href="mailto:framers@lists.frameusers.com">framers@lists.frameusers.com</a><br><b>Subject:</b> FrameMaker 10 and RoboHELP 9</span></p></div></div><p class="MsoNormal"><span> </span></p><p class="MsoNormal"><span>Esteemed colleagues,</span></p><p class="MsoNormal"><span> </span></p><p class="MsoNormal"><span>Can anyone give me specific information about the supposed special relationship between Frame 10 and RoboHELP 9 that allow for single source authoring of a help system? If it exists, must it occur within the TCS? I have a large update project and it would be immensely easier with single source capability.</span></p><p class="MsoNormal"><span> </span></p><p class="MsoNormal"><span>Thanks in advance for any suggestions, info, etc.</span></p><p class="MsoNormal"><span> </span></p><p class="MsoNormal" style="mso-margin-top-alt:1.0pt;margin-right:0cm;margin-bottom:1.0pt;margin-left:0cm"><span>Tom Scalise</span></p><p class="MsoNormal" style="margin-bottom:1.0pt"><span>Information Development Manager</span></p><p class="MsoNormal" style="margin-bottom:1.0pt"><span>Office (561) 622-5416</span></p><p class="MsoNormal" style="margin-bottom:1.0pt"><span>Fax (561) 622-9938</span></p><p class="MsoNormal" style="margin-bottom:1.0pt"><span><a href="mailto:thomas.scalise@crossmatch.com">thomas.scalise@crossmatch.com</a><b><span style="color:#365F91"></span></b></span></p><p class="MsoNormal"><span><a href="http://www.crossmatch.com/"><span style="text-decoration:none"><img id="Picture_x0020_1" src="cid:image001.gif@01cc5283.e03c1890" alt="Description: Description: Description: cid:image001.gif@01CBDF0D.2B428620" defaultcontextmenu="yes" border="0" height="55" width="196"></span></a><span style="color:#1F497D"></span></span></p><p class="MsoNormal"><span> </span></p><p class="MsoNormal"><span><br>This e-mail message from Cross Match Technologies, Inc. is intended only for the individual or entity to which it is addressed. This e-mail may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you received this e-mail by accident, please notify the sender immediately and destroy this e-mail and all copies of it. </span></p></div></div></blockquote><style>
@font-face {font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;}
p.MsoNormal,li.MsoNormal,div.MsoNormal {margin:0cm;margin-bottom:.0001pt;font-size:11.0pt;font-family:"Calibri","sans-serif";}
a:link,span.MsoHyperlink {mso-style-priority:99;color:blue;text-decoration:underline;}
a:visited,span.MsoHyperlinkFollowed {mso-style-priority:99;color:purple;text-decoration:underline;}
p.MsoAcetate,li.MsoAcetate,div.MsoAcetate {mso-style-priority:99;mso-style-link:"Sprechblasentext Zchn";margin:0cm;margin-bottom:.0001pt;font-size:8.0pt;font-family:"Tahoma","sans-serif";}
span.SprechblasentextZchn {mso-style-name:"Sprechblasentext Zchn";mso-style-priority:99;mso-style-link:Sprechblasentext;font-family:"Tahoma","sans-serif";}
p.BalloonText,li.BalloonText,div.BalloonText {mso-style-name:"Balloon Text";mso-style-link:"Balloon Text Char";margin:0cm;margin-bottom:.0001pt;font-size:11.0pt;font-family:"Calibri","sans-serif";}
span.BalloonTextChar {mso-style-name:"Balloon Text Char";mso-style-priority:99;mso-style-link:"Balloon Text";font-family:"Tahoma","sans-serif";}
span.E-MailFormatvorlage21 {mso-style-type:personal;font-family:"Cambria","serif";color:#1F497D;}
span.E-MailFormatvorlage22 {mso-style-type:personal;font-family:"Calibri","sans-serif";color:#1F497D;}
span.E-MailFormatvorlage23 {mso-style-type:personal-reply;font-family:"Calibri","sans-serif";color:#1F497D;}
.MsoChpDefault {mso-style-type:export-only;font-size:10.0pt;}
@page WordSection1 {size:612.0pt 792.0pt;margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1 {page:WordSection1;}
</style>
</body></html>