Dear Colleagues, Intuillion Ltd, the developer of DITAToo DITA CMS (http://www.ditatoo.com/) is happy to announce that DITAToo DITA CMS version 1.7 has been

Ok, looks good. I'll go back to my customer to do things properly, then make an initial commit and let you know. Look forward to work on this. Martn

A two-pass approach might make it easier. Just create the normal merge output into a variable and then process the contents of that variable in a mode to

Missed our #AdobeTCS webinar "Towards an Agile authoring methodology: learning from the Lean methodology"? RECORDING: http://adobe.ly/13xEqF4

The Center for Information-Development Management and Dr. JoAnn Hackos announce a call for participation in the upcoming Content Management Strategies/DITA

Are you overriding, somewhere, the attribute set for body__secondLevel? The default settings for the left margin, in commons-attr.xsl, are identical to the

bump

You can create "see" index entries as follows: Carassius auratus Goldfish I believe the index-see is what you

Couldn't get that to work. The border takes up the whole image block or figure block, and won't go just around the image. I'll have to look into it more.

Thanks for the tips! first solution, adapting the reltable to have tasks in both columns: I think all the references I'd seen so far had been to more complex

Hi, for this project we're using XEP (run by XMetaL 7) and OT 1.6 plus customization for creating PDF. Any advise on how to create 'see also' entrys in the

Hi, for this project we're using XEP (run by XMetaL 7) and OT 1.6 plus customization for creating PDF. Any advise on how to create 'see also' entrys in the

Wed May 15 10AM Pacific Time Register at: http://adobe.ly/11D6CTS (Will be recorded: link sent to registered attendees, even if you miss it) TWEET: 15May 10AM

Wed May 15 10AM Pacific Time Register at: http://adobe.ly/11D6CTS (Will be recorded: link sent to registered attendees, even if you miss it) TWEET: 15May 10AM

Hi, My client is upgrading from an old version of the OT (1.4.x) to 1.6.3. The original customization used @outputclass to get page- and column-breaks in PDF

Hi, My client is upgrading from an old version of the OT (1.4.x) to 1.6.3. The original customization used @outputclass to get page- and column-breaks in PDF

My bad, Franz-Josef. I said to put the new xsl:when within the xsl:when and I meant to say within the xsl:choose. So what you have below in your second code

My bad, Franz-Josef. I said to put the new xsl:when within the xsl:when and I meant to say within the xsl:choose. So what you have below in your second code

Would that it does. There is a Plus plugin that does that, but the D4P support for SVG does not (yet) do that. All D4P provides is a vocabulary domain module

Would that it does. There is a Plus plugin that does that, but the D4P support for SVG does not (yet) do that. All D4P provides is a vocabulary domain module