Ok, great. That seems to have fixed it. I'm using v.12, but I thought the value should be "false". So just to get this straight, this is a DITA OT bug?

Regards,

Anders

Well, actually the problem is something that I know has come up before, and I thought it would be resolved simply by choosing the local DTD. The thing is, the dita files have nbsp entities in them, and the local DTD has a declaration for this entity. But it doesn't seem to help. I searched the archi...

Hi,

I have some dita files that have doctype declarations specifying both public id and system id, but for this particular case I need the transformation to use the system id. Is it possible to make the transformation prioritize the system id instead of the public id?

Regards,

Anders

Yes, that was what I was thinking - having preset input files for the scenarios. I think this would be a good feature to have.

Regards,

Anders

Hi, I'm wondering if there is any way to do batch transformation except through the project view. My situation is this: I have a number of publications for different products, that often need to be retransformed. It is always the same products with the same settings, so it would make sense to do it ...

Right, yes some sort of post-processing is the only thing I've come up with so far as well, but I wanted to avoid that in case there already was some functionality in the OT or Oxygen that I had missed. But it seems that will have to be the way to go then.

Thanks,

Anders

Ok, I didn't realize that it was 1.5.1. So that's probably why it differs then. Yes, I think there was some copy instruction in the build script for the frameset files in the new version. I know I can switch DITA OT with the parameters in Oxygen, and I usually do that. I did so now too, but the diff...

Sorry, it was late when I wrote my question Forget about number 2, that was of course (for some reason) the title in the ditamap in the garage samples.

But I still wonder about question 1...

Regards,

Anders

Hi, I've previously only rendered HTML using DITA OT directly, but now I tried the HTML output using the transformation scenario in Oxygen. I was surprised to see that the output was not the same as when doing it directly in the OT: 1. Instead of the frameset output with the TOC in the left frame an...

Great, thanks!

A follow-up question for this thread: When I set some new values for a profiling attribute, say "product", are these set values saved in some sort of configuration file that is portable to another installation of Oxygen? Same question for "Profiling Condition Sets"... Regards, An...

Thanks that worked perfectly, especially together with the custom editor variables feature, since I don't use the DITA-OT in the Oxygen frameworks directory.

Regards,

Anders

Hi, I tried setting the xml.catalog.files in the transformation scenario as you suggested. But when I did, I the cfg protocol is not recognized (I set it to ${customization.dir}/catalog-testdocs.xml;${basedir}/cfg/catalog.xml). Here's the error message: [java] XTSE0165: javax.xml.transform.Transform...

Ok, thanks!

I'm using the conkeyref features, and I found something rather strange: When I add a conkeyref range for a few steps, the conref attribute is fine, but the conrefend attribute gets a strange value: <steps> <step conkeyref="resource/step1" conrefend="fake.dita#fake/step3"> <cmd/> ...

Ok, if you did add such possibilities for future releases that would be great. In either case, I just have to say that I think you've done a wonderful job so far, the editor just keeps getting better and better .

Regards,

Anders

Ok, I thought that was the whole point of being able to point to your own custom build file? So basically, the only point of specifying your own build file is if you want to specify other parameters than the ones already set in the dialog? I guess I'll have to run these transformation outside of Oxy...

Hi, I'm trying to run a custom build file with Oxygen, so I have specified the file in the transformation scenario dialog, and I can see in the log that it is being used, so that's no problem. But the problem is it doesn't seem to care about the properties I set there, which I assumed would override...

Good, clear answer! Thanks for that! But, to return to my original question: there is really no simple way to switch stylesheets for PDF then, seeing as the custom.xsl is selected by the catalog.xml file? I understand that I could according to your answer define several catalog.xml files, all pointi...

Another follow-up... After some more testing, it seems the Customization/catalog.xml in the currently used DITA OT applies no matter what is set in the Preferences XML Catalog setting...? I was surprised to find this, because I had previously heard in this forum that you needed to tell Oxygen about ...

A follow-up to this question: I discovered that with two different transformation scenarios (both for DITA pdf), I get different custom stylesheets. But I can't figure out how... The thing is, for scenario A, I had defined a particular Customization/catalog.xml file that pointed to a specific custom...

Hi, I have custom.xsl stylesheets defined, and referenced through the demo/fo/Customization/catalog.xml file (Added under Preferences -> XML Catalog). But I need to switch between different custom stylesheets for different documents. Of course I can edit the catalog.xml file, but it's kind of cumber...

Never mind! I found the problem myself. Apparently the catalog reference did work in the editor, but I had just forgotten to change task to test in the name of the DTD...

Regards,

Anders

Hi, I was wondering about the addition of the DTD to the catalog.xml. I have added the following to the catalog-dita.xml <public publicId="-//OASIS//DTD DITA Test//EN" uri="test.dtd"></public> <public publicId="-//OASIS//ELEMENTS DITA Test//EN" uri="test.mod">...

Ok, thanks for the clarification.

Regards,

Anders

Hi Radu, Ok, well I investigated a bit further in the xsl files as well as the build files, and I actually don't think the frontmatter.xsl is the entry point, but rather it seems to be topic2fo-shell.xsl now. That file has all the necessary imports for an entry file, and also calls root-processing.x...

Hi, I am a bit confused as to how the cover image is rendered in PDF with the Dita 1.2 provided with Oxygen. Before there was a call to dita2fo-shell.xsl in the rendering process, which had a template called "place-cover-art". This does not seem to be called at all in the Oxygen rendering ...

Absolutely, that's why I was surprised to see it, but it turns out I misunderstood the purpose then.

But that's perfect anyway, I'll just continue doing the specializations myself but at least now I have support for adding values in the editor. Great!

/Anders

Hi again, I have now tried the new profiling functionality, and it seems rather promising, but I'm not sure I get it fully. The big surprise was that it seems as if you can define new profiling attributes directly in the preferences dialog...? But I tried it, and it didn't quite work out. I defined ...

Ok, now I ran into a new problem... It works fine as long as I'm content with the default wysiwyg styling for dita. But, the problem is, I will have to modify this view somewhat, so I created a separate copy of the dita.css and the imported task.css. But how do I use it in a template? I.e. I have a ...