Re: Legacy help projects and job openings

[Alexia Prendergast <alexiap -at- SEAGATESOFTWARE -dot- COM>]

Hi, Julie,

We have a similar problem -- our product runs on two operating systems,
but 99% of the material is the same. Instead of two separate help
systems,
we maintain one set of files for the common stuff. Then we have separate
files for our platform-specific info. I set up two separate HPJs that
each
include the common files, then their specific files, so two versions of
the help
are built from essentially one set of files. We do some more stuff with
the way
we set up the directory structure within the code tree -- let me know
off-line
if you want more info.

Thanks,
A.

--
Alexia Prendergast
Senior Technical Writer
Seagate Software
mailto:alexiap -at- sems -dot- com

>-----Original Message-----
>From:  Julie Tholen [SMTP:julie_tholen -at- CNT -dot- COM]
>Sent:  Wednesday, August 20, 1997 1:58 PM
>To:    TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
>Subject:       Legacy help projects and job openings
>
>2. We have three products which use the same network management tool.
>The tool is smart enough to know which product it is on and pulls the
>appropriate interface .bmp. My help system(s) have to service all three
>products. I would like to have one help system, and three .bmp files
>that reflect the appropriate product.
>
>Once you get pass the interface .bmp, the functionality of the
>management system doesn't change, but the graphics need to.  Any
>suggestions? Should I just scrap that idea and
>build three separate help systems? The products are upgraded
>independently of each other.
>
>

 TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot-  Send commands
   to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
  Search the archives at http://www.documentation.com/  or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html