Page 1 of 1
keydef.xml error when building ditamap
Posted: Wed Jun 30, 2010 1:37 am
by fedoroffn
I have a ditamap with several <keydef> topics. I am using <term keys="">s to reference these <keydefs> in other DITA topics to produce links to the keydef topics (set to processing-role="normal").
My DITA transformation was working great last week, producing links to the <keydef> topics. Now, seemingly all of a sudden, no links are produced and I get this error when I run the transformation:
[xslt] /Applications/author/frameworks/dita/DITA-OT/xsl/xslhtml/dita2htmlImpl.xsl:4935: Error! Document has been marked not available: file:/Applications/author/frameworks/dita/DITA-OT/xsl/xslhtml/dita2htmlImpl.xsl/..//Users/fedoroffn/Documents/Source/Help/mainline/DITA Source/en/temp/Users/fedoroffn/Documents/Source/Help/mainline/DITA Source/en/keydef.xml
Thoughts?
Thanks
Re: keydef.xml error when building ditamap
Posted: Wed Jun 30, 2010 9:44 am
by Radu
Hi,
This error is usually given when a topic reference file (in this case probably the keydef.xml) is not found at the referenced location (maybe for example it is referenced with a file path instead of an URL path).
Did you make some changes to the transformation scenario lately? Does the transformation work for other formats ? (like IDIOM PDF).
Also make sure you delete the temporary and output directories before making the transformation (maybe ANT does not properly overwrite some files).
Oxygen 12 will have an action which tries to find all these linking problems on a given DITA Map and then reports the errors.
If you write us to our technical support email address we can give you a link to a beta kit of Oxygen 12 so that you can check your DITA Map.
Also, if you provide us with a sample DITA Map project we may be able to give you more details.
Regards,
Radu
Re: keydef.xml error when building ditamap
Posted: Wed Jun 30, 2010 6:40 pm
by fedoroffn
Thanks, Radu. Here are my repsonses to your questions and comments:
This error is usually given when a topic reference file (in this case probably the keydef.xml) is not found at the referenced location (maybe for example it is referenced with a file path instead of an URL path)
It appears that the transformation is looking for keydef.xml in the wrong location. The error says it's looking in
Source/Help/mainline/DITA Source/en/keydef.xml
when keydef.xml is a temp file created in the temp folder during the transformation and should be at
Source/Help/mainline/DITA Source/en/
temp/keydef.xml
Did you make some changes to the transformation scenario lately?
I have not. I am using the default "DITA Map XHTML" transformation.
I'll write to tech support and ask for the beta.
Thanks,
Nick
Re: keydef.xml error when building ditamap
Posted: Wed Oct 27, 2010 3:49 pm
by nigelparker
Hi,
Did this problem ever get resolved?
I had a book working perfectly. I moved a keydef file to a different folder and updating its properties in the ditamap to point to the new location.
None of my conkeyrefs work any more:
[xslt] C:\DITA-OT1.5.1\xsl\preprocess\conrefImpl.xsl:850: Error! Document has been marked not available: file:///C:/WORK/Gemalto/SANDBOX_DITA/Sample_files/Files_for_new_books/UserGuide/temp/UserGuide/Concept/Shared/Rvariables.xml
It's looking in the wrong place. However, the links work within OxygenXML. I have tried everything: refreshing references, deleting temp and out folders, nothing seems to work.
Re: keydef.xml error when building ditamap
Posted: Wed Oct 27, 2010 4:16 pm
by Radu
Hi Nigel,
Oxygen 12 comes with DITA Open Toolkit 1.5.1 which from what I know contained some content reference bug fixes.
Oxygen 12 also has a "Validate and Check for Completeness" toolbar action in the DITA Maps manager which can be used to check for broken references.
Maybe you can request a trial license on our web site and check if the DITA OT from Oxygen 12 does a better job of resolving the references.
If it still does not work:
You should try to prepare a small sample DITA Project in which the problem can be reproduced and send it to us.
Then I'll try to analyze it and post a bug on the DITA Open Toolkit bugs list.
Regards,
Radu