Editor variable for profile attribute?

Posts: 2
Joined: Mon Jan 21, 2013 10:54 pm

Editor variable for profile attribute?

Post by nrdlngr » Thu Jan 31, 2013 10:51 pm

I have a book that is shared between two software releases, and I use the "arch" parameter to filter out content that I don't want in an output.

Currently I have a PDF transformation scenario and a XHTML scenario set up, and I edit the scenario parameters with the proper values before running the scenario to profile the source and produce the output I want. However, I'm wondering if there is a way I can avoid editing the scenario parameters every time I create a different output. Is there a way I can pass a value from the "Profiling/Conditional Text" button, so I run transformation scenarios on what I see in the author view?

Can I use a custom editor variable for this? Or, is there already an editor variable for the visible profile set that I can insert in my transformation scenario profile.arch parameter that will pick up the value in the editor? That would be a great help to me.

Thanks in advance.

Posts: 7592
Joined: Fri Jul 09, 2004 5:18 pm

Re: Editor variable for profile attribute?

Post by Radu » Fri Feb 01, 2013 2:56 pm


As a workaround you can duplicate the transformation scenario and have one scenario (with custom parameters) for each produced output.

Actually we have an improvement request already logged in for somehow applying the current selected profiling condition set to a Docbook transformation.
We did this for DITA because DITA transformations filter based on a special DITAVAL filter file.
For Docbook it's more complicated and we do not yet know how to proceed because a defined profiling condition set (which basically says that certain attributes with certain values should be included).
And this profiling condition set needs to be translated into certain values for certain Docbook profiling attributes. So the profiling attribute set should probably be translated in multiple editor variables, something like ${arch}, ${audience}, ${platform} which would be expanded to nothing or to something based on the current applied profiling condition set.

Radu Coravu
<oXygen/> XML Editor

Post Reply