Don’t double post please – use the FM Integration forum.
That being said – to use the FM Publish command you have to do some homework first – you’ll need to set up a FM to RH project first to establish the conversion settings to be captured in a settings.isf file. However, I suspect your PDF isn’t being included because RH doesn’t know it’s there because it’s not a baggage file in the RH project (the one that’s hidden in the background when you “publish” straight from FM).
Thanks for the reply and for the heads up on double posting. I only wanted to get the question out so that it is viewed by people who view FrameMaker and RoboHelp postings. As I mentioned before, I don't know if this is on the FrameMaker end or the RoboHelp end.
Yes, I did create a .XPJ file, but it still did not work. I will look at this "baggable file" reference that you mentioned to see where that leads.
Thanks again for the reply.
@Peter - you could toss this one over to the FM Integration section as it concerns FM to RH functionality.
Thanks Peter and Jeff,
I am going to do some testing today to see if I can get my FrameMaker 11 hypertext links to PDFs, to get pushed through to
RoboHelp and WebHelp output.
It sounds like I definitely need:
- To point to a .XPJ
- To create an .ISF file
Hopefully, that will do the trick.
Thanks again to both of you.
I suspect they will just fine if you follow the traditional TCS integration route of creating a RH project and either linking or importing FM content. The external PDF would then be added to the RH project as a Baggage file, so that it's included in the help output generated.
What I'm suspicious of is the direct publish method all from within FM; to my understanding, once you've established your FM to RH settings and saved them off in a .isf file, then you can discard the RH project and "publish" on the fly by using the .isf file as the template for help generation. Doing it that way seems to strip a lot of the control over other things (like baggage files) that a full RH project offers you and that isn't included in an .isf file. So it may still not work in your case.