Comments on: MadCap Software Sponsors the Tech Writer Voices Podcast

By: Help authoring news and Product Reviews | TechTotal Technical Writing, Instructional Designing - ID Training Blog

Wed, 10 Feb 2010 05:23:24 +0000

[...] A first in the industry. Flare supports two different work flows… [...]

By: document imaging JIm

document imaging JIm — Thu, 05 Feb 2009 12:26:37 +0000

intersting post, thanks

By: madcap flare and sharepoint - Dogpile Web Search

madcap flare and sharepoint - Dogpile Web Search — Mon, 09 Jun 2008 19:02:58 +0000

[...] Studio). http://www.idratherbewriting.com/2008/02/16/technical-wri... • Found on Ask.com MadCap Software Sponsors the Tech Writer Voices Podcast | I’d Rather Be … SharePoint Wikis: Both Liberating and Frustrating. WordPress Shopping Carts … Flare 2.0 and [...]

By: TecWriter

TecWriter — Wed, 05 Dec 2007 09:05:34 +0000

[...] A first in the industry. Flare supports two different work flows… [...]

By: Paul

Paul — Tue, 13 Nov 2007 03:20:07 +0000

I think that the argument for DITA is two-fold: users want to be able to import DITA files into Flare. Currently there is no way to import XML files into Flare. DITA support would presumably provide the ability to import DITA as well as export DITA.

Also, providing a DITA-target would allow users who have already invested in DITA tools the ability to output to formats they already have created. If you already have customized/stylized DITA outputs you’ve created and invested in, the ability to output to those pre-determined outputs would be quite handy.

Plus, since there are tools out there that take DITA content and format it into various outputs, you could conceivably have a much shorter implementation cycle for Flare. (Currently you have to spend quite a bit of time getting your style sheet customized in a way that makes your content look good. If Flare supported DITA, there would be options for out-of-the box output options that look good as well.)

So, I think those are some of the arguments in favor of DITA support from Flare. For some people it is a buzzword only; for others, it could shorten implementation cycles, and allow formatting reuse that has already been invested in.

By: Tom

Tom — Tue, 13 Nov 2007 03:10:42 +0000

Thanks for your comment. Mike Hamilton says that DITA support is scheduled for an upcoming version of Flare. If the industry buzz continues with DITA, it will surely make it into Flare. However, I’m curious what you hope to gain from DITA that you can’t already get with Flare. Usually the argument for DITA is to publish to multiple formats and reuse content. You can do this with Flare.

By: Paul

Paul — Tue, 13 Nov 2007 02:58:02 +0000

You mean besides the adulation of our adoring fan base on the MadCap forums? Isn’t that enough? It keeps me posting in the forums

By: Tom

Tom — Tue, 13 Nov 2007 02:54:43 +0000

Thanks for the positive feedback on Flare. I think it is a solid product too.

Congratulations on your MVP status. Besides boosting your professional credentials, what do you get for being a Flare MVP?

By: David

David — Fri, 09 Nov 2007 14:15:18 +0000

Lisa pointed out one reason for easy sync, but another one is that in many cases others want or need to review documentation before it gets published. Unless these parties have Flare installed as well, a Flare project will be of no use to them. Especially Word is a common format and comes with the ‘track changes’ feature. The final version can then be easily imported into Flare using a project setup that was created using an earlier document version. I am sure that the tech writers don’t use Word as a source because they think its editor is superior to Flare, but that they have no other choice if they need to collaborate with others who do not have Flare installed.
And just to clarify, I am also a Flare MVP.

By: Lisa

Lisa — Thu, 08 Nov 2007 23:06:37 +0000

Hi, Tom. I’m also a Flare MVP. You were questioning the reason for the Easy Sync feature… I have a feeling that feature was geared more toward the Flare user who needs to import information from subject matter experts (SMEs). The SMEs can write/update content in a Word file stored in a central location so all the different SMEs can access it and modify it, if necessary, and then the Flare author can import that file every time he/she rebuilds the help project.