Support current filtering + specified flagging DITAVAL files in transformations
Posted: Sun Mar 22, 2020 5:43 pm
I am trying to refactor our DITAVAL files into separate filtering and flagging files:
(We currently have DITAVAL files for all multiplied combinations, but this is becoming unworkable.)
Consider the following DITA content that has content for product1 and product2:
The profiling menu allows us to filter by product via the filter* DITAVAL files, and to highlight content via the profiling condition colors - this is great!
In our output transformation, I use the currently applied filter condition so the writer can specify the product:
And in the transformation parameters, I specify the flagging according to whether I'm doing a review or final transformation:
Unfortunately these DITAVAL specifications are not cumulative. Instead, the flagging DITAVAL (args.filter parameter) takes precedence over the filtering parameter (the currently specified filter condition) and we lose the ability to filter the output.
It would be great for Oxygen to understand that when both DITAVAL-based specification types exist for a given transformation, that the intent is to combine them. (As a side note, this refactoring is to use the new "DITA-OT project file" feature in Oxygen 22.0 and the DITA-OT 3.4).
I've hit my limit of three attachments for this message. I'll attach a small testcase to the next message.
Code: Select all
$ fgrep 'action="include"' *
filter_product1.ditaval: <prop att="product" val="product1" action="include"/>
filter_product2.ditaval: <prop att="product" val="product2" action="include"/>
$ grep revprop *
flag_final.ditaval: <revprop action="include"/>
flag_review.ditaval: <revprop action="flag" backcolor="#FEFEC9"/>
Consider the following DITA content that has content for product1 and product2:
Code: Select all
<p>This <ph rev="1.0">changed</ph> line is for <ph product="product1">product 1</ph><ph product="product2">product 2</ph>.</p>
In our output transformation, I use the currently applied filter condition so the writer can specify the product:
And in the transformation parameters, I specify the flagging according to whether I'm doing a review or final transformation:
Unfortunately these DITAVAL specifications are not cumulative. Instead, the flagging DITAVAL (args.filter parameter) takes precedence over the filtering parameter (the currently specified filter condition) and we lose the ability to filter the output.
It would be great for Oxygen to understand that when both DITAVAL-based specification types exist for a given transformation, that the intent is to combine them. (As a side note, this refactoring is to use the new "DITA-OT project file" feature in Oxygen 22.0 and the DITA-OT 3.4).
I've hit my limit of three attachments for this message. I'll attach a small testcase to the next message.