MadCap Software Forums

The good news is I think you can disable the DOCTYPE declaration in the target file (under Advanced options).

It's strange that entirely sensible behaviour in 3.1 has been removed in 4.0. Surely this must be a bug?

I noticed this too. The only thing I can think of is that it's something to do with the difference between IE7's Quirks and Standards mode and what Flare is writing out at the top of each .htm file. Look at the source of the same compiled topic from Flare 3.1 and Flare 4.0. Any differences at the ...

There's an enigmatic email from MadCap that seems to have hit Europe before the rest of the world. You'll probably get it soon. It consists of a new MadCap DITA logo and the date 10-29-08. And that's all ...

Even the "Flare add-on" bit might turn out to be wishful thinking. For MadCap DITA 1.0, I'd anticipate a DITA editor based on the Flare/Blaze base code. (Of course, I'd love to be proved wrong.)

My guess, FWIW, is that it'll be a separate application within the MadPak suite. But maybe integrated with Flare/Blaze in some way?

Have you received it yet? Interesting! Speculation?

Suggestion to MadCap: Since the Flare 4.0 honeymoon period seems to be over already, how about a (quick?) fix that would at least allow us to save topic files in .fltrev format for our X-Edit reviewers?

Suggestion to Fellow Users: Has anyone looked inside a .fltrev file to see what makes it ...

Ok, what about Windows Server 2008?

Beacuse I have to say, if the answer is "no" here too, I must question the value of a solution that relies on our customers never upgrading...

Lisa beat me to it! Inline formatting could certainly give you that error, for example:

<p style="background-color: 'BG Popup';">Northern Virginia is home to people from diverse backgrounds.</p>

Kevin, I'm not sure why you say three variable sets are needed. Surely one variable set "Fruit" with one variable "Product" would be enough? Then just override the default value of "Product" in each of the three targets.

Also, I suspect the tag needs the name of the variable set in there too ...

Hi Lisa. Yeah, but you have to do this one topic at a time (unless you know otherwise)! I'd like to be able to do this for several topics at once.

I agree that it would be nice if Flare allowed you to apply more than one CSS file to multiple topics.

However, if you know that you will always want to apply MyStyles.CSS and MyOtherStyles.CSS together, but still want (for some reason) to maintain them as separate CSS files, you can always link to ...

Anyone who has done a MadCap training course will know that the Course Guides use exactly this sort of layout. I don't know for sure if Scott DeLoach originally used Flare to generate this material, but if so I'm guessing he used a two- or possibly three-column table for his tasks, with each row ...

If all else fails, open the skin in the internal text editor and add a Title="Title Of Your Help System" attribute to the CatapultSkin element. Works for me.

That's why I said I would be interested to know what my options are.

Did this get resolved? I'm about to start documenting a .NET app and would be interested to know what my options are.

FWIW, my understanding is that Blaze 1.0 is essentailly a subset of Flare 4.0.

But what will be the relationship between Press and Flare?

Thanks for your thoughts, Kevin. Your example highlights exactly the sort of issues I had in mind. By marking up your tips, warnings and notes identically, you've compromised any future re-use of your content in which you might need to present them differently. (That's not a criticism of your choice ...

What do people think is the best way to mark up XHTML to maximise the opportunity for content re-use and re-purposing, particularly if you can’t (now) predict what those new uses and purposes might be?

To kick-start the discussion, two alternative strategies, at opposite extremes, suggest ...

Please let us know what response you get from MadCap. It's frustrating that this useful feature comes and goes!

Well, this is embarassing. I just needed to enable Show Markers. But, note, until you do this the MadCap:bodyProxy tag doesn't appear in the left-side block display either. So that's what confused me.

Update: They have mysteriously appeared.

As far as I can see (I'm still trying) this hasn't been fixed in v3.1.

Unless anyone knows better?

Has any one else seen (or rather not seen) this? I can add a body proxy to a master page, the bodyProxy tag is visible in the Text Editor, but the tag does not appear at all in the XML Editor, either within the master page itself or in the left-side tag bars. Consequently, I can't right-click and ...