<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#336666" bgcolor="#FFFFFF">
<font face="Verdana">Hi Rebecca...<br>
<br>
There are two things here that you need to take into account.
First is just getting cross-refs to remain linked up through the
conversion process from FM to XML. Second is to get those
cross-refs to reference the individual topic files that result
from "shredding" the chapter-based XML files into DITA topics
(assuming that you're planning on going to separate topics and not
nested chapter-DITA files). Also getting the xref/@href format
correctly build can be tricky ("<filename>#<topicid>/<elemid>").<br>
<br>
Long ago I developed a plugin to handle all of this, and I've
forgotten how to do it without the plugin .. although it can be
done (with lots of scripting of various sorts). I recall that one
thing to try is to import a template into the FM files that
reformats the cross-refs so they include the Idref in the
cross-ref text. Change the format so this is in some delimiters to
make it easy to locate .. perhaps "[[<Idref>]]".<br>
<br>
Maybe someone can provide you with more useful info. :o<br>
<br>
<sales-pitch><br>
<br>
However .. what I'd suggest is that you download my FM2DITA plugin
..<br>
<br>
<a class="moz-txt-link-freetext" href="http://leximation.com/tools/info/fm2dita.php">http://leximation.com/tools/info/fm2dita.php</a><br>
<br>
Give it a try and see if it does what you need. If nothing else,
it may give you some tips on conversion table development and
ideas for tools that you can develop in-house. It's chock full of
utilities that will make your conversion process easier.<br>
<br>
</sales-pitch><br>
<br>
Also .. there's Mif2Go which costs less and once you get things
set up, will basically "just work".<br>
<br>
Remember that one of the reasons to use DITA is to leverage to
tools that already exist rather than needing to create your own.
No need to reinvent the wheel, right?<br>
<br>
Cheers,<br>
<br>
...scott<br>
<br>
<br>
<br>
</font>
<div class="moz-cite-prefix">On 12/8/13 2:00 PM, rebecca officer
wrote:<br>
</div>
<blockquote cite="mid:52A5A2E2020000380006070F@gwia2.atlnz.lc"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<base href="x-msg://6210/">
<meta name="GENERATOR" content="MSHTML 9.00.8112.16520">
<div>
<div>Hi everyone</div>
<div> </div>
<div>We're currently in the process of converting from
Unstructured FrameMaker files to DITA using FrameMaker 11. <br>
</div>
<div>The engineer who's working on the conversion has a question
about cross-references. When he structures the document using
the conversion table, he'd like to be able to save the Idref
value for the cross-reference as an attribute in the element
it is wrapped in. At the moment, when he structures the
document, all he can manage is to wrap the text in a
<xref> element.</div>
<div> </div>
<div>If anyone's got any ideas about how to do this - or about
how else to avoid having to manually re-create thousands of
cross-refs - I'd be really grateful! The engineer's happy with
scripting, esp Python, so it doesn't have to be a purely FM
solution.</div>
<div> </div>
<div>Thanks very much,</div>
<div>Rebecca</div>
<div> </div>
<div> </div>
</div>
<p><br>
NOTICE: This message contains privileged and confidential<br>
information intended only for the use of the addressee<br>
named above. If you are not the intended recipient of<br>
this message you are hereby notified that you must not<br>
disseminate, copy or take any action in reliance on it.<br>
If you have received this message in error please<br>
notify Allied Telesis Labs Ltd immediately.<br>
Any views expressed in this message are those of the<br>
individual sender, except where the sender has the<br>
authority to issue and specifically states them to<br>
be the views of Allied Telesis Labs.</p>
<p> </p>
</blockquote>
<br>
</body>
</html>