DITA and XMetaL Discussion
IF July 10, 2013 at 11:23 pm
Modifying topic.title attribute based on outputclass – PDF outputJuly 10, 2013 at 11:23 pmParticipants 2Replies 3Last Activity 9 years, 2 months ago
I want to change the background color of topic titles based on the value of the outputclass attribute.
From what I can tell, I can do that with a “choose” statement. For example, I am able to modify the “p” attribute set as described here ( http://tech.groups.yahoo.com/group/dita-users/message/32117 ). Thanks Severin! I make this modification in the “…. DITA_OTpluginsxmfoCustomizationfoattrscustom.xsl” file. Everything works fine.
However, when I try the same syntax on the “topic.title” attribute set, I see a Bad attribute : Could not parse attribute value ” warning in the output log and the PDF file is not modified.
Is there a reason the topic.title attribute set behaves differently than the p attribute set with “choose” statements (other than some stupid error on my part)?
Using XMetal 8, XMetal Enhanded PDF via RenderX XEP ouput.
Isabelleseverin.foreman July 11, 2013 at 1:26 am
Reply to: Modifying topic.title attribute based on outputclass – PDF outputJuly 11, 2013 at 1:26 am
Did you try to update the attribute-set in the file specified in this post?
SeverinIF July 11, 2013 at 4:51 pm
Reply to: Modifying topic.title attribute based on outputclass – PDF outputJuly 11, 2013 at 4:51 pm
Yes – I tried the same thing in the “….DITA_OTpluginsxmfoCustomizationfoattrsxm-cfgcommons-attr.xsl” file and saw the same behavior I described above.
I just tried other attribute sets this morning:
I get the “bad attribute” error when I use a “choose” statement with the topic.title and topic.topic.title attributes.
I do not get the error when I use a choose statement with the topic, p, or fig.title attributes.
IsabelleIF July 12, 2013 at 10:00 pm
Reply to: Modifying topic.title attribute based on outputclass – PDF outputJuly 12, 2013 at 10:00 pm
Could this be a clue?
Updates to the PDF processor in DITA-OT 1.5
•attr-set-reflection.xsl now actually works. It used to be that some attribute sets were “fakes” – topic.topic.title for example couldn't have
or in it. Now all attributes sets are “real” – they all support normal xsl behavior
- You must be logged in to reply to this topic.