Copy link to clipboard
Copied
My client has finally decided that we will upgrade from Tech Comm Suite 1.5 to the latest version, just not right now (the decision alone is progress at least).
They also want to switch to using numeric map IDs for CSH (instead calling the path/filename which is linked externally to the application form name), which is how they originally wanted to call help. Currently I have a separate CSH paragraph style that lists the form name as well as xrefs to create the path and html.filename. There are often multiple such paragraphs within a topic, because multiple forms call the same topic. I generate a list of these paragraphs, do a little search/replace magic, and hand off a "mapping file.txt" to the developer. I don't remember how or why we came up with this as the best solution, but it's worked for several years now, so we've stuck with it.
I have read many forum posts to understand the correct process for using map IDs with TCS, but still have some questions.
All guidance is greatly appreciated,
Laurie
For posterity, here is the resolution we came to offline.
Copy link to clipboard
Copied
I'm not too big on FM->RH integration so I'm hoping Jeff will jump in.
Before I start, a little clarification on terms used: A topic id is an alphanumeric string to identify a topic. A map number is a numeric id. What you refer to as map ID is what RoboHelp calls a map number.
You may also be interested in: https://www.wvanweelden.eu/article-category/context-sensitivity
Kind regards,
Willam
Copy link to clipboard
Copied
Thanks Willam. Your response (and your site) were very helpful. I also learned a lot from a recent Adobe webinar I found ("GUEST BLOG: Setting the Help Hooks: Context Sensitive Help Using RoboHelp « TechComm Central by Adob...).
I am still unclear on some of the particulars of creating the MapIDs in Framemaker, and hope Jeff jumps in. Here's what I did:
I've read recommendations that if you're just using RH to process the files (i.e. using FM as the main authoring tool), then you should enter the CSH markers in FM and link to the FM files in RH, but if you are doing any post-processing in RH, you should import the FM files and create the .h file in RH. Sounds like Jeff creates the markers in FM but imports the FM files. So I started over and tried it that way.
After importing the book into RH, I looked at the default .h file again. This time there was still only one entry, but it was to the cover chapter from the FM book.
This thread (Re: Context-Sensitive HELP!!!!!) says I still have to import the .h file before the Topic IDs will appear - I want to create a .h file, so what exactly am I importing? I've tried Force Update, I tried creating a new .h file and exporting that -- nothing is getting me the two Topic IDs that I created in FM.
I hope someone can help me to bridge FM8>RH7 and come up with map files that I can give the developer.
Thanks,
Laurie
Copy link to clipboard
Copied
Hi Laurie, I'll try to explain my process and show what I'm getting with some screenshots.
For this project I author in FM and import to RH currently using TCS4. I tried linking initially, but because I'm using the FM concept of a master book of books, RH seemed to choke on the linking process way back in TCS2, so I ditched that method and went the import route (supposedly it's improved, but I haven't had any time to test). I set up a CSH marker type in FM with the product's program name as the marker text. That program name comes across as the Map ID in RH (hopefully seen in these 2 screenshots):

and the end of that line that got cut off -

The FM content is busted up into topics using the Heading 1 and Heading 2 FM paragraph types and you'll notice that CSH bookmark (#CSH_124) gets generated and placed on the topic (see HTML view of this Cash Requirements Lists topic):

This all ends up producing a BSSCDefault.h file with a series of lines like this:
#define GJP86 1731
#define GJP10 1732
#define GJP23 1733
(that's a number sign, the word define the program name and the Map number that RH assigned in case that text gets mangled).
I take that .h file and use it as the source for the program to use to launch the CSH help when the user is on that program screen and presses F1. We're using the JavaScript method of invoking the help that will translate the program name and find that Map# to use.
Copy link to clipboard
Copied
Thanks Jeff. The first screenshot was what I was expecting. Here's what I did and the results:


Laurie
Copy link to clipboard
Copied
May be a bug - want me to have a look at your sample FM book?
Copy link to clipboard
Copied
That would be great, thanks Jeff. I'll send it privately.
Copy link to clipboard
Copied
You may still have my e-mail on file – if not, PM-me
Copy link to clipboard
Copied
On a whim, since I'm now importing rather than linking, I tried importing from FM8 directly into our standalone version of RH10, and I do get the Map IDs correctly that way. I need to figure out the mapping and topic breaks - is there anything I need to watch for doing it this way, without TCS? It seems too easy, i.e. why would anyone buy TCS if they can just import FM files directly into RH?
Copy link to clipboard
Copied
Pricing – cheaper to buy the suite than the individual programs
Copy link to clipboard
Copied
Yeah, but are there any other TCS integration bits that would be missing that might be important?
For me, having FM8 and RH10 already, is there anything I need to do differently or watch for?
Copy link to clipboard
Copied
Only for the linking functionality
Copy link to clipboard
Copied
For posterity, here is the resolution we came to offline.
I think we'll be safe for a few years at least, until browsers outpace RH10. Maybe by then the client will be able and willing to change our doc strategy/delivery and we can upgrade to something more current.
So glad to be able to ditch RH7 and all the workarounds I had to juggle to get TCS1.5 to behave!
Now I just need to hope the developers can figure out how to work with the new map files and API!
MANY many thanks to Jeff Coatsworth for his time helping me to get to this point!
Laurie
Find more inspiration, events, and resources on the new Adobe Community
Explore Now