Question
Cross-references in DITA files
Adobe Technical Support sent me here. I hope someone here can help.
I have a DITA map file and XML files. Within some of the XML files, I used the fm-xref element to create cross-references to XML files which are also in the DITA map.
When I select DITA > Build FM DITABook from DITA Map file, I get a nice FM book file with xml.fm files in it. Just ducky, except for the cross-references. The cross-references in the xml.fm files still point at the source XML file. I expected that the cross-references would point to the corresponding locations in the new xml.fm files, not to the original source files. After fiddling with FM for a while, I couldn't figure out what to do.
So, I contacted Adobe Tech Support, and they said, "This can happen if you do not have your read/write rules set correctly. By default, cross references will point to the XML unless specified differently. For information on how to set your read/write rules, I would suggest
this webpage: http://www.adobe.com/devnet/framemaker/pdfs/Structure_Dev_Guide.pdf. There is a whole chapter in the PDF about read/write rules."
So I spent an afternoon reading about read/write rules. I'm sorry to say that I gained no insight on how to fix this. I contacted tech support again, and they assured me that 1) it is the read/write rules and 2) they don't know how read/write rules work.
Does anyone know the read/write rule that will force FM to point the fm-xref element to the new file instead of the original file? Would you care to share? Thanks!
I have a DITA map file and XML files. Within some of the XML files, I used the fm-xref element to create cross-references to XML files which are also in the DITA map.
When I select DITA > Build FM DITABook from DITA Map file, I get a nice FM book file with xml.fm files in it. Just ducky, except for the cross-references. The cross-references in the xml.fm files still point at the source XML file. I expected that the cross-references would point to the corresponding locations in the new xml.fm files, not to the original source files. After fiddling with FM for a while, I couldn't figure out what to do.
So, I contacted Adobe Tech Support, and they said, "This can happen if you do not have your read/write rules set correctly. By default, cross references will point to the XML unless specified differently. For information on how to set your read/write rules, I would suggest
this webpage: http://www.adobe.com/devnet/framemaker/pdfs/Structure_Dev_Guide.pdf. There is a whole chapter in the PDF about read/write rules."
So I spent an afternoon reading about read/write rules. I'm sorry to say that I gained no insight on how to fix this. I contacted tech support again, and they assured me that 1) it is the read/write rules and 2) they don't know how read/write rules work.
Does anyone know the read/write rule that will force FM to point the fm-xref element to the new file instead of the original file? Would you care to share? Thanks!
AdChoices