[oXygen-user] Struggling with conkeyref/conaction=pushafter

Frank Dissinger frank.dissinger at cgs-oris.com
Tue Mar 28 07:18:59 CDT 2023


Hi Radu,


Thank you for the link. Hm...


If the pushed content is not shown in the Oxygen Editor, then the 
feature is not really useful for me. I need to see it to have control 
over what I am doing.


The conref-push content does not appear in CHM output either. Perhaps 
this has to do with the fact that I still use oXygen V21.1 to generate 
CHM output. (I made some XSL customizations which are not easy for me to 
apply to V25, a bit difficult and lengthy to explain...).


It appears much simpler for me to filter the contents out. But owing to 
the way my process is set up, I would need to apply a second ditaval file.


Can I specify two ditaval files for the "args.filter" argument? This 
would be the best.


And I would need a second attribute in addition to "product", otherwise 
I would have to edit each and every element that uses a "product" 
attribute. There are not so many attributes available. Perhaps I could 
(mis)use "platform"... (for indicating the project).


I heard of ditvalref branch filtering and I tested this. It does not 
create the desired result as duplicates of every reused topic are 
created. This is not what I want and it messes up many topic references. 
Can I set up branch filtering differently so that no topic duplicates 
are created? Probably not...


The reason is that my ditaval files contain conditions for creating 
variants (oem1, oem2, etc. -- no condition stands for the base product) 
of a product group (project1, project 2). The same ditaval conditions 
(oem1, oem2, etc.) are used across different product groups. It never 
occurred to me to filter on product groups (projects) because I use root 
ditamaps stored in different folders to create output for different 
product groups.


Regards,

Frank


------------------------------------------------------------------------
Am 27.03.2023 um 18:50 schrieb Oxygen XML Editor Support (Radu Coravu):
>
> Hi Frank,
>
>
> Maybe this will help:
>
> https://blog.oxygenxml.com/presentation-reuse/conref_push.html
>
>
> One remark, Oxygen will not show the pushed content in place but 
> publishing should work.
>
>
> Regards,
>
> Radu
>
> Radu Coravu
> Oxygen XML Editor
> On 3/27/23 18:05, Frank Dissinger wrote:
>>
>> Hi all,
>>
>>
>> I have tested the "DITA > Push Current element" feature, but cannot 
>> get it to work.
>>
>>
>> I want to inject a <dlentry> element into a shared topic which is 
>> used in two projects. The element to be injected is stored in a 
>> warehouse topic for project 1. What I want is to inject this element 
>> only when project 1 is built. When project 2 is built, the key to the 
>> warehouse topic resolves to a different file which doese not include 
>> the element. So what I hope is that the element is only injected when 
>> I build project 1 and that it is left out when I build project 2 -- 
>> without any error or warning generated in the log file or in Oxygen's 
>> editor window.
>>
>>
>> However, the element does not appear in project 1 and in Oxygen it is 
>> shown as an empty <dt><p> struture. In a previous attempt the element 
>> was shown in the editor window, but not in output either. I can't 
>> remember what I did differently...
>>
>>
>> I may not have undestood this feature correctly. Can someone 
>> enlighten me? Thank you.
>>
>>
>> Regards,
>>
>> Frank
>>
>>
>> The dita code:
>>
>> *
>> *
>>
>> *file.dita*
>>
>>         <dlentry conaction="mark" conkeyref="lib_ref/my_id">
>>           <dt/>
>>           <dd>
>>             <p/>
>>           </dd>
>>         </dlentry>
>>         <dlentry conaction="pushafter">
>>           <dt>A term. The term in lib_ref.dita should be injected 
>> after that.</dt>
>>           <dd>
>>             <p>Explanation</p>
>>           </dd>
>>         </dlentry>
>>
>>
>> *lib_ref.dita
>> *
>>
>>       <dl>
>>         <dlentry id="my_id">
>>           <dt>The term to inject after the term in file.dita</dt>
>>           <dd>
>>             <p>Explanation</p>
>>           </dd>
>>         </dlentry>
>>       </dl>
>>
>>
>> *variables.ditamap*
>>     <keydef href="reuse/lib_ref.dita" keys="lib_ref"/>
>>
>> Appearance in oXygen.
>> -- 
>>
>> *Frank Dissinger*
>>
>> Documentation Manager
>>
>> ....................................................................
>>
>> *CGS Publishing Technologies International GmbH*
>>
>> *Email *frank.dissinger at cgs-oris.com | *Web* www.cgs-oris.com 
>> <http://www.cgs-oris.com/>
>>
>> *Address* Kettelerstr. 24 | D-63512 Hainburg | Germany
>>
>> *Phone* +49 6182 9626-27 | *Fax* +49 6182 9626-99
>>
>> *Commercial register* Offenbach, HRB no. 21495
>>
>> *Managing directors* Bernd Rückert, Christoph Thommessen
>>
>>
>> https://www.cgs-oris.com/Signatur.png 
>> <https://www.cgs-oris.com/signatur>
>>
>> _______________________________________________
>> oXygen-user mailing list
>> oXygen-user at oxygenxml.com
>> https://www.oxygenxml.com/mailman/listinfo/oxygen-user
>
> _______________________________________________
> oXygen-user mailing list
> oXygen-user at oxygenxml.com
> https://www.oxygenxml.com/mailman/listinfo/oxygen-user
-- 

*Frank Dissinger*

Documentation Manager

....................................................................

*CGS Publishing Technologies International GmbH*

*Email *frank.dissinger at cgs-oris.com | *Web* www.cgs-oris.com 
<http://www.cgs-oris.com/>

*Address* Kettelerstr. 24 | D-63512 Hainburg | Germany

*Phone* +49 6182 9626-27 | *Fax* +49 6182 9626-99

*Commercial register* Offenbach, HRB no. 21495

*Managing directors* Bernd Rückert, Christoph Thommessen


https://www.cgs-oris.com/Signatur.png <https://www.cgs-oris.com/signatur>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.oxygenxml.com/pipermail/oxygen-user/attachments/20230328/fd3df2fc/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: EstacsollFrlKD6H.png
Type: image/png
Size: 51235 bytes
Desc: not available
URL: <http://www.oxygenxml.com/pipermail/oxygen-user/attachments/20230328/fd3df2fc/attachment.png>


More information about the oXygen-user mailing list