Rosen,
Sounds like you may have copied cross-references from an original location to a 
new location. This brings along with it the original source ID marker. You 
can't have more than one unique ID marker, else you get wierd cross-reference 
issues.

There is a tool from West Street Consulting that may fix your problem. Check 
out the XRef Wizard (http://weststreetconsulting.com/WSC_XRefWizard.htm). Only 
$35.00 (for one user). You can download a trial version so see if it helps. It 
has proved to be a life saver.

Also, refer to the support information (Appendix D) in the Mif2Go User's Guide. 
Jeremy should be able to steer you in the right direction, if it is a Mif2Go 
option issue.

--- On Wed, 10/13/10, Menahem Rosen <Menahem.Rosen at objet.com> wrote:

From: Menahem Rosen <menahem.ro...@objet.com>
Subject: "Toc" cross-ref markers
To: "framers at lists.frameusers.com" <framers at lists.frameusers.com>
Cc: "steve at context.co.il" <steve at context.co.il>
Date: Wednesday, October 13, 2010, 6:01 AM

When using Mif2Go to create html (chm) Help from my FM files, I have found many 
cross-reference links that do not work.? Upon inspection of the html source 
code, I see that the problematic links begin "#Ran_toc155..." instead of 
"an2525860.htm#Ran375..."

In the FM file, double-clicking on the x-ref displays the cross reference 
dialog box, showing the "Cross-Ref" marker type, and the "_toc155..." marker. 
Using this dialog box to change the marker type and link to the paragraph does 
not make a permanent change: double-clicking again on the x-ref displays the 
old "_toc" marker.

The only solution I have found is to delete the offending marker in the target 
and then create a new cross reference from scratch. The KB questions are how 
did the problem occur, and how can I be sure that it won't re-occur? The 
practical question is how can I quickly replace the offending cross references 
with proper ones? (Obviously, doing so manually is a very tedious task, 
especially since the target may be referenced by multiple cross-references in 
the book.)

TIA,

Menahem R.

Reply via email to