Hi Radu:
Thanks, with your help, I finally got it to work, Oxygen rocks! Thanks again.

Hi Radu:

Is it possible for you to take a look at the DTD file I sent you? There might've been a typo somewhere but I couldn't seem to locate it, any help from you is greatly appreciated.

Hi I copy the files you sent me and copied them to the dita-ot/plugin directory according to the structure of the folder you sent me, then I ran the integrator, everything went ok. I then tried to create a blank doc template by opening a blank DITA doc, and in text mode, I have the following: <?xml ...

Hi, Thanks for the modified plugin, really appreciate it! I know that this plugin requires the default DITA-OT to work (the one shipped with the current version of Oxygen), but since I am using an older version of DITA-OT (1.2), how do I get this to work on that older version with Oxygen v. 17? Any ...

Hi, This question is more of an extension of a specialization question that I asked a few years, back in the days when I was using Oxygen v. 13: https://www.oxygenxml.com/forum/topic6669.html I am currently evaluating Oxygen XML Author v. 17.1 on Mac OS X EL Capitan 10.11.4. I was trying to create a...

Hi Radu: Thanks for the reply. Just out of curiosity: What is the purpose of having a Customization subdirectory inside the DITA-OT folder? What does that subdirectory do anyway? Thanks.

Hi, I saw a diretory in DITA-OT\demo\fo called "Customization," so I naturally assumed that this was the place that hosts customized settings. However, when I tried to migrate my custom settings by saving my custom files there, the customized settings did not reflect on the output. Yet, if...

Hi Radu:
You are absolutely right about the match selector being incorrectly set; I changed it from "txvia-d/artifact_type" to simply "artifact_type", and it was working! Thanks for pointing out the root cause of the problem, you have my highest regard

Hi Radu: I completely commented out the template for <codeph>, and ran the transform again, the specialized element <artifact_type> still didn't get the attributes I set for it. You mentioned that maybe the match selector was incorrectly set, what could be wrong with my match selector, could you ple...

Hi Radu:
Thanks for the reply; however setting priority to a higher number doesn't seem to work either, it still grabbed the attribute set for <codeph> and applied it to <artifact_type>, any ideas?

Hi, I also posted this question on the Yahoo DITA user group board. This is a question I've always wanted to ask but never had a chance to do so, partly because I didn't really think this could be a problem until now. Long story short: I've created a new specialized element called <artifact_type> ba...

Hi Sorin, that's what I thought, thanks again.

Hi, I've been scratching my head about this and could not find a solution. Basically what I want to do is this, I have a couple of DITA topic tiles (topic/title) that are formatted as <codeph> (Monospaced font, that is), and when I generate my PDF, I want the TOC　entry for the topic title formatted ...

Thanks again.

Hi Radu:
I received your reply, and your solution worked! Thanks a lot for your help.

Hi Radu, thanks for your help, I've sent my specialized files to: support@oxygenxml.com .

Hi, I've created a specialized domain called "txvia" and added two specialized elements: "artifact_type" and "txvia_reserved." I've added entries to the catalog-dita.xml file so that it can resolve my newly created public ID: "-//TxVia//DTD DITA Topic//EN." Ho...