Hi, we've discovered that file names (e.g. file names of images used in the RH project) are included as suggestions in the Responsive HTML5 output of our project:  Is there a way to turn this off? Having file names as the first suggestions makes the search all but unusable. Especially since the suggestions also include thumbnail images that are generated by RoboHelp if a thumbnail class is applied to an image.   Thank you for your help. Cheers, Birgit ... View more

Hi, another question for printed documentation which drives me crazy. In my RH 2017 Classic project, I have multiple tables and table styles: * By default and in the table style "celum", the table should have all borders. * In the table style "no-border", the table should have no borders.   I am using a dedicated css file for the print output (so no Word style mapping) and everything else works fine, but no matter which table style is applied to a table in my project, the borders are never present in the Word output, even though I am explicitly (and with !important) specifying the borders for all relevant table styles as well as the default table in the print.css: table { table-layout: auto ! important ; width: 100%; font-family: "Open Sans", sans-serif ! important; border: 1px solid #585858; } table td { vertical-align: top ! important ; word-break: break-word !important; padding: 5px ! important ; border: 1px solid #585858; } table th { vertical-align: middle ! important ; word-break: break-word !important; padding: 5px !important; border: 1px solid #585858; } table.celum { border: 1px solid #585858 ! important ; border-collapse: collapse !important; } table.celum th { border: 1px solid #585858 ! important ; background-color: #0079db; }   An example: Here is a table in the RH project: The table has the table style "celum" applied: <table class="celum" style="border-collapse: separate;" border="1"> <col style="width: 6.037%;" /> <col style="width: 32.991%;" /> <col style="width: 60.972%;" /> <tr class="hrow"> <td><p>Button</p></td> <td><p>Name</p></td> <td><p>Function</p></td> </tr> ... </table> But in the Word output, the table looks as follows:   What am I doing wrong, why is the border not applied to any of my tables in the printed documentation output? Any help is much appreciated.   Cheers, faeneth ... View more

Hi, I'm trying to generate a printed documentation from my RoboHelp 2019 Classic project, which has some complex conditional tagging applied. I can't seem to get the conditional expression right so only the content that I actually want is included.   These are the available build tags in my project: Topic-level tags (identify which of our product a whole topic applies to): topic_dam topic_nova topic_cma Content-level tags (identify content for each product in a topic which has content for multiple products) content_dam content_nova content_cma Topic/Content-level tags for user-level user_casualUsers user_powerUsers Content-level tags for the medium (for layout reasons I partly have two versions of images/text) medium_online medium_print Content-level tags for stuff that needs to be excluded: exclude   What I'm having trouble with is finding the right combination so I can export the printed documentation for a.) only one of the products (dam, nova or cma), b.) with only the "medium_print" stuff included and none of the "medium_online" stuff (regardless of other tags that are applied), c.) with all powerUsers and casualUsers stuff included (for the right product) and d.) without any of the "exclude" stuff (regardless of other tags that are applied).   The closest I have gotten so far is the following expression (for the "nova" product variant): topic_nova AND NOT exclude AND NOT medium_online OR content_nova AND NOT exclude AND NOT medium_online OR medium_print AND NOT exclude OR user_powerUsers AND NOT topic_cma AND NOT topic_dam AND NOT content_cma AND NOT content_dam   However, this ALSO includes all the stuff that only has the "exclude" tag applies (and no other tags on content-level). How do I automatically exclude the "exclude" content without worrying about other tags that content may have? How do I do the same for "medium_online"?   For my online output with dynamic content filter, I use the following output/filter settings, which pretty much sum up what I also want to accomplish for the product-specific print output: Conditional build tag: NOT exclude AND NOT medium_print --> The print and exclude stuff doesn't even get generated. Filter-options for group "User":  user_casualUsers --> Show only casual user content user_powerUsers --> Show only power user content user_casualUsers OR user_powerUsers --> Show content for both user types Filter-options for group "Application": topic_dam AND NOT content_cma AND NOT content_nova OR content_dam --> Show only stuff for the "dam" product topic_nova AND NOT content_cma AND NOT content_dam OR content_nova --> Show only stuff for the "nova" product topic_cma AND NOT content_dam AND NOT content_nova OR content_cma --> Show only stuff for the "cma" product With this filter-setup, when I go for the "casual OR power user" option and any of the product-specific filter options in combination, it shows me exactly what I want.   How do I reproduce this as a single conditional expression (for printed output, I can only apply a single conditional expression, so it needs to cover all the bases)?   Any help is much appreciated.   Cheers, Faeneth ... View more

I have created a stylesheet for generating the "Printed Documentation" output for our RoboHelp 2019 Classic project. In the stylesheet, I give explicit absolute sizes (in cm and px) to the image styles. However, these image styles are not applied to images in the project when the Word document is generated. Instead, all images are either 100% of their size or 100% of the page's width.    Here is the CSS for a particular image which is displayed small in the RoboHelp project and HTML5 output: img.thumb_left_small { width: 120px ! important ; height: auto ! important ; float: left ! important ; margin-right: 25px; } The specified width of 120px (I also tried 3 cm) is not translated to the Word document when generating Printed Documentation:   How can I give large images in my project a size that is smaller than 100% of the page width in the generated Word document? Any help is much appreciated 🙂   Thanks, Birgit ... View more

Hi, for our help system https://help.celum.com we generate the output from 4 different projects - a dedicated project for each of our product lines and a parent project which merges all of them together and contains some marketing intro topics. If I try to generate the "Printed documentation" output for the merged project, it only includes the marketing topics that are actually part of the merged parent project. All the child project topics are not included. Is there any way to generate a single PDF from a merged project that has 1 parent and multiple child projects? Or is it simply not possible? Do I have to generate a Word document of each child project and then merge them all together before converting to PDF manually?   We are using Adobe RoboHelp 2019 Classic (have not switched to the Reimagined UI yet).  Any help would be greatly appreciated.   Cheers, Birgit ... View more

Hi, I'm using RoboHelp 2017 Update 2 for our new product documentation, which will be an HTML5  help with a customized Indigo layout. The product has two different GUIs, one for casual users and one for more experienced users and administrators. The help content between the two GUIs can be switched with dynamic content filters. The two GUIs are constructed and designed completely differently and I think it would be great to have a dedicated glossary for each GUI. Now I'm looking for a way to switch the shown glossary depending on which of the content filters is activated. Is this even possible? The glossary files don't seem to have the "Apply conditional tag" context menu entry. Alternatively, can I somehow apply a conditional tag to specific glossary entries (terms and definitions) in the same glossary file? Otherwise people who can only see the casual GUI will be bogged down by complex terms in the glossary which have nothing to do with what they can see, and advanced GUI users will have the opposite problem. Thanks for any helpful hints Cheers, Birgit ... View more