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

Similar Messages

  • Conditional build tags applied to topic but it still displays in my TOC?

    I have applied topic level conditional build tags to topics.
    The corresponding books are still being displayed in my TOC. I
    checked the 4 topics and the condition is applied at the topic
    level. What am I missing here?

    Hi Renee
    If I recall correctly, you were also using Conditional
    tagging on almost everything in the TOC too.
    It's worth noting that:
    1. Sometimes the tagging will conflict and you won't get the
    results you were expecting
    2. Any topic inside a book should disappear if you are
    tagging at topic level. But the book will remain if at least one
    topic linked to a page inside the book wasn't excluded and remains.
    Cheers... Rick

  • 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 Ignored in Header

    Using RoboHelp HTML 8.
    When generating Microsoft HTML help, I have a conditional build tag which has been applied to the contents of the header and footer.
    Once I view the .chm, I still see the header and footer. There is a graphic in the header and text in the footer which are excluded, but the header and footer both have pattern backgrounds, which are images, that do not get excluded.
    Has anyone else seen this behavior, and/or know a workaround?
    Thanks!

    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 - Default Options Missing

    Greetings,
    In RHX6 when I right-click in a topic to apply a conditional
    build tag the default options Online and Print do not appear in the
    menu; the only option is New/Multiple.
    How do I get the default options back?
    Regards,

    This sounds like that at some time in the past the default
    ones have been deleted. Just add them again from the New/Multiple
    menu item.

  • 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.

  • 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.

  • In RH9, random conditional build tags appear within topic text

    I have assigned conditional build tags to text within a topic. After closing the topic and re-entering at a later time, other (additional) text now has the conditional build tag assigned as well. However, I did not assign the tags to those other sections of text.
    I do not have any trouble assigning a conditional build tag at the topic level. The issue only occurs when a tag has been assigned to text within a topic.

    There is another thread running on this. See http://forums.adobe.com/thread/58834?tstart=0
    I am locking this thread so that all replies go to the one above.
    See www.grainge.org for RoboHelp and Authoring tips
    @petergrainge

  • RH 11: Conditional Build tags applied: Content still showing up in search

    Hello. I am generating WebHelp using conditional build tags using RH 11.
    I have marked books in the TOC with a CBT of Not in 6.1.
    I generated help and excluded content marked with the CBT Not in 6.1.
    When the Web Help is generated, the books marked with the CBT  do not display in the TOC. However, if I do a search, topics that are under the books and therefore should not be included in the output have search results returned.
    Is there a scenario in which topics that have been excluded from the generated help would still show up in search?
    Your help is greatly appreciated.
    Jenny

    Hi Jenny
    Indeed there are a few reasons this may happen.
    First, simply excluding a topic or a book in the TOC simply makes sure that the TOC doesn't have a link pointing to the topic. Normally, I'll just tag the topic itself and ignore tagging the TOC. If a topic has been excluded, it won't appear in the TOC.
    In the WebHelp SSL recipe, click to expand the Content Categories section and look at the settings on the right. You might try ensuring the following option is enabled. It's named Exclude Unreferenced Topics from Output. As long as nothing else is linking to the topic, ensuring it is removed from the TOC *SHOULD* cause it to no longer be included.
    Cheers... Rick

  • 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

  • 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 Generated All Over Topics in RoboHelp 9 (HTML)

    I'm creating a help system and user manual using RoboHelp 9. The whole thing depends very heavily upon the conditional build tags. (Some parts are online and others are only for the print version of the manual.)
    Here's my problem: When I go back to topics I've already created, the tags are automatically generated in the wrong parts of the topic. The error lies in how RoboHelp is generating the HTML behind the scenes. (This was verified by one of our in-house developers who was thoroughly amused with RoboHelp's attempt at writing HTML.) I'm at my wits end. We have tried generating a new help system, only importing images from the old help system. It worked fine for awhile, but then the same problem cropped up. Is this some sort of bug? Is there a setting that I'm overlooking?
    I'm officially at my wits end. Help.

    Never seen what you're describing - when you tag text in a topic with a CBT, it stays stuck to it - there's no auto generation of CBTs. When you create your help, you specify what to show & what to hide in your SSL layout recipe.

  • Conditional Build Tags - Problems when generating content

    Hi,
    Just wanted to print 4 pages of a long help project so I added conditional build tags called 'ad-hoc' and created a Printed Doc SSL where ad-hoc was the conditional build value.
    When I generate the document I am getting everything still though. Am I being particularly thick today?
    I tried tagging everything 'online' and then adding the ad-hoc tag to the pages building the condition as 'online' AND 'ad-hoc' but then got nothing.
    Help appreciated as ever.
    Nick.
    @Tompsk on Twitter.

    I don't think the One Off Print tag is needed. If you apply Generic to all topics, then remove it from a few before generating online help with NOT GENERIC applied, you will get only the topics from which you removed the tag. No need to apply another one.
    If you wanted to print, then forget tags, just have a print layout where you only select those topics you want in.
    Print works the opposite way to online. Print you have to include, online you have to exclude.
    See www.grainge.org for RoboHelp and Authoring tips
    Follow me @petergrainge

  • 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.

Maybe you are looking for

  • New to internalization help me

    Hi there, i am new to this internalization issues, so please bare with me. I have an application(web based) that needs to be supported in 6 different languages. From what i could understand is there are some input methods which will help us to map th

  • Options for Seagate Backup Plus for Mac/Windows

    I have a new Mac-mini (my first Mac since my original Mac 128), and just got a 3TB Seagate Backup Plus.  It's so new, I haven't even read up on Time Macine though I assume that's the way to go. I originally had in mind partitioning the Seagate with o

  • NI Max Configurin​g Motion Bd Parameters - How to retrieve them

     I use my PXI-7344 Motion Card with Labview 7.1 and I configure the parameters such as the software limit thresholds in Ni Max.  When I am writing my Labview program and I am trying to see where the PXI-7344 SW Limits thresholds are set, I can not re

  • Appending to a zero length clob

    9.2.0.6 this works: var myClob clob begin :myClob := to_clob(' '); for rec in (select * from delme1) loop dbms_lob.append(:myClob ,to_clob(rec.ename || '\n')); end loop; end; but this does not var myClob clob begin :myClob := to_clob(''); for rec in

  • Boot camp (vista 64-bit home premium) not seeing both my CPUs

    so i just received my mac pro =) base config with 8800GT. i just installed windows vista 64-bit home premium via boot camp. everything is going fine, it's just when i open task manager, it only sees four cores instead of all eight. is it because i ha