Re: [oXygen-user] Setting up catalogs
Hi David, We'll probably have this fix available by Oxygen 9.3 (couple of days). When the fix will be available all you will have to do will be to add your catalog to the Oxygen catalogs list and the DITA Maps Manager topic references will be solved through the catalog. Regards, Radu -- Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com David Linton wrote:
I understand that you use URN's in topicref href's and you want when a map is opened in the DITA Maps Manager view to see correctly the links to the hrefs (solved by catalog) and of course when double clicking a link to open in the editor the real location solved by catalog. Indeed Oxygen does not yet solve by catalog the topic references presented in the DITA Maps Manager but we can work on this. Is my understanding correct?
Yes, that's right.
You also speak something about Oxygen ignoring catalog entries at validation. What kind of validation are you referring to?
I don't know - that's just the phrase you used in the user guide, where you distinguished "validation" from "transformation". I figured they were the only two processes involved, but I guess that was wrong.
Also, how have you modified the DITA-OT toolkit to allow the URN's to be resolved at transformation time?
DITA-OT isn't happy with map files which aren't at the top level so I ended up preprocessing all the links into a temporary directory with some XSL; a side-effect of that process is that topicref hrefs get resolved before they get to DITA-OT.
Before I did that, it worked fine to replace the <xslt> ant task in DITA-OT with one that used saxon with the apache commons resolver.
rgds dave .
I understand that you have an xml catalog which solves the URN's to real locations. Can you send us a sample from it?
I use "uriStartString" to save writing out all the URNs, although I'm aware that the URNs aren't quite compliant with the RFC, but it's not caused any problems so far.
<group xml:base="/build/dlinton/p4-workspaces/ws-david/docs/style/MAIN/dita-ot/"> <rewriteSystem systemIdStartString= "urn:quative.tv:dita:xsl/" rewritePrefix= "xsl/" /> <rewriteURI uriStartString= "urn:quative.tv:dita:xsl/" rewritePrefix= "xsl/" />
<rewriteSystem systemIdStartString= "http://docs.quative.tv/dita/xsl/" rewritePrefix= "xsl/" /> <rewriteURI uriStartString= "http://docs.quative.tv/dita/xsl/" rewritePrefix= "xsl/" /> </group>
<group xml:base="/build/dlinton/p4-workspaces/ws-david/docs/style/MAIN/"> <rewriteSystem systemIdStartString= "urn:quative.tv:dita:extensions/dtd/" rewritePrefix= "dtd/" /> <rewriteSystem systemIdStartString= "urn:quative.tv:dita:apiref/dtd/" rewritePrefix= "dtd/" /> <rewriteSystem systemIdStartString= "urn:quative.tv:dita:javaapiref/dtd/" rewritePrefix= "dtd/" /> <rewriteSystem systemIdStartString= "urn:quative.tv:dita:dtd/" rewritePrefix= "dtd/" />
<rewriteSystem systemIdStartString= "urn:quative.tv:style:" rewritePrefix= "" /> <rewriteURI uriStartString= "urn:quative.tv:style:" rewritePrefix= "" />
<rewriteSystem systemIdStartString= "http://docs.quative.tv/style/" rewritePrefix= "" /> <rewriteURI uriStartString= "http://docs.quative.tv/style/" rewritePrefix= "" /> </group>
<group xml:base="/build/dlinton/tmp/generated/"> <rewriteURI uriStartString= "urn:quative.tv:docs:generated/" rewritePrefix= "" /> <rewriteURI uriStartString= "http://docs.quative.tv/generated/" rewritePrefix= "" /> </group>
<group xml:base="/build/dlinton/p4-workspaces/ws-david/docs/content/MAIN/cca-ccom/"> <rewriteURI uriStartString= "urn:quative.tv:docs:cca-ccom/" rewritePrefix= "" /> <rewriteURI uriStartString= "http://docs.quative.tv/authored/cca-ccom/" rewritePrefix= "" /> </group>
<group xml:base="/build/dlinton/p4-workspaces/ws-david/docs/content/MAIN/"> <rewriteURI uriStartString= "urn:quative.tv:docs:" rewritePrefix= "" /> <rewriteURI uriStartString= "urn:quative.tv/docs/" rewritePrefix= "" /> <rewriteURI uriStartString= "http://docs.quative.tv/" rewritePrefix= "" /> </group>
This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, discussion or disclosure by others is strictly prohibited. If you are not the intended recipient of this email, please contact the sender by return email and delete all copies of this email and its attachments, if any.
On 24/06/2008 at 12:23, Radu Coravu <radu_coravu@sync.ro> wrote: Hi David,
We'll probably have this fix available by Oxygen 9.3 (couple of days). When the fix will be available all you will have to do will be to add your catalog to the Oxygen catalogs list and the DITA Maps Manager topic references will be solved through the catalog.
Regards, Radu
That'll be great, thanks ! By the way, I wasn't able to install the Eclipse version on my Eclipse 3.3 because some of the dependencies decided they now required the new 3.4 — a bit off, since it's not official until tomorrow! I upgraded to the 3.4 release candidate and oxygen warned me that I should be using 3.3 (but then worked fine) This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, discussion or disclosure by others is strictly prohibited. If you are not the intended recipient of this email, please contact the sender by return email and delete all copies of this email and its attachments, if any.
Hello again, Now I am evaluating Oxygen version 10 as our procurement process is slow :-) Thanks for incorporating the ditamap resolution feature. It works very well. But I have one more request: I would like to see catalog resolution also for hrefs in the editor's "Author" view. Because all the URIs I use need to be resolved, hrefs in <xref>, <link>, <image> etc. are not found. This is less of a problem than before, since navigation from the map manager is now possible, and the "Text" view resolves the hrefs correctly when I press F3, but it would be nice to see images and follow related links from the "Author" view. rgds David Linton .
Radu Coravu <radu_coravu@sync.ro> 24/06/2008 12:23 >>> I understand that you use URN's in topicref href's and you want when a map is opened in the DITA Maps Manager view to see correctly the links to the hrefs (solved by catalog) and of course when double clicking a link to open in the editor the real location solved by catalog. Indeed Oxygen does not yet solve by catalog the topic references presented in the DITA Maps Manager but we can work on this. Is my understanding correct?
Yes, that's right.
This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, discussion or disclosure by others is strictly prohibited. If you are not the intended recipient of this email, please contact the sender by return email and delete all copies of this email and its attachments, if any.
Hi David, Thanks for the feedback. We will consider adding xref/link/image resolution through the catalog in a future version (hopefully 10.1). Regards, Radu -- Radu Coravu <oXygen/> XML Editor http://www.oxygenxml.com David Linton wrote:
Hello again,
Now I am evaluating Oxygen version 10 as our procurement process is slow :-) Thanks for incorporating the ditamap resolution feature. It works very well. But I have one more request: I would like to see catalog resolution also for hrefs in the editor's "Author" view. Because all the URIs I use need to be resolved, hrefs in <xref>, <link>, <image> etc. are not found.
This is less of a problem than before, since navigation from the map manager is now possible, and the "Text" view resolves the hrefs correctly when I press F3, but it would be nice to see images and follow related links from the "Author" view.
rgds David Linton .
participants (3)
-
David Linton -
Mircea Enachescu -
Radu Coravu