TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Re: What Program Do You Use for Software Documentation?
Subject:Re: What Program Do You Use for Software Documentation? From:"Paul Pehrson" <paulpehrson -at- gmail -dot- com> To:"CL T" <straylightsghost -at- gmail -dot- com> Date:Thu, 23 Oct 2008 10:42:58 -0600
** Disclaimer: I'm a Certified Flare Trainer and MadCap MVP, but that isn't
my primary job **
What about code samples didn't work the way you wanted? I'm using Flare
exclusively and I'm including code samples and they work just fine. I
created a separate class of <p> for code samples, and then adjusted my style
settings for that class in my stylesheet. My code samples look great in both
online and printed output.
I'm not sure what functionality you want that you're not getting here, but I
don't see any problem with the way Flare handles code samples.
Paul Pehrson
docguytraining.com
On Thu, Oct 23, 2008 at 8:34 AM, CL T <straylightsghost -at- gmail -dot- com> wrote:
> I've written a few manuals in Flare that are single-sourced -- it worked
> well (with the exception of Code Samples...still a LOT of work to do there
> MadCap).
>
> [...]
>
>
> -Collin Turner
> Tech Writer, Screencaster, Writer
> www.collinturner.com
>
>
>
> On Thu, Oct 23, 2008 at 6:38 AM, Stephen Arrants <steve -at- mbfbioscience -dot- com
> >wrote:
>
> > > I do take exception to including Flare, RoboHelp, etc. as single
> > > source tools. They normally require some other tool to produce the
> > > text, and often the formatting before transforming it. As such they
> > > are transformers and are only marginally single source tools. They
> > > are more accurately a multiple plath transforming tool.
> > >
> > > Scott
> >
> > We've had success with Flare 4, publishing HTML Help and a printed manual
> > from the same source files. Granted, it took a lot of work and
> re-education
> > of staff to do the groundwork of setting up styles, conditions, etc. But
> it
> > can be done, and it was less painful than writing in Framemaker and then
> > wrestling that content into the online suit of clothes.
> >
> >
> > --
> > Steve Arrants steve -at- mbfbioscience -dot- com
> > Writer
> > MBF Bioscience (Microbrightfield, Inc.)
> > +1.802.288.9290 ext: 124
> > www.mbfbioscience.com
> >
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ComponentOne Doc-To-Help 2009 is your all-in-one authoring and publishing
solution. Author in Doc-To-Help's XML-based editor, Microsoft Word or
HTML and publish to the Web, Help systems or printed manuals. http://www.doctohelp.com
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-