Sorry, the software to which I was referring is the application for
which we're providing context-sensitive help.

I haven't found any documentation stating anything about needing to
break up the FM files per topic. Our software developer claims it's
necessary, and our tests on the machine control prove him to be correct.
I suspect the problem is with our control's software. At the very least,
I'm missing something that will make it all work.

We're using a custom .h file that holds our topic IDs and the control
screen IDs (Map IDs).  Example: #define IDH_ScreenName 123. The text is
the same as what we put in the TopicAlias marker. The screen ID is the
number assigned to the screen by the software developers.

-----Original Message-----
From: Bill Swallow [] 
Sent: Tuesday, April 10, 2007 4:40 PM
To: Gross, Karen
Cc: framers at
Subject: Re: FrameMaker files and CHM

Which software are you talking about? WWP?

You most certainly don't have to have one topic per FM file. That
defeats the whole point of single-sourcing with FM and the point of
using WWP in the first place.

Can you provide details?

On 4/10/07, Gross, Karen <GrossK at> wrote:
> I've assigned my markers, one per heading that starts a new page, and
> mapped the headings in WWP. Our software, which resides on a machine
> control, seems to require that we break up the FM file into smaller
> files, one topic per file. That doesn't sit right with me. It seemed
> me that I could have more than one topic, each assigned to separate
> headings, that reside in one FM file.

Bill Swallow
HATT List Owner
WWP-Users List Owner
Senior Member STC, TechValley Chapter
STC Single-Sourcing SIG Manager
avid homebrewer and proud beer snob
"I see your OOO message and raise you a clue."

Reply via email to