Hi Nick, Thanks for your reply. After some investigating, having the conref topic references as resource-only in the map doesn't solve the issue. :-( Best wishes, Christina

#keys #conref

Hi Jay, Please see some answers below: Good question, right now our Oxygen Publishing Engine available on the web site is based on DITA OT 3.5.4. It has extra patches for: https://github.com/dita-ot/d

#keys #conref

Good morning Jonathan, it seems to me that having reusable images in a dedicated warehouse-topic is easier to manage than keydefs in a map: create a table with two columns where the left column holds

#conref #keys

At a previous job, we were doing content management without a CMS, and we relied on simple, consistent practices and enforcement to take care of things like naming files and @id's. Tony Self's book an

#conref

Hi Ozana, How about if you keep that key definition for "key_doc_titles" in the front matter and also copy it inside both key scopes? Regards, Radu Radu Coravu <oXygen/> XML Editor http://www.oxygenxm

#conref #DITA-OT

Hi Matt, After you define these keys in different key scopes you can explicitly refer to any of them like: Or as other use cases you can refer to the same DITA topics in various key scopes and have th

#conref

Hi group I have multiple similar equations in my DITA topics where only one or two values are different, so I would like to reuse the identical parts. Is there a way to do this (if necessary with a pl

#conref #MathML

I tend to use conref for cases where reuse is internal to a single topic, where the overhead of seeing up a key is really not needed. I use the this topic structure to implement. That said, I can coun

#conref

Hi Bob, Thank you for your reply. I wasn't aware of this restriction. Seems illogical... I entered the code you suggested (had to switch to XML View): <steps conkeyref="key/id"> <step><cmd/></step> </

#conref #FrameMaker