Conditional Build Tags in RoboHelp 9 PDF Review output?

It doesn't look like it's possible to exclude conditional text from the output for the new PDF review feature in RoboHelp 9. (From Review > Create PDF for Review.) Is this accurate?
Thank you,
-Jerod Allen

I'm sorry but I don't.
I suggest you submit a feature request that these requirements are added.
The more people who report a bug or request a feature, the more likely it is to be actioned. Please follow this link.
http://www.Adobe.com/cfusion/mmform/index.cfm?name=wishform&product=38
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

Similar Messages

I need help with the conditional build tag option RoboHelp 10

I need help with the conditional build tag option. I want to apply CBT to content in a topic. I looked at the Help topics and believed that I applied the feature correctly. Howver, it is not working as desired. In the 2nd sentence below I want the text highlighted in blue to only appear for the printed output and the text printed in purple to only appear for the .htm /online output. Please help.
There are common tasks used to manage the folders in the Navigator and the folders
in the BBS Folders Viewer Grid. For more information on these common tasks see Help
and Support in Success Enterprise. click the links below.

Hi there
Using tagging is a two part process.
Part One
You create and apply the tags to the information you wish to control.
Part Two
You create a Build Expression that is used when you generate your output. The Build Expression typically reads something like: NOT Tag1 (or whatever your tag name is)
Then when you generate and use the Build Expression, the information tagged is not included in the build.
Cheers... Rick

Conditional Build Tags Break on Chinese

Using RH7 (for word) on Win XP with Word 2007.
Generating HTMLHelp (chm only)
I am trying to take full advantage of Conditional Build Tag
to implement single source output. I have created my help files and
had the text translated into Chinese. I had the person doing the
translation simply add the Chinese text to the end of every English
paragraph. Then I created conditional build tags for English and
Chinese and applied the build tags the appropriate bodies of text.
If I generate "Chinese" it appears to work correctly, however
when I generate "English" I get the English text as well as a few
characters of Chinese at the end of each paragraph. The Chinese
characters that are displayed are seemingly random characters from
the Chinese text, but I can not find any rhyme or reason as to why
those particular characters are inserted.
Things I have done to troubleshoot...
- Explicitly excluded Chinese text from output (expression
was "NOT Chinese") (No Change)
- Added line breaks between English and Chinese (No Change.)
- Changed the font encoding ("SimSun" and "Arial Unicode MS")
(No Change)
I only tried this because the original Chinese text used
both fonts.
- Removed punctuation from Chinese text. (No Change)
I suspect there is a problem in RH7 for word when using
Chinese characters, but I bought the new version of RH because it
was supposed to be able to handle the Chinese characters. Well, it
turns out the only official support for Chinese is when using
RH-HTML (which was not mentioned when purchasing.) I have about 10
years of work done in RH for Word and am not excited to migrate to
HTML since some things don't transfer over when importing the
project to HTML, like the conditional build tags for example.
I have uploaded my doc, and an image that helps illustrate
the problem.
The Doc: Job_Console_ExtraTech.doc
The Image: Job_Console_ExtraTech.jpg
They are on the Support Portal FTP site...
Here is the information I used to get there...
https://www.adobe.com/support/crm_portal/ssi/ftpinfo.html
If anyone else has had success with conditional build tags in
RH7 for Word using Chinese text, I would really like to know if
there are any tricks or secrets that might help me get this working
correctly.
Thanks, J

I was a bit bummed when I found out I couldn't do the TOC
with conditionals either. But I made the help files intentionally
graphical so that the TOC, index, and searches are of less
importance. I am using the help files as a sort of graphical
trainer for an application suite.
It is disappointing that Adobe touted the multilingual
functionality of version 7 and this is what they meant, but it's
better than nothing.
I am just confused about how the Chinese characters are
showing up when the conditional build tags are clearly supposed to
be omitting them.
I think the next step is to embrace the HTML transition and
see if I have better luck there. The only daunting thing about that
is recreating all the conditional build tags.

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 for TOC in Robohelp X5

HI, Can we apply conditional build tags for TOC in robohelp
X5. I know this feature exists in robohelp X6 and x7. But as i am
working on x5, i want to know whether we can apply conditional
build tags for TOC. if yes, whats the process?

Hello again Abraham
Okay, so you have a book named Privileges. It is linked to a
topic named the same, right? And inside this book is a book named
Billing. I'm guessing your TOC structure would look like this:
* Privileges
**** Billing
******** Topic one
******** Topic two
You seem confused that the Privileges book doesn't disappear
when you exclude the Privileges topic. If that were to happen,
would you also want the Billing book and all topics inside to
disappear? Because if the Privileges book were to be removed,
anything and everything inside the book would also be removed.
Indeed to remove a book you need to coax all topics linked
inside (or inside sub books) to disappear too.
Cheers... Rick

RoboHelp applies Conditional Build Tags

Has anybody else had this problem?
It seems that RoboHelp (version 7) applied the Conditional
Build Tag on its own to various topics. Is there anything I can do
to prevent that in the future?

Salladep has now posted the same issue at http://forums.adobe.com/message/5177045
This is puzzling as it was a known issue in Rh8 until fixed and, as above, until these posts no one else has hit the problem with 8 or 9.
pmacbean has not replied so I don't know if what was suggested worked. Try what I have suggested above and let us know whether or not it works.
See www.grainge.org for RoboHelp and Authoring tips
@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.

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

Switching off conditional build tags

I now have quite a few conditional build tags in my RH7 project and it's getting a bit difficult to see what's what in my topics as they are covered in coloured hash lines. Is it possible to switch off the view of individual tags? For various jobs I need to see certain ones but not others.
Also, can I just check that I am using them right?
Our software has web and windows versions so I have a 'Web' tag and a 'Win' tag for where the content differs and I create different outputs for each.
Within the web version, we now have 2 different sets of customers who each need slightly different content and different names/logos etc. So I have created 'Customer X' and 'Customer Y' tags as well as 2 separate tables of contents. So in places, I have text which has 2 tags on it, 'Web' and 'Customer X' or 'Customer Y'.
Does this sound ridiculous? Is there a better way?
I know I could have used user defined variables for the company names but I would still need the cond build tags for the content so figured it would keep it simpler just to use tags.
Helen

Hi there
Sorry, no way to turn off individual tags. You can turn off the shading if you like.
Click View > Show > Conditional areas.
You might also consider submitting a wish form to ask for this type of functionality to be added to a future version.
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

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

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.

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 tag for folders

I was told this might be a new feature in coming updates but
have not seen an update in about 4 years (glad i didn't buy the
maintenance) - does anyone know a way to edit core files to enable
a folder to link a conditional build tag without code being
rewritten when you generate a new file set?
Thanks,
Steve

Hi Steve
Believe it or not, Adobe is hard at work on a new version of
RoboHelp to make an appearance some time next year. Maybe there
will be a feature that allows different ways of applying
conditional tagging. If you want to be sure this suggestion reaches
Adobe, you can click the link below and submit a Wish Form.
Click
here to visit the Wish Form
Note that if topics are excluded, they don't appear in the
output. So essentially, if you apply conditions to all topics
inside a folder and all are excluded via the build expression, that
folder is effectively moot.
Sincerely... Rick

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 cause RH9 AIRHelp crash

I have seen multiple posts about system crashes when using RoboHelp HTML and conditional build tags. Is anyone having the same problem using build tags with RH9 and AIR Help output? I have tried different combinations of build tags, a single build tag, as well as different project topics. All cause RoboHelp 9 to crash when generating AIR Help. Any suggestions? Is this a reported bug?

Hi there, this sounds somewhat like the issue I have with generating WebHelp, which I've posted here: http://forums.adobe.com/message/3813225#3813225
I can't seem to find other posts that relate to this, and you mentioned other posts at the start of yours. Can you reply with links? I would appreciate your time.
Thanks,
Michelle

Conditional Build Tags in RoboHelp 9 PDF Review output?

Similar Messages

Maybe you are looking for