adobe technical support sent me here. hope here can help.
i have dita map file , xml files. within of xml files, used fm-xref element create cross-references xml files in dita map.
when select dita > build fm ditabook dita map file, nice fm book file xml.fm files in it. ducky, except cross-references. cross-references in xml.fm files still point @ source xml file. expected cross-references point corresponding locations in new xml.fm files, not original source files. after fiddling fm while, couldn't figure out do.
so, contacted adobe tech support, , said, "this can happen if not have read/write rules set correctly. default, cross references point xml unless specified differently. information on how set read/write rules, suggest
this webpage: http://www.adobe.com/devnet/framemaker/pdfs/structure_dev_guide.pdf. there whole chapter in pdf read/write rules."
so spent afternoon reading read/write rules. i'm sorry gained no insight on how fix this. contacted tech support again, , assured me 1) read/write rules , 2) don't know how read/write rules work.
does know read/write rule force fm point fm-xref element new file instead of original file? care share? thanks!
i have dita map file , xml files. within of xml files, used fm-xref element create cross-references xml files in dita map.
when select dita > build fm ditabook dita map file, nice fm book file xml.fm files in it. ducky, except cross-references. cross-references in xml.fm files still point @ source xml file. expected cross-references point corresponding locations in new xml.fm files, not original source files. after fiddling fm while, couldn't figure out do.
so, contacted adobe tech support, , said, "this can happen if not have read/write rules set correctly. default, cross references point xml unless specified differently. information on how set read/write rules, suggest
this webpage: http://www.adobe.com/devnet/framemaker/pdfs/structure_dev_guide.pdf. there whole chapter in pdf read/write rules."
so spent afternoon reading read/write rules. i'm sorry gained no insight on how fix this. contacted tech support again, , assured me 1) read/write rules , 2) don't know how read/write rules work.
does know read/write rule force fm point fm-xref element new file instead of original file? care share? thanks!
hi michael...
i think tech support person didn't understand going on. r/w rules have nothing issue. 1 of known "issues" default fm8 dita map book conversion process .. unfortunately don't know of way around problem. might able make work modifications xslt import script (you won't able "fix" it, given assumptions, might able make work files).
btw .. dita-fmx handle situation properly. (http://www.leximation.com/dita-fmx).
regards,
...scott
scott prentice
leximation, inc.
www.leximation.com
i think tech support person didn't understand going on. r/w rules have nothing issue. 1 of known "issues" default fm8 dita map book conversion process .. unfortunately don't know of way around problem. might able make work modifications xslt import script (you won't able "fix" it, given assumptions, might able make work files).
btw .. dita-fmx handle situation properly. (http://www.leximation.com/dita-fmx).
regards,
...scott
scott prentice
leximation, inc.
www.leximation.com
More discussions in FrameMaker Structured
adobe
Comments
Post a Comment