Does Oxygen add in <?xm-replace_text?> processing instruction when using SDL Authoring Bridge?

Post here questions and problems related to editing and publishing DITA content.
ann.jensen
Posts: 295
Joined: Wed Jun 17, 2015 10:19 am

Does Oxygen add in <?xm-replace_text?> processing instruction when using SDL Authoring Bridge?

Post by ann.jensen »

Hi,
Our authors use XMetaL across the SDL Authoring Bridge and XMetaL adds in a <?xm-replace_text?> processing instruction to resolve names of topics linked to in cross references.
Does Oxygen apply this same PI for topics authored across the SDL Authoring Bridge?
Any advice appreciated,
Regards,
Ann
Radu
Posts: 9059
Joined: Fri Jul 09, 2004 5:18 pm

Re: Does Oxygen add in <?xm-replace_text?> processing instruction when using SDL Authoring Bridge?

Post by Radu »

Hi Ann,

Oxygen does not use this processing instruction in any way, when in a DITA topic you have a cross reference to another DITA topic and the xref has no text inside it Oxygen retrieves the title of the target topic dynamically when you open the XML document containing the link. So it does not "cache" that title inside a processing instruction.

Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com
ann.jensen
Posts: 295
Joined: Wed Jun 17, 2015 10:19 am

Re: Does Oxygen add in <?xm-replace_text?> processing instruction when using SDL Authoring Bridge?

Post by ann.jensen »

Thanks for your reply Radu.
When you say
Oxygen retrieves the title of the target topic dynamically when you open the XML document containing the link.
does the linked-to topic have to exist locally along with the XML document containing the link?
Or does Oxygen go across the SDL Authoring Bridge to source the title if it's not available locally?
Thanks again,
Ann
Radu
Posts: 9059
Joined: Fri Jul 09, 2004 5:18 pm

Re: Does Oxygen add in <?xm-replace_text?> processing instruction when using SDL Authoring Bridge?

Post by Radu »

Hi Ann,

Most CMS integrations (including SDL) work with a custom URL protocol implemented by the browser vendor with an Oxygen plugin, so when I open in Oxygen a resource from the SDL browser view implemented by SDL as an Oxygen plugin, Oxygen opens an URL like "sdl://path/to/topic.dita" and asks SDK for the content.
When topic.dita has an xref like <xref href="target.dita"/>, Oxygen creates an absolute URL for the reference like "sdl://path/to/target.dita" and again asks the SDL connector for the content. The SDL plugin/connector may retrieve the content from the server or it may have also a small local cache (which it does from what I know) to avoid retrieving the same resource's content twice.

Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com
Post Reply