Master conditional indicators tag set

[aharper]

Hi,

I am new to Flare I'm converting a huge FM project that contains many books, and am importing each book separately in order to avoid overwriting images with the same names and to keep things tight and together. This working well except for the conditional text indicators. Because I'm importing each FM book separately, each one is creating its own condition tag set. This alone is ok but will be very tedious to deal with when I create my master TOC and set up my target for my online output (which includes all topics from all books and shows/hides accordingly) and I have to set several conditions in each set to include or exclude. Very time consuming!

Is there a way to create a master condition tag set - similar to having a master stylesheet? I envision setting my conditions to include/exclude just once for the entire Flare project and applying that master condition set to the online help output that includes all my topics. Then, for each PDF target output for each book, I could then revert back to using the settings for each condition tag set for each book.

A note - the tags sets are the same in each book.

Thanks!
Adriana

[i-tietz]

The only thing I can think of is to do a project wide find&replace with Flare or another editor/tool that allows you to do a bulk f&r ...

[lacastle]

Very time consuming!

fyi - much of what needs to be done during a conversion from FM to Flare is very time consuming! there may be some quick tricks to make things a little smoother, but it still takes a lot of time to get started with Flare.

[aharper]

Hi Laura,

Thanks- that is somewhat comforting. I keep thinking I'm doing it wrong because there seems to be a lot of things that need 'doing'.

i-tietz - My apologies if I wasn't being clear. I'm not looking to find and replace anything I don't think. I'm looking to create a master set of conditions to set as include/exclude that would be applied to each topic in the online help output, instead of selecting which conditions should be included/excluded in each set, from each book, brought in with each import.

Adriana

[DocuWil]

The webinar below could help you much more:

http://www.madcapsoftware.com/demos/webinars.aspx
Subject:
Advanced use of Condition Tags and Single Sourcing in MadCap Flare

[NorthEast]

My apologies if I wasn't being clear. I'm not looking to find and replace anything I don't think. I'm looking to create a master set of conditions to set as include/exclude that would be applied to each topic in the online help output, instead of selecting which conditions should be included/excluded in each set, from each book, brought in with each import.

I think the point being made was that if you had the same types of conditions in each import, then you could use a find and replace to change these import-specific conditions to use a single global condition.

For example, say you had a 'PrintOnly' condition in each FrameMaker file, then your Flare project would have multiple separate conditions from each import, like importA.PrintOnly and ImportB.PrintOnly. You could search for these conditions, and rename them to a global condition; e.g. rename importA.PrintOnly to Global.PrintOnly, and so on.

To do this, you can search for the condition in the HTML code (using find in source code); which are in the format:

Code: Select all

MadCap:conditions="ConditionFilename.ConditionName"

[i-tietz]

I think the point being made was that if you had the same types of conditions in each import, then you could use a find and replace to change these import-specific conditions to use a single global condition.

For example, say you had a 'PrintOnly' condition in each FrameMaker file, then your Flare project would have multiple separate conditions from each import, like importA.PrintOnly and ImportB.PrintOnly. You could search for these conditions, and rename them to a global condition; e.g. rename importA.PrintOnly to Global.PrintOnly, and so on.

To do this, you can search for the condition in the HTML code (using find in source code); which are in the format:

Code: Select all

MadCap:conditions="ConditionFilename.ConditionName"

Excellent, Dave! THANX! So I don't have to explain.

Just one more detail: If an object (text, image, table, paragraph, ... ) has more than one condition, it looks like this:

Code: Select all

MadCap:conditions="ConditionFilename.ConditionName1,ConditionFilename.ConditionName2"

So I would consider it wise to search for ConditionFilename.ConditionName only - and not for MadCap:conditions="ConditionFilename.ConditionName".

[aharper]

Thanks for the explanation and the webinar. The find/replace makes good sense.

Adriana

[aharper]

Hi all,

One more question on this thread... Once I done the find-replace, can I go into my project organizer and delete the conditional code set (that has all the conditions I am no longer using)?

Thanks,
Adriana

[LTinker68]

Yes.

[aharper]

Thank you!

Adriana

[LTinker68]

If you're ever in doubt, make a backup of the entire project before deleting something like that. If it does turn out to be necessary down the road, then you have a working version that you can copy back into the project.