Invalid xref format

[sverhagen]

Hi,


Somehow I manage to insert xrefs like this:

Code: Select all

<p id="FS939">The transaction can be cancelled. A <xref href="../Client Stations UI/Overall%20Client%20Station%20UI%20Characteristics.dita#DynamicButtons" format="dita#DynamicButtons">dynamic button</xref> is used as the cancel button.</p>

I would say the format is wrong. Is this a known problem? Is there a solution?

I don't know how I manage to do this, I'm using the normal Cross Reference functionality. This is as of 14.0.

Kind regards, Sander.

[Radu]

Hi Sander,

As I replied here:

http://tech.dir.groups.yahoo.com/group/ ... sage/28179

the problem can happen when the DITA Map references a DITA topic with a @href value which is not fully escaped, something like:

Code: Select all

 <topicref href="Event Detail Types

Listed/Detail%20sectionTo%20-%20Copy.dita"/>

and you use "Search for file" to insert the cross reference instead of browsing for it.

Could you check in your DITA Map that all topic references are properly escaped?
We can also modify the format detection on our side to make it more robust.

Regards,
Radu

[sverhagen]

Thanks for that.

Could you check in your DITA Map that all topic references are properly escaped?

They weren't. So, as I said here, I cleaned up all hrefs. So let's see what happens.

We can also modify the format detection on our side to make it more robust.

I think that would be a good idea anyhow.

[sverhagen]

Hi,


Even though cleaning up all my xrefs, after I just created an entirely new topic, and trying to link to it, things went wrong again:

Code: Select all

<p id="FS14178">An <xref

href="../Miscellaneous/Event%20Types%20Listed/External payment transaction handled.dita#topic_ajl_ns3_2h"

format="dita#topic_ajl_ns3_2h">event</xref> is generated for a deferred

payment.</p>

This is does the new file I created:

Code: Select all

External payment transaction handled.dita

Kind regards, Sander.

[Radu]

Hi Sander,

And how exactly is the new topic "External payment transaction handled.dita" referenced in the DITA Map?
What is the exact value of the @href attribute set on the topicref?
Is the path contained in it properly escaped?
Did you edit the DITA Map in the Text page or did you use our actions to insert a topicref?
Did you use the "Search for file" utility to find the new topic for cross reference? Does the same thing happen when browsing for it using the file chooser?

Regards,
Radu

[sverhagen]

Hi,

And how exactly is the new topic "External payment transaction handled.dita" referenced in the DITA Map?

Incorrectly:

Code: Select all

<topicref href="Operator%20Web%20UI/Test Test.dita"/>

Did you edit the DITA Map in the Text page or did you use our actions to insert a topicref?

It is put there, as I create the topic, using "Insert After", "New topic...". So no manual editting involved.

Did you use the "Search for file" utility to find the new topic for cross reference?

Yes.

Does the same thing happen when browsing for it using the file chooser?

No.

Hope this helps!

Kind regards, Sander.

[Radu]

Hi Sander,

Now I think I understand.
So you call "New Topic...", the "New from templates.." dialog shows up.
Then in the "Save as" field you will have a value like:

file:/C:/main/dita/Operator%20Web%20UI/topic.dita

You do not browse for a specific location (because the shown folder location is proper) but you edit manually the name of the file (without setting %20 instead of spaces in the file name). Then indeed Oxygen does not escape the file name in the generated topicref because if considers that the path to the topic already is escaped (there are already %'s in the path).
We will make some improvements and try to correct the file name even if the path is already corrected.

What you could do in the meantime would be either to always use the Browse button next to the Save As field or to write the file name with spaces escaped to "%20" (which is awkward).

Regards,
Radu

[sverhagen]

Hi Radu,


Thanks for that, I'll happily await whatever upcoming release can fix this, and meanwhile I'll fix by hand or regularly run the little tool that I made for it, no worry.

Kind regards, Sander.

[Radu]

Hi Sander,

A fix for this will be available in Oxygen 14.1, in September this year.
Thanks for the patience.

Regards,
Radu

[Radu]

Hi,

Oxygen 14.1 was just released and should contain the fix for this.

Regards,
Radu