Structured Cross-References

Morning everyone
I'm currently working in a structured template in Frame 9.  I am trying to insert a reference to a graphic that I have already created in the structure.  The problem I am having, which it seems to me that I am doing something wrong is that when I go to insert a refint element, it brings up the cross-reference box, but under the elements listing in the document, it doesn't contain the title element.  I am trying to reference to the title element that is a child of the graphic element.
There are only a few elements showing and even less that contain any text. Can someone help me out and tell me what I am doing wrong?
I have also saved this back to Frame 8 and I still have the same problem.  I am also the one developing the structured application, so it is possible that the problem may reside with the application itself.
Screen shot attached...
Thank you
Lyncca

Hi Van,
Yes, I did end up linking to the higher level, but we still had to add the unique id.  I had overlooked it when building the DTD/EDD.  It has been a couple of years since I created a structured app, so some of those little things got lost since then
It works perfectly now! (until I find something else that doesn't work )

Similar Messages

  • Cross-reference between structured and unstructured FM documents

    Hello,
    Is it possible to retain FM cross-references from structured to unstructured FM documents during an XML round trip?
    From what I know, cross-references between or inside structured documents form pairs of ID and IDREF, while cross-references to unstructured documents are dumped as normal text and lose their functionality.
    The unstructured target documents might be converted to Structured FM at some point, but for the time being I'd like to find another solution. Do you know any solution to this?
    Thanks,
    Johannes

    Johannes,
    This is just a guess, because I do not do this.
    First, of course, you cannot export the unstructured file to XML, because it is unstructured.
    Second, IF the cross-reference from the structured file to the unstructured file were done via your cross-reference ELEMENT, then the cross-reference element should export to XML as an XML element with one of its IDref attribute set to the ID of something in the unstructured file. When you open the XML file in FrameMaker, the cross-reference is re-established.
    In other words, when exporting to XML, FrameMaker does not care to what you are referencing. It just converts the cross-reference element into an element with an attribute in the XML file. So, it should work as expected when opened in FrameMaker. Of course, I am assuming your read-write file is set up to handle cross-references.
    On the other hand, IF you are creating your cross-reference from the structured file by simply inserting a cross-reference, that is NOT as an element, then I do not know what happens. If it is being exported as text, then I am not sure FrameMaker will know what to do with it when you reopen the XML file.
    Hope this helps,
    Van

  • How can I get XML cross-references to translate to Structured FrameMaker?

    I've been using Structured FrameMaker from the beginning, and have designed many EDDs, and about 10 years ago I did some translation of SGML into Structured FrameMaker (7.2) which worked well.
    Now, (with FrameMaker 10), I've had to design an EDD to translate XML documents into Structured FrameMaker.
    In my EDD I've a CrossReference element called XRef; this has an attribute of ID, which in turn has a value of IDReference and has Special AttributeConrols of ReadOnly.
    My target elements in the EDD all have an ID attribute with a value of UniqueID.
    My XML document's target xref element has  an attribute of linkend, and in XML this works as I'd expect.
    When I pass the XML file through the EDD/Template, everything works except that I get an ID = no value, which, of course, results in no display of the cross-reference data in the document.
    Oddly, in structured FrameMaker, my element of link, with an attribute of linkend, works as it should, and displays the data.  It may not be important, but the value for linkend is IDReference not UniqueID, and this displays correctly (I changed this attribute's value to Unique ID in my EDD and it made no difference to the XRef value in my document).
    After making all these EDD changes, I've been careful to save the changes, import them to all files in my book and finally update the book.   Everything hangs together - except, of course, that the cross-reference doesn't work.
    I'd sincerely appreciate any help or advice other users might have because I'm quite frankly stumped.

    Russ,
    Sorry about the delay in replying; got sidetracked trying to fix some FrameMaker 10 problems; on occasion, it laughs and crashes if we copy an element in a document and paste it to somewhere illegal.  This doesn't happen all the time, but it might be something someone might do, so it was interesting to know.
    Anyway, back to cross-references.
    In our r/w rules we have:
    "linkend" is fm attribute "ID";
    Can we also have a similar line under the cross-reference element as:
    element "xref"
         is fm cross-reference element "XRef";
         attribute "linkend" is fm property cross-reference id;
         attribute "role" is fm property cross-reference format;
    At the moment the second line is:
    .....attribute ID is fm property cross-reference id;
    I tried adding the attribute "linkend" is fm property cross-reference id; (so that I had both linkend and ID) bit but this made no difference.
    In general use cross-references work, in that it picks up data in one place in the document, e.g. WorldWideWeb, and repeats it elsewhere.   So in our xml file we have a link element with an attribute linkend which, when it's processed (ignoring the handshake code used to link the two - which could be something vague like 12345vvdog), repeats whatever is the target.
    Conversely, for a cross-reference, in xml they use an xref element which also has a linkend attribute (similar mysterious secret handshake behind the scenes) which is deemed to point to a list of references.   This looks like it might be the stumbling block in that it links to an area in the xml document which is used as an internally generated list of references.  Apparently this is only built when the xml book equivelent is finalised, so is not, like the link and linkend coupling described above.
    I've passed this back to the xml people, and they are investigating a different way of preparing their cross-reference to a list of references (I'm now thoroughly confused with all these references - good thing the weekend's just around the corner).
    I appreciate all you help and advice, I'll admit that this is a lot more difficult to understand than straight-forward EDD element creation along with their respective attributes.   Life used to be so much more simple back then!
    In sum, what I thought I was doing was allowing an ID attribute with a value of IDReference in my elements, this was deemed to allow for FrameMaker cross-referencing.   In Structured FrameMaker, on its own, this works just fine; it all fell flat on its face when trying to import xml.   I tried to see whether the xref element's ID attribute could also be a UniqueID, but as just about everyone has said, this is a silly idea.   I was just trying stuff to see whether it might make a difference - you'll not be surprised to see that it didn't!
    For the moment, I have attributes called ID with a value of IDReference, and I understand you're all suggesting to leave it at that.
    If I understand correctly, I could eventually use an IDRef attribute if I wanted a UniqueID value to be used, though I'm not sure what a UniqueID is used or useful for, so will file that for future use.
    Again, thanks for the advice and help.
    Chris

  • Cross references in structured documents

    Hi there,
    Perhaps someone of you has a tip for me regarding cross references in structured FrameMaker.
    The problem we have at the moment:
    We were working with FM8 structured. But - as we worked with FM documents most of the times - very often the xml files are not on the latest version.
    When we now want to update these documents with FM9 and save them as xml documents, there are lot's of errors that the attribute type is not defined for the element fm-xref.
    Perhaps some of you know this error message.
    At the moment we do exchange all those cross reference for new ones.
    Of course, when we have a xml document which contains the latest status, this is not a problem.
    You just open the xml file and save it as FM9 document. No problem with any cross reference...
    But what can I do with those FM8 documents?
    Would it help to use some application just for fixong the cross references in those (if possible)?
    This definitly seems to be an error in FM itself.
    Is there perhaps some fix for FM9 I don't know about?
    And how about FM10: Will I have the same problems, if we switch to that version?
    Regards,
    Anna

    Hi Van,
    I fear, I expressed myself not very clear. I try again.
    We have DITA structured documents. However, lastest status often was saved in the FM document. The xml documents often are not representing the final status.
    When I open the FM8 document in FM9 everything looks pretty good.
    But: When I want to save the document as xml with FM9, I'm getting errors regarding the cross references.
    The cross references which were created in FM8 - doesn't matter, if a valid xml document or a FM document - always look the same.
    (BTW: I don't think that in structured documents cross references always refer to elemts with a unique ID.)
    example from xml which was created with FM8:
    <xref href = "#id08B4A0R30E9" type = "fm:Chapter">"..."</xref>
    the only difference in the FM document is that the element is called fm-xref there, as it's not an external url.
    in FM9 those cross references are totally different.
    example from xml which was created in FM9:
    <xref href = "#id08B4A0R30E9" class = "- topic/xref">"..."</xref>
    When saving the FM documents with the cross references from the first example as xml in FM9 (we don't have FM8 anymore), I get an error that the attribute type is not defined.
    When having a xml document that was last changed with FM8 and opening/ saving this with FM9, there is no error.
    At the moment I do not know how to solve this issue.
    And also I'm not sure weather the same problem might accour again with change from FM9 to FM10 or else.
    It is a great effort to make new cross references just because we upgraded from FM8 to FM9. (And of course always at most inconvienent time.)
    As we are thinking of upgrading to FM10, it would be good to know before, if there are any similar issues to expect.
    Or if there is an fix for FM9 or FM10 to avoid this at all.
    Regards,
    Anna

  • Preserving Chapter Cross References when going to Structured Framemaker

    Hello,
    I am trying to preserve all of my cross references that link from chapter to chapter, within the same book. If I convert files one at a time, then FrameMaker has trouble finding the link in the destination chapter - because that chapter has not yet been converted to Structured FrameMaker.
    I have not tried Batch Processing, but I am sure I would get the same results.
    With that said, what must I do to these external chapter cross references, so that they convert over to Structured FrameMaker?
    Thanks in advance for your response.
    Regards,
    Jim

    Jim,
    Like Russ, I have had to redirect the cross-references manually following conversion; HOWEVER, I have also noticed that existing IDs in the unstructured version seem to get put into the converted element as an attribute. In other words, if my EDD defines a Title element with an Id attribute and the unstructured document contains a title paragraph that is the target of a cross-reference, then upon conversion the corresponding Title element has TWO attributes, one is named Id and the other ID. Id has no value, but ID does. The structured document does not validate and I have to delete the ID attribute to make it validate.
    This leads me to believe that had I named the attribute ID in my EDD, then it would be assigned a value upon conversion; however, I have never tried this. If I had, FrameMaker would likely create the Title element with two attributes, both named ID!!!
    Take it for what it is worth,
    Van

  • Display cross-references' linked documents filename in the xref panel

    Our company creates technical manuals consisting of five chapters, all named the same, except with a different prefix. For example the "ABC Widget" manual has an introduction chapter named "ABC 1 - Introduction", a safety chapter named "ABC 2 - Safety", etc. Many times I re-use documents for creating subsequent manuals using the "Save As" command. So the "ABC 1 - Introduction" chapter would be saved as "EFG 1 - Introduction" for the "EFG Widget" book. For all the internal xrefs it saves a whole lot of time since all of the xrefs are preserved. But for cross-document references it creates a problem. For example, if the "ABC 1 - Introduction" chapter has a xref to "ABC 2 - Safety", when I save the Introduction chapter as "EFG 1 - Introduction" it will still retain the xref to "ABC 2 - Safety".
    Right now, the only way to see if there are xrefs pointing to latent docs, is to check each one manually. If the xref panel displayed a column indicating the filename of the linked documents, I would be able to tell at a glance if that xref was pointing to the wrong document.
    Thank you.
    ID CS5, MAC

    Hi Van,
    I fear, I expressed myself not very clear. I try again.
    We have DITA structured documents. However, lastest status often was saved in the FM document. The xml documents often are not representing the final status.
    When I open the FM8 document in FM9 everything looks pretty good.
    But: When I want to save the document as xml with FM9, I'm getting errors regarding the cross references.
    The cross references which were created in FM8 - doesn't matter, if a valid xml document or a FM document - always look the same.
    (BTW: I don't think that in structured documents cross references always refer to elemts with a unique ID.)
    example from xml which was created with FM8:
    <xref href = "#id08B4A0R30E9" type = "fm:Chapter">"..."</xref>
    the only difference in the FM document is that the element is called fm-xref there, as it's not an external url.
    in FM9 those cross references are totally different.
    example from xml which was created in FM9:
    <xref href = "#id08B4A0R30E9" class = "- topic/xref">"..."</xref>
    When saving the FM documents with the cross references from the first example as xml in FM9 (we don't have FM8 anymore), I get an error that the attribute type is not defined.
    When having a xml document that was last changed with FM8 and opening/ saving this with FM9, there is no error.
    At the moment I do not know how to solve this issue.
    And also I'm not sure weather the same problem might accour again with change from FM9 to FM10 or else.
    It is a great effort to make new cross references just because we upgraded from FM8 to FM9. (And of course always at most inconvienent time.)
    As we are thinking of upgrading to FM10, it would be good to know before, if there are any similar issues to expect.
    Or if there is an fix for FM9 or FM10 to avoid this at all.
    Regards,
    Anna

  • Cross reference not working properly in epub exported from IDCC

    Hi,
    I'm not sure whether this is a known issue within ID so forgive me for bringing it up if it is. I couldn't find any satisfying answer on this forum, hence my question.
    It seems that cross references between the xhtml-docs created from split ID document during the epub export don't work properly. They link to the text anchors specified as relative links. My editor uses software compliant to many e-reader platforms that removes all the relative links between the xhtml files within any epub and replaces them by absolute hyperlinks (http://). The result is... broken links all over. Their specification asks for the the anchor entires in the content.opf file instead of the relative links. Is there a way to work it out in InDesign and have the content.opf file contain the navigation to the anchors in xhtml files within the epub?
    I'm working with IDCC 9.1 btw. Would appreciate any help...
    Kind regards, Kasia

    Hi,
       Not sure exactly where you gone wrong.
       If you want the running sum to start from beginning for each YEAR and each LINES. Use this
               =RunningSum([Sales revenue]; ([Year];[Lines]))   => Need Square brackets around Year and Lines. This forum site doesn't display square bracket correctly
       If you want the running sum to start from beginning only for each LINES (regardless of YEARS). Use this
                =RunningSum([Sales revenue]; ([Lines]))
       Not sure why you added ROW in your functions. Hope this help. Works for me, just tested using my efashion with the same structure are yours.
    Regards,
    Ken
    Edited by: Ken Low on May 9, 2011 8:15 AM
    Edited by: Ken Low on May 9, 2011 8:17 AM

  • How do I preserve cross reference text when exporting to XML?

    I am exporting my Framemaker documents to XML. However, when I open the raw XML, the reference formatting is obviously gone. So instead of seeing, say,  see Figure 6. I now see, see . 
    Is there some way to preserve this on export?
    Help would be much appreceated!

    Josh,
    The normal behavior is to have an empty element with the ID/IDRef markup that allows the xref element to be resolved again afterwards, by whatever post-processing step you put the XML through. The text of a cross-reference is a FrameMaker formatting artifact (not unlike a paragraph format, etc.) and is intentionally discarded during export. If you reimport the XML with the empty element, FM will re-resolve the xref, and then will restore the text using whatever format it originally had (the format name is also stored as markup).
    If you want to preserve the element tag of the xref, I don't think there is any way to preserve the text, unless you write an import/export API client. You could possibly use an XSLT stylesheet to repopulate the text in some cases, but this seems like a process fraught with many complications.
    If you do not care about the element tag, the manual says that you can just unwrap it, then you'll get the xref text. Here is a (rough) snip from the Structure Developers Guide:
    Translating FrameMaker cross-reference elements to text in markup
    You may not want your FrameMaker cross-reference elements to remain elements in the
    markup representation—you can choose to translate them to text instead. To do so, use
    this rule:
    fm element "fmtag" unwrap;
    where fmtag is the FrameMaker element tag for a cross-reference element.
    All of this does beg the following question, though... why do you want to do this, especially if the text is referencing figure numbers, page numbers, etc. that have no relevance in the markup? Normally, it is expected that preservation of the markup is the essential thing, allowing the text to be regenerated later by whatever process uses the XML (perhaps including FM). If you drop the element tag, the actual link will be permanently lost.
    Russ

  • Cross-Reference creation

    Hello to all!
    I am new to this amazing world of Extendscript but I have been using Framemaker since version 5.5.
    I am working on a kind of cross-reference manager and it works really nice. I can list all cross-references at book or document level, select the cross-reference to be shown in the current document and so on. I am using non-structured FM.
    The problem I am facing is the creation of cross-reference itself.I know how to create a Cross-Ref Marker for the Xref, but I don´t know how to insert the Xref into the content. I tried with NewAnchoredFormattedObject function with objType, format and textLoc parameters. Also there´s the XRefSrcText property (string containg unique ID:pgf_tag:text).
    The question is: Should I use the same string (the content of XRefSrcText) as text for the Cross-Ref type Marker? Or just the pgf text that contains the Cross-Ref?
    I have found several examples using Framescript but I am unable to replicate the code using ES.
    Thanks for reading me. I will appreciate any help on this.
    Regards

    Hi again Jang:
    I have been trying to create the XREF following your suggestions:
    First I created a XREF using the FM procedure. Then I created a code to get the info from Data Browser in the ESTK.
    Then I created a XREF using my own code: FM recognizes the XREF (as you can see on the right image) but I cannot get any cross-ref on the content.
    Here is the code for the Cross-ref marker target creation:
    var doc = app.ActiveDoc;
    var flow = doc.MainFlowInDoc;
    var pgf = doc.TextSelection.beg.obj
    var tLoc, marker, markerType;
    tLoc = new TextLoc(pgf, 0);
    marker = doc.NewAnchoredObject(Constants.FO_Marker, tLoc);
    markerType = doc.GetNamedObject(Constants.FO_MarkerType, "Cross-Ref");
    marker.MarkerTypeId = markerType;
    marker.MarkerText = "10978: Heading1: PREAMBLE";
    Here is the code I am using to create the XREF:
    var doc = app.ActiveDoc;
    var flow = doc.MainFlowInDoc;
    var pgf = doc.TextSelection.beg.obj;
    var oTLoc1=new TextLoc (pgf, 0);
    var format="Page";
    var newcrossref=doc.NewAnchoredFormattedXRef(format, oTLoc1);
    newcrossref.XRefFmt.Name=format;
    newcrossref.XRefSrcText= "10978: Heading1: PREAMBLE";
    I have tried with tons of modifications but without success.
    I hope you can help me!
    Regards

  • Cross-reference marker ID

    Hi everyone,
    Has anyone worked with duplicate cross-reference markers before?
    My question is, is the uique number in each marker text the same if multiple markers exist in the same location?
    Thank you for your help.

    You can find the markers by either doing it in a brute force manner using the Find > Marker of type (and have the Marker window open to see the contents) or by using a MIF version and using a text editor to search for the MText right after a <MType 9> entry. The MText would be the duplicate and the Unique ID entry would be two lines further.
    The general structure of a Marker in MIF is as in the following example:
       <Marker
        <MType 9>
        <MTypeName `Cross-Ref'>
        <MText `37042: Body: At vero eos et accusam et iusto odio blandit praes'>
        <MCurrPage `1'>
        <Unique 998385>
       > # end of Marker
    Cross-refs target the MText line using a <XRefSrcText ...> entry that is the same as the MText content.

  • Cross-References coming from Word in FM 7.2

    Hi Folks,
    I have a problem with the Cross-References. I create an EDD and Read/Write rules, and generate a conversion table. With it I'm converting all the my documentation in MS Word to Structured FM 7,2. It works well, but there two main problems that I can't solve. I spent a lot of time reading the Structure application Developer Guide, but I can't find a solution.
    First one is a minor problem that I can solve with a script but, maybe I'm doing something wrong on FM and it is easy to fix on the conversion table. When I apply the conversion table it generate without problems the RootElement, and apply tags for the paragraphs and Character formats, but I can't do that put other tags that are not related with text. I mean, my DTD need this structure:
    <book>
    <body>
    <heading1>xxxxx</heading1>
    </body>
    </book>
    and I obtain it:
    <book>
    <heading1>xxxxx</heading1>
    </book>
    I don't know if I can modify Rules, or EDD or Conversion table, to add the intermediate tag when use Structure Current Document
    Second one is a blocking one. I generate the XML with the tags and fix any problem on it. It works great and I obtain a XML :
    <book><heading1 Id = "i1003066"><bookmark
        type = "38548: Heading 1: 1. This is the title"/>This is the title</heading1>
    <paragraph>This is the text of the Title <reference Idref = "i1003066" type = "Page"/> and it bla bla bla</paragraph></book>
    But when I try to re-open the XML with my structured application I obtain a log error:
    "Error at line 17, char 31, Message: ID attribute 'i1003066' was referenced but never declared"
    and a warning about cross-references missing (they working before save it as XML). File open and all is fine, except that references are missing and when I try to update the Reference dialog box to find other file is open with this message:
    1 Unresolved Cross-References to File: Current
    And ask me to find the "Current" file where point the reference. All the references in the document appears missing.
    Must I have two set of files, one FM for generate the PDF, and the XML for generate the help with my XLS? It is not possible re-open the XML on Framemaker and don't lost the references?
    Thanks for your help.
    Regards,

    Hi Van,
    You wrote:
    >>  You need to DELETE "Xref"  . . . This states that the reference element is a Frame cross-reference element;  you should not include another name.
    That may or may not be true. If the element names are different in the XML (DTD) than FrameMaker (EDD), this is the mechanism by which you translate names. It may be that in this case, the EDD element name is Xref, but the DTD element name is reference.
    You also wrote:
    >> Maybe this will help clear things up, but it may be unreasonable to expect that cross-references in Word will translate cleanly to structured FrameMaker.
    In this case, I couldn't agree more. Esperanzas, I would recommend that you limit your faith in the conversion process, because there are many variables that will likely get mistranslated. Unless you are willling to do some programming with the FDK to clean up afterwards, I would expect that all cross-references should be recreated manually after import.
    Russs

  • FrameMaker 11 trial version crashing on save and cross-reference insertion

    Hi everyone,
    I've recently started a new position. My prior background was heavily DITA, and I'd describe my FrameMaker experience as late beginner or early intermediate. The new position uses FM exclusively though, so I've been on a steep learning curve lately.
    I'm using the trial version of FrameMaker 11, downloaded about two weeks ago, until the PO for my full FM 11 license is processed. I'm working in book and document files that have been upgraded, I believe, from FM 9 to FM 10 and then from FM 10 to FM 11. All of my colleagues are still using FM 10, with a mind to upgrade to FM 11 in the spring as our new budget comes through (I am, so to speak, the FM 11 guinea pig for the group).
    My workstation is a brand new HP Elitebook laptop running Windows 7 64-bit (I believe our IT department downgraded it from Windows 8). Windows is fully up-to-date. My trial version of FM 11 is 11.0.1.382 and also up-to-date as of this message.
    My issue: FM 11 randomly crashes several times a week, sometimes once a day or so, sometimes when I try any of the following:
    Saving all files in a book (using Shift + the File menu command)
    Saving individual document files (generally using the Save icon in the tool bar)
    Attempting to insert a cross-reference (placing the insertion point within the document, then opening the Cross-Reference tool in the right-hand side bar)
    The crash takes the appearance of FM freezing for several seconds, then the dreaded message window opening with the words "FrameMaker has detected a serious error and must quit", with columns of error codes below.
    I've googled and binged and not found anything for this issue in FM 11, so I thought I'd post here. I have tried the following, based on somewhat similar discussions I've seen for crashes in earlier versions of FM)
    Mif-washing the files
    Working in the Structured FrameMaker interface instead of the Unstructured
    Neither of these has worked. FM 11 trial continues to crash. It doesn't happen often; I'd say that I'm able to successfully able to perform the above tasks 20 times or so, with the crash on the 21st. But on a busy day, that's a few crashes a day.
    To mitigate damage, I have autosave set to every two minutes and gotten in the habit of only having one or two documents open, instead of all in a book, to minimize the number of recovery files I need to process.
    After one of the initial crashes, I did as Adobe asked and forwarded the crash report to them for troubleshooting.
    My colleagues are watching all this very closely, and my troubles might influence our decision to upgrade from FM 10 to FM 11. So any insight into this issue would be appreciated!
    Cheers,
    Eric

    Eric,
    The multitude of unesolved x-refs may due to the font issues when updating the book. During an update, if the files aren't open, FM tries to open them in the background but if it encounters an error like a missing font, it skips the file and then any x-refs to that file are unresolved. This can cascade to make things look really worse than they are.
    What is your default printer when you start FM? It should be the Adobe PDF prnter instance. If not, then you might want to insatll the Sundorne SetPrint utility (http://www.sundorne.com/FrameMaker/Freeware/setPrint.htm) thta will automatically set this for your FM sessions only.
    One other place where fonts can hide is in table definitions. The catalog stores the font information (and not just the explicit paratag) of the cells in the header and first row. As Jeff mentions, you need to check the MIF file in detail. An excellent tool for quickly browsing your MIF is Graham Wideman's Mifbrowse (http://www.wideman-one.com/gw/tech/framemaker/mifbrowse.htm).

  • Changing cross-reference formats - what do my options mean?

    Hi all, using TCS2 on Win 7 64 bit.
    I have a question about changing a cross-reference format. I have one that is "<paratext>" right now - the " included. So my xref says (for example):
    For more information, please see "Appendix 1".
    I want to change this to that it doesn't show quotation marks anymore. I know the HOW of doing this, my question is once I have made the change, a dialogue box appears asking me which cross-references this change should apply to. My options are:
    Internal Cross-References
    References to All Open Documents
    References to All Documents
    I don't know which one I should chose. I am working in a book structure that has a bunch of FM files imported to form chapters. Each file file uses this old style xref so I need to update the xref format in each file (I think I need to do this one by one) and in some instances my xrefs are within the same doc, sometimes they are to other files within the FM book. So I think I need to pick 'References to All Documents' but it says there is no undo so I'm seeking advice first!
    Many thanks in advance,
    Adriana

    adrianaharper wrote:
    Hi all, using TCS2 on Win 7 64 bit.
    I have a question about changing a cross-reference format. I have one that is "<paratext>" right now - the " included. So my xref says (for example):
    For more information, please see "Appendix 1".
    I want to change this to that it doesn't show quotation marks anymore. I know the HOW of doing this, my question is once I have made the change, a dialogue box appears asking me which cross-references this change should apply to. My options are:
    Internal Cross-References
    References to All Open Documents
    References to All Documents
    I don't know which one I should chose. I am working in a book structure that has a bunch of FM files imported to form chapters. Each file file uses this old style xref so I need to update the xref format in each file (I think I need to do this one by one) and in some instances my xrefs are within the same doc, sometimes they are to other files within the FM book. So I think I need to pick 'References to All Documents' but it says there is no undo so I'm seeking advice first!
    Many thanks in advance,
    Adriana
    Internal means only within the current document. All open, and all, are self-explanatory.
    Your question shows that you're not sure what will happen when all instances of the cross-references that use the format are changed, either because you can't remember what you created in your own book, or because you're working on a book created by someone else, or that you collaborate on with others.
    Don't let "no undo" scare you off. You can undo the result by saving all the files, before you do the changes. From within the book window, hold Shift while clicking the File menu - Save changes to Save All Files in Book. Or, from within any open file, hold Shift while clicking the File menu - Save changes to Save All Open Files. After you save the files, performing any non-undoable operation like changing the cross-reference format only makes the changes, but doesn't save the affected files. These actions are undoable by holding Shift while clicking the File menu again; from within a book window, Close becomes Close All Files in Book, and from with an open file, Close becomes Close all open files. When prompted to save, click Don't Save. Alternatively, from within each open and changed file, File > Revert prompts for confirmation, and if you choose to continue, the last-saved version of the file reopens.
    If you want yet another safety layer, copy the whole file structure that will be affected to a safe location. If the set of assets is sprinkled all around the system, Bruce Foster's inexpensive FM plug-in "archive" will copy the whole collection into one place: http://home.comcast.net/~bruce.foster/products.htm.
    HTH
    Regards,
    Peter Gold
    KnowHow ProServices

  • Cross-References Broken In RoboHelp 10 Output

    We are using FrameMaker 11 to author our documentation. We have some cross-reference links that do not work when the FrameMaker book is imported into RoboHelp. Upon import, the href information is not included in the link in the HTML code. The text looks like a link, however. When the help is generated, the text is not a link.  The following is an example of a non-functioning link:
    see <a>Link</a>.</p>
    Here is an example of a cross-reference that is functioning correctly:
    <a href="#XREF_90399_Heading_Text">Link</a>
    There are no errors in FrameMaker. The cross-reference is updating correctly in FrameMaker. In addition, when a PDF is made form the same book, the cross-reference works in the PDF.
    Troubleshooting steps I have taken:
    I have tried going to MIF and back for both the source and target documents.
    I have recreated the cross-reference and marker.
    I have tried linking to a heading cross-reference marker, as well as a manually create cross-reference marker.
    I have renamed the file.
    I have renamed the marker.
    I have used different cross-reference formats.
    I recreated the file by copying all the text to Notepad and pasting the text back into a fresh FrameMaker file.
    None of the steps I have attempted have corrected the issue for the cross-reference I focused my troubleshooting on. I hope that someone can point me in the right direction to correct this issue.

    I have been trying everything I can think of to move the files around to resolve the issue. 35 characters is very disappointing. Is this for the file and cross reference or the whole file path? I am not sure how you are going to be able to link from one Framemaker file to another, including a cross-reference name (especially when you can use heading for the cross-reference name) with a limitation like this.  We also have a large library with many directories. We utilize single sourcing, so some files are in completely other directories from the file that is cross-referencing to it. From what you are telling me, it sounds like we no longer have the ability to use cross-references from one file to another in our library structure. Are you saying that all cross references basically need to be in the same file to allow cross references to work properly in RoboHelp? We moved from a WebWorks solution and we never had any issues with our links.
    What I don't understand is the marker is in the destination file in the converted RoboHelp files, but the link is completely missing the <a href="#XREF_name ofmarker"> code in the cross-reference link. When I go in and manually link the cross-reference in RoboHelp, it works. This seems like a bug. I think having a 35 character limit on a filepath, filename, and cross-reference name is not going to work for anyone that has any sort of complex directory structure with multiple authors, sharing content and since it isn't a limitation of HTML, I don't see why this functions this way. Manually linking isn’t a reasonable option for us. We have a publishing system that publishes all of our output. We have hundreds of files that are generated automatically.

  • Cross references in custom XML

    Hello!
    We have a custom XML schema and a structured application that allows us to edit our XML documents in FM. The schema contains a definition for a cross reference element and a definition for a target element.
    =============================================================
    Example:
    A cross reference element (say, documentA.xml contains this element): <cref target="documentB.xml#sect123"/>.
    A target element (say, documentB.xml contains this element): <section id="sect123"/>.
    Also I have a book in FM that includes both documentA.xml and documentB.xml.
    =============================================================
    FM outputs error messages when I try to save documentA.xml.
    So, I have few questions concerning this issue.
    How should I describe the cref element in EDD?
    A manual says, that the @target attribute must be of the IDREF type. Sounds good but the # char is restricted for IDREF values. How can I resolve this contradiction? If I write <cref target="sect123"/> (target id without filename) FM outputs error messages when I open documentA.xml in FM.
    Thank you!

    Dear Russ,
    Thank you very much for the answer. I'm sorry for my replying you with a delay,
    To make long story short, now it's OK: we can load a document with cross references to FM as well as we can save it form FM. Thank you once more.
    I'd like to make some comments that might be useful for other readers of this forum.
    As far as I understand the Structure Developers Guide mostly describes import/export transformations between an XML format and the FM format. But we never convert XML files to FM files and vice versa in our application. We open an XML file in FrameMaker, we edit the XML file in FrameMaker, and finally we save the XML file from FrameMaker. So, while reading the Guide I had a permanent doubt if import/export is the case I deal with.
    After several probes and attempts we found out that the following format of cross reference is appropriate for our application:
    <xref srcfile="fm-properties.xml#sys_psnt_part_number" format="CrossReference"/>
    (We found this type of cross references on page 399 of the Guide).
    The xref element must have an attribute of the IDREF type defined in a schema and in an EDD even while we don't use it. This attribute may actually be omitted in an XML file but we had to define it for xref.
    The root element of a target XML document must have an attribute of the ID type even while we don't use it.

Maybe you are looking for