Conditional Build Tags and Baggage Files

Good afternoon
I have a project where I need to produce two outputs - one
for the internet and one for our intranet. I have applied
conditional build tags to the topics that I don't want displayed on
the internet however, the topics with baggage files attached still
show up - I can't figure out how to apply a cbt to these files. Can
someone help me please?
Thanks

HI Leapy.
OK I think I have got to the reason why your CBTs are being
included. If you have them at the topic level, they are exlcuded.
If you have them at the topic contents level they are included. Do
a right click on the CBT in the project tab and select the
"Properties" popup menu item. You will probably find that the tags
show up at content level. If you change these to be at topic level
you should be OK.
BTW if you are using merged webhelp there is a known problem
with links failing. Peter Grainge has covered this, and the
workaround, very well at his site. Click
here
for more details.

Similar Messages

Can I use conditional build tags in CSS files?

I am using RoboHelp X5.0.2 and building CHM files.
I use conditional build tags to output different Help files
for the different products we have that all have similarities.
In the past I have setup the CSS file to show headers, links
etc in the color scheme we use to keep the look and feel of our
branding. One of the new products uses a different branding color
scheme.
I was wondering if there is a way I can use conditional build
tags in the CSS file so that when I build one type of help it uses
header in one color and when I build another help it uses a
different header color. Does anyone know how to do this? If it is
not possible in my current version, is it possible in the latest
version of Robohelp?

[WORKAROUND ALERT IN X502]
For .chm output, you could:
1. In the Topics pane, select all the topics (click on one
topic and press Ctrl+A).
2. Right click in the highlighted area and select Properties.
3. In the Appearance tab, select the different style sheet.
4. Click Save.
5. Generate the .chm file.
6. (optional) Repeat steps 1-4 to revert to previous style
sheet setting.
Good luck,
Leon

Conditional build tags and numbered lists

Is there a way to get numbered lists to automatically update
when conditional tags are used? For example, only step 6 of a 10
step list is needed for 1 of 4 products. However, when I preview
the content for the 3 of 4 products that do not require that step,
the list is numbered 1, 2, 3, 4, 5, 7, etc.

Hi darwinsfolly.
Have you checked the Trusecode to see if there is anything
amiss there? Perhaps a nested <ol start=x> tag?

Topic and content level conditional build tags

What is the difference between a topic level and a content
level conditional build tag? Why would you select one over the
other? How do you select one over the other.

First let me point out that the same conditional build tag
can be applied at either the topic level or the content level. It
sounds like you may be thinking that you have to create a tag as
for either the content or topic level.
Apply a tag at the topic level when you want the entire topic
excluded from a certain output. Do this by right-clicking on a
topic in your Project Manager, going to Apply Conditional Build
Tag, and selecting the tag.
Apply a tag at the content level (text, images) when you want
the topic to be included but want specific content to be excluded
from a certain output. Apply a tag at this level by selecting the
text and/or images that you want to apply the tag to,
right-clicking, going to Apply Conditional Build Tag, and picking
the tag.
Note that you wouldn't use a tag at the topic level on a
topic where you have used that same tag at the content level, and
vice versa.
Generally, the idea of build tags is to set an output to
exclude certain tags, but you can also set outputs to include tags
instead, which then excludes all other tags.
--Ben

Conditional build tags/expressions in the TOC

Hello all,
I've run into another issue with my conversion, this time with Conditional build tags and expressions.
All seems to be fine in my topics, but not in my TOC.
Some of my topic titles have words that have conditional text applied in the source FrameMaker document.
These topic titles also appear in the TOC that's automatically generated when I link my Frame book to Robohelp.
I set the conditional build expression in the Webhelp settings dialog and then Save and Generate.
These topic titles appear to pick up the correct conditional build expression in the topics themselves, but the TOC heading shows multiple conditions (including the condition I've set to "Exclude").
So, for example, if my topic title is
"Conventions in this documentonline help"
WHERE
document > should appear in PDF only
and
online help > should appear in Webhelp only
I can get the Webhelp topic to use the title "Conventions in this online help"
but the corresponding TOC heading looks like this:
"Conventions in this documentonline help"
Any ideas?
Thanks.
Sue

Conditional build tags are not imported to TOC from FrameMaker content. However, one can follow another approach to achieve this. One can manage the Conditional build expression in FrameMaker itself and import the filterted content in RoboHelp. Inorder to achieve this, set the conditional build expression in FrameMaker. Turn on the setting in RoboHelp to "Apply FrameMaker Conditional Text Build Expression". [File->Project Settings->Import->Edit(FrameMaker Settings)->Other Settings]
This way RoboHelp will import only the filtered content with Conditional Build Tags resolved as per the expression applied in FrameMaker.
Mayank

Conditional Build Tags...weird behavior?

If I apply a conditional build tag to a topic from the TOC
tab, the topic gets included in the output even if I have specified
that tag to be excluded.
However, if I apply the same conditional build tag to a topic
from the Project tab, then the topic gets excluded (as expected)
from the output because I have specified that tag to be excluded.
Is this inconsistency in behavior by design? I looked at the
RoboHelp Help, and it appears there is nothing wrong with adding
conditional build tags to topics from the TOC tab.
Can someone shed light on this? I am using Adobe RoboHelp
HTML 6, Build 099.
Thanks,
K
P.S.: It appears RoboHelp is completely ignoring the
conditional build tags that I am adding to topics from the TOC tab.
If I see these tagged topics from the Project tab or the Topics
tab, there is no color shading for these topics. The color shading
for the topics shows only if I tag the topics from the Project Tab
or the Topics tab.

Here's a copy-paste from the RH Help...It didn't explain
things the way you did. :-(
Applying conditional build tags to Table of Contents
Use conditional build tags to design and create multiple
versions of your project from a single set of source files. After
creating the conditional build tag, you can apply it to both books
and pages in the TOC for maximum control over the final results.
From the TOC view, you can apply conditional build tags to Topics
also. When you generate a project, you can define conditional build
expressions to include or exclude the book or page in the TOC, from
the output.
Show Me
Use this procedure to apply conditional build tags to books
and pages in the TOC. When you exclude such a tag from your output,
the book or page in the TOC, is not included in the output.
To apply a conditional build tag to a book or page in the
TOC:
Option 1:
Create the conditional build tag.
Click the TOC tab to view the Topic list.
Select a book or page to which you want to apply a
conditional build tag.
Right-click and select Apply Conditional Build Tag, and
choose the Tag you want to apply. The tag is applied to the
selected book or page.
When you generate the project, you can define conditional
build expressions to include or exclude the tagged books or pages
in the TOC, from the output. (A TOC to which a tag has not been
applied, will be included in the output.)
Option 2:
Create the conditional build tag.
Click the TOC tab to view the Topic list.
Select the book or page to which you want to apply a
conditional build tag.
From the Format menu, select Apply Conditional Build Tag, and
then choose a tag. The conditional build tag is applied to the
selected book or page in the TOC.
When you generate the project, you can define conditional
build expressions to include or exclude tagged books or pages in
the TOC, from the output. (A TOC to which a tag has not been
applied, will be included in the output.)
To apply multiple tags:
From the Format menu, select Apply Conditional Build Tag, and
choose New/Multiple. The Conditional Build Tag dialog box appears.
Click Check All to apply all the tags, or select specific
tags to apply to the book or page in the TOC.
Click OK.
If your project is under version control, these steps may
include more options. Click here for more information.
Tips:
You can also apply conditional build tags to topics, topic
content, folders, and Index.
To verify the tags applied to topics, topic areas, TOC, and
Index, or rename a tag, or change the color of a tag, click the
Project tab, expand the Conditional Build Tags folder, and
double-click the tag. You can make the desired changes in the
Conditional Build Tag Properties dialog box.
Ensure that you remove textual references to the excluded
book or page, such as text links, which refer to the tagged book or
page in the TOC. (Hotspots are not active for excluded topics.)
If you generate Printed Documentation, TOC with Conditional
Build tags are not excluded from printing.

Conditional Build Tags lost converting from X5

When I did a trial conversion of an existing RH Office X5 project to RH8 it lost all of the Conditional Build Tags. As the X5 project was made up of 29 Word documents with many tags it would be a big job to go through all of the topics and redo the work. The company for which I work supplies multiple software products using common forms and the wording for each product is different, therefore when I compile help for each product the Conditional Build Tags are very important. Is there any way that the tags could be retained when converting to RH8.

Thanks for the suggestion.
I have created all of the Conditional Build Tags and when I look at the
properties it lists the Topics that they are used in. Howver, when I look at
the properties of the individual topics the check boxes are all clear for
all Conditional Build Tags.
I have also noticed that none of the Content level conditionality has been
preserved during the upgrade. This is a major problem as it would take a
long time to go through all of the documents and re-apply the tags to text
and graphics. If I do upgrade is this something that I would have to do
manually?
I have upgraded to 8.0.2
Regards
Tony Champ

Conditional Build Tags for Text Blocks Applied to Entire File

RoboHelp 8.0.0.203. This post also deals with conditional build tags, but in this case the conditional build tags have been associated with sections of text and text blocks within a topic. The design was implemented originally in RH7 and the project has since been updated with RH8.
For example, you could have three blocks: Purpose, Procedure, Tips, and a Notes block. They are disabled by applying blocks Tag A, Tag B, Tag C, and Tag D respectively. If Tag A is applied to the Purpose, it is cross-hatched in the design window and does not appear upon generation.
The problem is that tags that are seemingly unrelated to blocks, such as Tag C and Tag D, are spontaneously applied to those blocks -- by the software. In fact, they would be spontaneously applied to all of the blocks and text in a some of the files (for no apparent reason), cross-hatching every element and every block of text in the file. When we unapply the tag and store the file, when we re-open the file, the tag is mysteriously re-applied to all the blocks -- again by the software.
Has anyone seen this type of problem in RH8?
Below is further detail about the problem
An example of how tags shold be applied involves a block involving three banners
<div class="banner">
     <?rh-udv_start name="Banner A" ?>BANNER A NAME<?rh-udv_end ?>
     <?rh-udv_start name="Banner B" ?>BANNER A NAME<?rh-udv_end ?>
     <?rh-udv_start name="Banner C" ?>BANNER A NAME<?rh-udv_end ?>
</div>
Under normal conditions, an associated tag would be applied to "unselect" two classifications, thus selecting the third by default. This is done by highlighting the associated banner, right-clicking and selected the "UnselectedBanner" tag, Below, banner C is selected by unselecting Banners A and B. T
<div class="banner">
     <?rh-cbt_start condition="UnselectedBanner"?>
     <?rh-udv_start name="Banner A" ?>BANNER A NAME<?rh-udv_end ?><?rh-cbt_end ?>
     <?rh-cbt_start condition="UnselectedBanner"?>
     <?rh-udv_start name="Banner B" ?>BANNER A NAME<?rh-cbt_end ?><?rh-udv_end ?>
     <?rh-udv_start name="Banner C" ?>BANNER A NAME<?rh-udv_end ?>
</div>
The <?rh-cbt_start condition="UnselectedBanner"?> indicates that the section is de-selected.
Note, that the "<?rh-cbt_end ?><?rh-udv_end ?>" are in opposite order in the example (but that's how it appears in the file).
In the cases where this problme occurs, we the html riddled with "Tag D" and "Tag C" condition tags for all the elements.
<?rh-cbt_start condition="Tag C, Tag D"?><div .......     </div><?rh-cbt_end ?>
I cannot attach any files because these files are on a classified system.
Thank you much.

Hi Tammy
It will also be helpful if everyone that encounters the issue reports as a bug. It's like a voting system. The more reports of bugs that are seen, the more weight is given to the priority. This directly translates to the fix being posted sooner rather than later.
So even though the bug has been "reported", you and others should take a moment and report as well!
Cheers... Rick
Helpful and Handy Links
RoboHelp Wish Form/Bug Reporting Form
Begin learning RoboHelp HTML 7 or 8 within the day - $24.95!
Adobe Certified RoboHelp HTML Training
SorcerStone Blog
RoboHelp eBooks

Conditional build tags with character styles and ignored text

RoboHelp HTML v8.0.2.208
Windows XP Professional Version 2002 Service Pack 3 with 2 GB of RAM
Output: WebHelp and HTML Help
I have recently moved my projects from RH HTML X5 to RH HTML 8 and this is when the following problem appeared. I use lots of conditional build tags within the help projects. Some of these tags are for my own use for reference and I combine these with character styles containing a coloured background (highlight) so that they show up in the WebHelp or HTML Help output (e.g. text to identify the software version that the field/feature/text was added, reminders to check details, insertion of bug ID numbers, design document names, etc.). These areas of text are stripped out of the final build for customers by using a conditional build expression.
What I have noticed is that if a paragraph contains text with a conditional build tag applied AND that tagged text has a character style applied AND an unknown word within the conditional build tag is ignored (with the HTML tag <?rh-ignored text="word_to_be_ignored" ?>), saving the topic, closing it, then re-opening it shows that the conditional build text has stretched to the next conditional build tag, or to the end of the topic if there aren’t any other conditional build tags. This also happens by switching from Design View to HTML View. Note that this doesn’t happen if Ignore All is applied to the unknown word.
This doesn’t just apply to projects converted from RH X5. I created a new test project in RH8 and the same behaviour was observed. Similar behaviour occurred very occasionally in RH X5 but that seemed to be down to HTML tags being nested incorrectly.
The largest project contains around 1200 topics and with many hundreds of conditional build text areas this now causes a problem. I’ll probably have to locate every ignored word in an area of conditional text within each project, set it to Ignore All and then manually remove and re-apply the conditional build tags, unless someone can come up with something clever. Can anyone else replicate this and should it be logged as a bug?

Hi Daggins,
Thanks - that is good info to have. But as we all agree, that does take away from the point of single-sourcing.
You aren't misunderstsanding exactly... I am doing all my conditional tagging in FM and it works like a charm in terms of the PDFs that I generate from FM, and even the conditionally tagged text in RH shows/hides correctly. The issue is I am also importing my index and TOC from FM... and even if I have an entire file in FM tagged as conditional (all the text is tagged as conditional, I don't know if you can tag a file as conditional), the file name as a heading it still appears in the RH TOC. There is no text... but in my view it shouldn't appear in the TOC either (it looks like just a broken link when I generate my online help) - this is not ideal.

RH6 crashes with th and conditional build tags

Hello together,
The attached code worked fine with RH X5, but leads to a
crash with X6. To fix, you have to replace the <th> by
<td>, but it is not too easy to find the topic within a
project. The fix is quite easy, but it is hard to find in a big
project.
This happens, when the conditional build tag is used.
Thanks and best regards,
Katrin Lusser

Hello Peter,
My wife created the topic with X3 or X5.
She just tried again with X6 and after several changes (set
heading, insert, delete, etc.) she had the same constellation.
Unfortunately, until now, she could not find out the exact way to
reproduce. But it is definitely possible. We will post here, when
we find out, how to do it.
Best regards,
Michael

Conditional Build tags affecting formatting and merging hyperlinks

I'm working in RH6 on a number of projects. In all of them I use a specific caption box/format combination for tips and notes. I also use a conditional build tag so I can generate a 'lite' versions of full help, suitable for printing. I note that on occasions, when I apply the build tag, I lose the formatting on the text - or the entire formatting of the text is applied where I don't want it applied.
Wrose, still, I find that applying a build tag to a list of hyperlinks can merge the link addresses so they all point to the same area, which is pretty disastrous.
Is this a bug Adobe know about? Is it fixed in 7 or 8?
Any advice appreciated.
Robin

Hi again
Well, I wasn't suggesting it wasn't a bug.
I suppose it's quite likely that something is getting munged. Actually, I think that's rather obvious as it's happening to you.
I think perhaps the editor is becoming confused. I believe the way these things are handled is by using some specially formatted span tags to apply the CBTs.
By the way, these new forums now support screen captures. So we no longer have to resort to a reasonable facsimile using only text.
Sorry I don't really have a workaround to offer here. At this point I'm as puzzled as you are.
Cheers... Rick
Click here for Adobe Authorized Captivate and RoboHelp HTML Training
Click here for the SorcerStone Blog
Click here for RoboHelp and Captivate eBooks

In the paragraph after a conditional build tag, an inline image gets wrapped in a div tag

Hi,
TCS5, so FM 12 and RH11. I have successfully applied some conditional build tags by turning off the apply conditional build tag setting and using the Conditional Build Expression in the WebHelp properties instead.
In RoboHelp, everything looks correct. I generate WebHelp and suddenly, a div tag is wrapped around the inline image in the paragraph that followed the text marked conditional.
This did not happen with TCS 4 (FM11, RH10). I am not sure why this div tag is applied only when I generate the help. Any thoughts on what to check?
Lauren

Hi lauren,
I tried to replicate the above mentioned issue, but did not get the <div> around the image in Webhelp output. Would it be possible for you to provide more information on this:
At what point does the <div> start appearing around the image, as soon as the CBT expression is applied?
If yes, what is the expression?
What happens when expression is set to None again and individual CBT is under application
Is there a spacing or the CBT text just follows the inline image?
Please send us a sample file for the same, if possible. Thanks!
Amit

The extra space created due to Conditional Build Tags

Hello,
I am authoring a online help file, for a web application. As different content is needed for the 4 different roles of the user, I have used Single Sourcing option and made use of conditional build tags for the content that is not common among the different roles. I even have images which are difffernt for the differnt roles. I have used conditional build tags for these too. The problem is that, extra space appears in place of the images which are not applicable to build I am publishing. Is there any workaround other than modifying the HTML files to remove the extra space added?
Regards,
Deepti Korwar

hi Deepti,
I have seen this issue on multi-level lists (in RH9) when using soft returns (Shift-Enter) within the lists.
An extra space is added before images marked with CBTs. But this only caused problems in print.
Are you seeing this space on all outputs or just print?
Can you paste a code snippet from one of the offending list?
Perhaps you can get round this by opening up the HTML tab and carefully examining and perhaps moving the CBTs.
e.g. <?rh-cbt_start condition="xyz" ?><img src="xyz" > <?rh-cbt_end ?></p><?rh-list_end ?>
Will be helpful to see the code.
thanks
Craig

Text coded with conditional build tags still showing up in TOC even if tag is "excluded"

I am using TCS2, Windows XP.
After creating a book in FM and coding with conditional build tags, I imported into RH. When I generate, I have the output tag set:
NOT NoOUtput AND NOT Internal AND NOT Print - I want to generate my External, Online Help webhelp. And it works like a charm. Except that:
In the TOC, I can still see headings for things that are "internal" - when I click on it, they don't go anywhere... but I don't want them to appear in the TOC!!
It seems to be excluded from the index and the search. I am sure I am just missing a step or something...
In looking through the forums I found this... http://forums.adobe.com/message/751847#751847 -- I don't know if it is still applicable since it seems to be referring to RH6 (which is a bit away from RH 8 that I am using)...
Any help is appreciated!
TIA,
Adriana

Hi Daggins,
Thanks - that is good info to have. But as we all agree, that does take away from the point of single-sourcing.
You aren't misunderstsanding exactly... I am doing all my conditional tagging in FM and it works like a charm in terms of the PDFs that I generate from FM, and even the conditionally tagged text in RH shows/hides correctly. The issue is I am also importing my index and TOC from FM... and even if I have an entire file in FM tagged as conditional (all the text is tagged as conditional, I don't know if you can tag a file as conditional), the file name as a heading it still appears in the RH TOC. There is no text... but in my view it shouldn't appear in the TOC either (it looks like just a broken link when I generate my online help) - this is not ideal.

How to apply conditional build tags to the topic title that is displayed in Search tab of CHM?

I have the project in which 2 different words are used to reffer to one objects (this word/term depends on the customer). All other information related to functionality, steps, etc. are common. So:
In the help content (body of the files), I created 2 conditional build tags (CBT) for these terms.
In TOC, if topic title contains the term, I created 2 different topics reffered to the single topic file, but the title of the topic shows correct term (depends on CBT).
File names of this topics contain only term1.
The problem occurs when I generate CHM for CBT2 and search for the term1 (marked with CBT1) using the Search tab. All occurrencies where term1 presence in the file name, appear in the found results.
How can I resolve the issue?
These topics must be found by search (that's why "Exclude from search" option is not a decision).

Ahhh, you are correct. I believe it was Version 10 introduced that.
So here's what I'd suggest. Even though you are unable to use a variable in a Topic Title, it can still be used in other places such as the TOC, the Index and in the Topic content. So I'd still recommend that you declare and use a variable for those items. Just to simplify things.
As for any topics that have the term in the title, you could create two topics. One with the term one way and the other with the term the opposite way. Then use a Conditional Build Tag to exclude and remove the one that shouldn't be found.
This may cause you a bit of a maintenance issue by having the same topic content in more than one place. (one for each topic)
So to overcome that, you would be able to add the main body information to a topic and use an Inline Frame in the two topics that would then simply be shells with appropriate Topic Titles. Either that or declare a snippet and use the snippet in both topics. Put the main part in the snippet.
Cheers... Rick

Conditional Build Tags and Baggage Files

Similar Messages

Maybe you are looking for