Hi, Maybe you can attach a small trim-down DITA project exemplifying the problem. In this way we can also see how the task title refers to the defined key. Also tell us what DITA Open Toolkit version

#conditional-processing #reuse

You've defined keydefs that have <topicmeta>, which is not valid inside a topic title. -m

#conditional-processing #reuse

My task title will not display the product name for each product in both the dita and pdf. The task title is the same product name for all products. My keydefs are defined in the submap. I have attach

#conditional-processing #reuse

Hi Ed, If you look inside a DITA OT bundled with Oxygen, it has in the "plugins" folder a plugin named "com.oxygenxml.dost.patches". That plugin depends very much on the DITA OT version, if installed

#conditional-processing #DITA-OT #branch-filtering #specialization

Hi Radu, I think I might have found the culprit: I tried to generate output using DITA-OT 3.5.2. Our customized plugins rely on Oxygen plugins, so I naturally copied Oxygen plugins from their installa

#conditional-processing #DITA-OT #branch-filtering #specialization

Hi Ed, Can you give a list with all the custom plugins you installed in DITA OT 3.4.1? Also just to make sure, you did not copy the DITA OT 3.4.1 installation over the older 2.x installation, right? B

#conditional-processing #DITA-OT #branch-filtering #specialization

I use the standard procedure described here. The exact command is (I wont list the complete directories since they’re irrelevant I think): dita --input=file.ditamap --output=desktop\folder --format=ht

#conditional-processing #DITA-OT #branch-filtering #specialization

Hi Ed, DITA OT 3.5.2 comes with a very new Saxon XSLT processor in its "lib" folder "Saxon-HE-9.9.1-4.jar". You seem to be running the publishing with an older Saxon JAR library. How exactly do you st

#conditional-processing #DITA-OT #branch-filtering #specialization

Hi everyone, we’re trying to upgrade our dita-ot from 2.5.4 to the newest version. I copied our custom plugins to the new dita-ot directory and integrated them using the dita install-command. Now, eve

#conditional-processing #DITA-OT #branch-filtering #specialization

Hi Bella, Since you’re using DITAToo CCMS, you might check out the configuration database add on. This has been designed for managing complex conditions in DITA content. Contact your DITAToo vendor to

#conditional-processing

I haven’t done it yet, but have you looked into groups? http://docs.oasis-open.org/dita/dita/v1.3/errata02/os/complete/part3-all-inclusive/archSpec/base/usage-of-conditional-processing-attributes.html

#conditional-processing

We have some complex conditionalization, too, and these are some techniques I’ve used. For ditavals: · “Exclude” all profiling attributes by default: <prop action="exclude"/> · “Include” all @otherpro

#conditional-processing

Hi, The conditional attributes are very complex for our documentation because our product is highly customer configurable. Our conditions have complex combinations of AND, OR, and NOT, for example, (A

#conditional-processing

Thanks. Exactly what I was looking for. Appreciate it. John

#conditional-processing #hazard-statements

Hi John You could control the output of ISO or ANSI icons via the map. I use this technique in my PDF plugin to control for instance the layout (A4/US). First you need to define a variable in roots-pr

#conditional-processing #hazard-statements

Hi Radu, Defining keyscopes and keys for each topic did the trick. Thank you for the tip. Kind regards, Pieterjan

#conditional-processing

Hi Pieterjan, It probably depends on the order in which the DITA OT engine does the branch filtering and the conref resolution. From what I looked it seems to first do the filtering and then the conre

#conditional-processing

Hi, I am currently trying to figure out the branch filtering mechanism, but I am lost when it comes to branch filtering and reused content. Is it possible to do branch filtering on reused content? I w

#conditional-processing

Because the safety alert symbol is generated by the note tag and not part of content in the topic. <Note type='warning'> Automatically renders the exclamation and 'warning' text in standard Dita. Seem

#conditional-processing #hazard-statements

If you can use DITAVAL for the hazard icon, why wouldn't that work for the safety alert symbol as well? As long as you don't have to mix ANSI and ISO in the same book, you could put the right image in

#conditional-processing #hazard-statements