Within a dita to text plugin, I'm splitting up a lenghty element using <?linebreak?> in the dita docs. The plugin then uses <xsl:template name="lbremain" match="processing-instruction()[name() = 'linebreak']"> to break it up at those processing instructions. What I'd like to do (...

Still hoping for a helping hand from someone on this one. Anyone got any thoughts? - G

Dan, Thanks for the reply. I have the identical code plus lines above that section that deal specifically with first and last... <fo:page-sequence-master master-name="{$master-name}"> <fo:repeatable-page-master-alternatives> <xsl:if test="$first"> <fo:conditional-page-master-refe...

I need different footers for the FIRST and LAST page of my body in an existing custom PDF DITA-OT plugin. I have: <xsl:template name="insertBodyFirstFooter"> <fo:static-content flow-name="first-body-footer"> <fo:block xsl:use-attribute-sets="__body__odd__footer" text-al...

Radu, I think you've got me on the right path. With a few tweaks I have it breaking up the text so I can handle the first segment separately from those that follow. Now I need to figure out a way to indent any part of each segment that wraps to the next line, but you've got me moving forward. Thanks...

Radu - Thanks for your reply. Unfortunately, unless I'm missing some nuance or piece you expected me to know to fill in, your code simply selects the entire msgText text node as a single entity in essentially the same way <xsl:template match="*[contains(@class, ' msg/msgText ')]"> does. In...

I have a DITA document for **TEXT** output that contains msg elements like this: <msg> <msgId>
 <msgNumber>1234567</msgNumber>
 </msgId> <msgText>The variations of this message are explained below. <?linebreak?> -option one. <?linebreak?> -option two. </msgText> </msg> I need the output of msgText t...

I'm trying to create a solution to some of our writers using a space or simply not populating <sep> elements. I thought I could just customize Content Completion Assistant so that <sep> elements would be automatically created with a non-breaking space inside them (&#160;). Unfortunately, it look...