Crashing with cross-references

We are still crashing when trying to work with cross-references. Running CC 9.2.1. Is another update coming to fix this?

We are having the same problem.  Whenever we open a file that was created using Cross References Pro, in a previous Indesign CS version, InDesign CC crashes immediately.  I have installed all of the recent 2014 updates, and the problem continues to happen.  The Cross References Reader will not install on my system, as I only have InDesign CC now, and it will only install on systems with up through CS6.
Please find a solution ASAP, as we cannot open our old documents to make any changes or reference the links.

Similar Messages

  • Problem with cross reference

    Hi,
    This is my first post.
    I was getting behind on a particular project so my boss asked me to commission a design agency to complete work being done on some prospectuses I started designing.
    The agency did their bit and sent the Indesign files back to me but the cross references I create do not work properly. The cross referenced page numbers just wont show.
    I have tried copying the text frames to new documents and the cross references work. It's as if someone turned off a switch in that particular document.
    There are 13 individual documents in all, each with a minimum of 20 pages, which I intend putting together using the Book panel - so its important the cross references work.
    Please see the last lines on pages 2 and 3 of the attached document. the 'please see pageXX' is what I mean. these are pages from the rogue document.
    Any help/suggestions will be appreciated.
    Thanks
    please download the sample indesign file using this dropbox link
    http://dl.dropbox.com/u/80149652/sample.zip

    I don't know exactly what is causing the problem, but I can definitely see it in Story Editor.
    In the screen cap below, the story editor windows on the top row are your file, and the bottom row are a new file with your text pasted in and new cross-ref added. Note the differnce in the tags:
    I cant find any casue for the difference, and I don't know what the defective tag is all about. I thought perhaps it was related to a third-party x-ref plugin, but I don't see any sign of that, either. I'm stumped, and the pragmatist in my says copy and paste and move on for now, but save a copy for further exploratin when you have time.
    And ask the other agency to tell you what they did and if they use any third party plugins.

  • Trouble with Cross-References

    FM11 / DITA 1.2
    What could cause a particular cross reference to consistently NOT work? I know that's vague. I'll try to give a more specific example:
    Let's say I have a collection of xrefs across several XML files in a DITA map. Some xrefs might even point to the same item (usually a <title> tag with an ID attribute). On output to a book with FM components, particular xrefs just will not work (they output as "unresolved"). I can fix it manually in the FM file, but I'd rather it work correctly in the first place, especially since I deal with translation in to several languages, and if I can't get an xref to just work, I have to fix it many, many times.
    I've tried deleting the xref and starting again; I've tried changing the ID attribute in case there was some kind of conflict...I still have trouble with that particular xref (and this happens with more than one xref). What else can I try?
    Again, I know this is vague. I'd be happy to elaborate on relevant points. I just don't currently have time to write a massive description and I want to get this question out.
    Thanks in advance.

    Hi ohnehosen...
    Are you up to date on your FM11 patches? It's hard to say what could be causing this problem .. does sound strange.
    While this shouldn't be the problem, you might try linking your xref to the container "topic" element (topic, concept, task, whatever is the immediate parent of the title you're pointing at). While in theory you should be able to xref to a title, that's not really the intent, your cross-ref is referencing a "topic" not the title within the topic. The same goes for a figure or table, you reference the fig or table element not the title within those elements.
    I'd assume that the code in the FM-DITA plugin was designed to work by referencing the container ,it probably wasn't tested the way you're doing it, and there may be some flakiness that would cause this to not always work.
    Give it a try .. let us know how it goes.
    …scott

  • Can this be done with Cross References?

    My document has 10 figures (photos, e.g.) with corresponding cross references in the text. Due to a series of changes, I now need to delete Figure 5. The old Figure 6 now needs to be Figure 5, the old Figure 7 needs to be Figure 6, etc. And the corresponding text sources need to update as well.
    Is this possible with InDesign's built-in Cross References feature? If not, is there a plug-in out there that could solve my problem?
    Thanks.

    Are you asking how you could set it up in the past so that in the future you could automate the process? If so, yes. I'm doing a book with a slightly similar feature. But it only handles the actual text in the ID document. It doesn't handle changing the names of the photos that have been placed. So if you need to rename the placed PSD files, I can't help you.
    But, if it's text only, here's what I'm doing.
    My figure captions are numbered lists. The format is "Figure #" and then the text. They have been set to run across stories.
    When I x-ref the figure, I have the x-ref set to pick up the number of the paragraph but not the actual text of the paragraph.
    If, in your example, I were to take out figure 5, I would take out the figure photo and caption. This would leave a missing x-ref in the body text. That's fine. I would delete it. Then all the rest of the x-refs would need to be updated.
    Similarly, I could insert an x-ref. I believe the auto number would come from its position on the pages of the text.
    HOWEVER, you would need to have set this up initially. It won't help afterward.
    PS: I hope you're asking this for the future and for many more than just 10 figures.

  • Updating numbered Cross references crashes InDesign in both CS6 and CS4

    I have a large medical journal that has over a hundered references, which I cross-referenced with the thinking that the client may well insert or amend the refernces. I was correct and now the customer has several references to go in I have updated the first in its numbered list at the end and gone to "update cross-refernce" and InDesign crashes. I have tried this in CS6 and CS4 but both crash.  

    This happens often, particularly with cross-references across documents that are managed with an InDesign book file. One common suggestion, in addition to updating the installed software with the latest patches, is to open all the files in the book before updating; this may or may not always succeed. Search this forum for cross-reference crash to see other suggested solutions.
    Some of those posters may mention the commercial third-party Cross-References Plug-in for InDesign, from dtptools.com, and the poster's experience with it. It is reputed to be much more reliable than InDesign's built-in cross-references. It includes an option to convert the ID cross-references to its own, and that's reversible. There's a free trial. There's also a free reader plug-in for users who will need to open and edit documents that contain the plug-in's cross-references. The reader plug-in permits users to edit content in the documents without affecting the cross-references. HOWEVER, to edit or creatge new cross-references, users need the full plug-in.
    HTH
    Regards,
    Peter
    Peter Gold
    KnowHow ProServices
    mccoole1 wrote:
    I have a large medical journal that has over a hundered references, which I cross-referenced with the thinking that the client may well insert or amend the refernces. I was correct and now the customer has several references to go in I have updated the first in its numbered list at the end and gone to "update cross-refernce" and InDesign crashes. I have tried this in CS6 and CS4 but both crash.  

  • Cross-reference to chapter in book

    I have an eighteen-chapter book, where all the figure numbers, table numbers, and the first- and second-level numbered headings are prefixed with the chapter number.  It would be a nightmare if (as is possible) the chapters were to be reordered later in the day.  So I put each chapter in a separate ID document, put all the documents in a book, and made liberal use of the 'Chapter number' text variable.
    My question is: what do I do with cross-references like 'See Chapter 9'?  How can I treat these so that they will automagically update if Chapter 9 gets moved to become Chapter 13?  As far as I can tell, using the cross-referencing feature doesn't work with text variables, so I can't just point it at the chapter number at the beginning of the relevant chapter (which is, once again, the 'Chapter number' text variable).
    Any ideas?
    Also, slightly irrelevantly, I notice that InDesign is prone to crashing if I try and cut text containing a text variable.  Is there a known bug?

    I have an eighteen-chapter book, where all the figure numbers, table numbers, and the first- and second-level numbered headings are prefixed with the chapter number.  It would be a nightmare if (as is possible) the chapters were to be reordered later in the day.  So I put each chapter in a separate ID document, put all the documents in a book, and made liberal use of the 'Chapter number' text variable.
    My question is: what do I do with cross-references like 'See Chapter 9'?  How can I treat these so that they will automagically update if Chapter 9 gets moved to become Chapter 13?  As far as I can tell, using the cross-referencing feature doesn't work with text variables, so I can't just point it at the chapter number at the beginning of the relevant chapter (which is, once again, the 'Chapter number' text variable).
    Any ideas?
    Also, slightly irrelevantly, I notice that InDesign is prone to crashing if I try and cut text containing a text variable.  Is there a known bug?

  • Cross Reference Sources appearing in Story Editor view but not appearing in the Cross Ref pane

    I have imported a Word document containing working cross references into an InDesign document. The vast majority of these cross references import correctly and link to their destinations within the document, however there are some that are not working. If I view the text frame in the story editor view, I can see these "broken" cross reference sources that came in from the Word doc but on selecting them I can see that there isnt a corresponding entry for it in the cross reference pane. As said, there are only a few that are behaving like this.
    What could be causing these not to appear in the cross reference pane?
    Obviously as they are not appearing in the list of cross references I can't update them, and also, as they are technically broken cross references, because a source exists for them but there is no corresponding entry in the pane, then on export to epub, InDesign crashes (If there is one broken cross reference in a document, export to Epub will crash indesign).
    Also, to clarify, in the Word doc if I navigate to a cross reference that is failing once in InDesign, I can update it properly, and also navigate to its destination in the Word doc, so it's not as though these cross references are broken before coming into InDesign. Also I believe the destinations for these "broken" cross references are coming across properly to indesign too as I can see them in the story editor view.
    Supposed Cross Reference source selected in Story Editor view on left, but no corresponding cross reference highlighted in pane on right:
    Technical Details:
    InDesign CS5.5 - Version 7.5.3
    Microsoft Word 2010, File type .docx

    I have found the possible cause of this problem!
    If a table is used within the Word document somewhere between where the cross reference source is and its destination then that particular cross reference will be broken as described above in my initial post.
    So the "fix" is to remove any occurances of a table in the Word document and the cross references come into InDesign perfectly. This is actually not a fix at all. I need to use tables in the Word document for layout purposes so if they break cross references if they stand between them and their destinations then I have to compromise, i.e. use tables but with no cross references in the document or vice versa.
    I found a similar issue recently with index markers in Word causing a shift on the cross reference tags when bought into InDesign. The "fix" again for that was to remove all index markers from the Word document. See post about this here: http://forums.adobe.com/thread/1043981
    InDesign really needs to sort out the issues with importing of Word documents with cross references in them. If I can't use index markers and tables in a Word document without breaking its cross references then they can't claim to have the ability to import a Word document while maintaining its cross references into an InDesign document. It just doesnt work as ive painstakingly proven.

  • Cross references corrupted after placing Word document into an InDesign document

    I am placing a word document which contains cross references to headers and captions/figures within the document. They seem to be fine and function correctly in the Word document, however, after I place this word doc into my InDesign doc, I take a look at the cross references panel and notice that the cross references have been corrupted. It is wrapping the wrong portions of text from the cross reference destinations. See screenshot for a visual of how the cross references are malformed. For example the 7th cross reference in the list should say Framework Details, not "Framework Detai
    InDesign Cross References Panel - showing malformed bits of text
    Another visual of this issue can be seen if I view the text frame in Story Editor view, see below. You can see that the cross reference source tags (blue arrow like symbols) are wrapped around the wrong portions of text. The blue tags shoud be wrapped around Framework Details and 52
    InDesign Story Editor
    You can see below as to why I think the cross references are fine in the Word doc, you can see the same cross reference I used in the example above in the word doc and it is wrapping the correct portion of text:
    Word - showing cross reference is formed corerctly
    Why is this not being maintained after placing this file into InDesign?
    Also I am not performing any cross reference updates after I import, this problem occurs immediately after the place of the doc.
    Why would InDesign be having difficulty in importing these cross references? I have set up a simple test Word document with cross references to headers and figures in and they have imported fine. What could be wrong with this other particular word doc that would be causing this "corruption" of cross references? This is not only causing my cross references to break visually and lack the update capability but also I cannot export the InDesign doc to an ePub as it keeps crashing. I believe from my reading on the web that if there is only one broken cross reference source i.e. the cross reference destination that it is trying to link to is missing, then the export to epub will fail. So this is causing a massive headache for me at the minute.
    Is there anything I could be looking at in the Word doc to try and figure out why the porblem is occuring in the first place?
    If anyone has any tips or a possible solution to this I would really appreciate it. Even better if someone knows the reason why this is happening I can tackle it from the source and prevent it happening time and time again.
    Thanks, Dave

    Only bad experiences, Peter ...
    I've seen this character shifting before on numerous occasions, both with cross references and with hyperlinks. (It's especially funny with hyperlinks, 'cause you can see that the outline box shifts one character at a time per each next link...)
    The thing is it's not just limited to hyperlinks and cross refs. Dave's screenshot doesn't show bold, italics, or other local formatting, but it's a fair bet these are off by a couple of characters as well.
    Dave's experiment of making a "minimal" Word document to confirm it's a persistent bug didn't work. I found the same thing: either a document comes in fine, or everything is foo-bar right from the start. There must be some internal Word code that InDesign forgets to count as 'a character position'. Without delving into the Word file with some very advanced tools, it's anyone's guess what code that would be.
    I can only offer the one solution that works for me: in Word, remove all hyperlinks (which is what Word uses for internal links as well as for external ones) and convert all cross-references to text. Then, if the file finally imports fine, re-build them in InDesign. It's a cumbersome workaround, but slightly better (only just) than checking each reference, delete, rebuild, check next -- etc. (And with that the chance that your other text attributes are also off.)

  • Cross-references to hyperlink destinations (text anchors) results in file slowdown

    I'm using text anchors for the first time in a 12-file book (~280 pages) for the table/figure list in the front matter. There are maybe 100 or so total cross-references in the front matter in tables (where one column is the text of the figure title and one column the page number).
    About halfway through the process of adding the cross references, things got reallllly slow, and only in that one document. So slow that reformatting became almost impossible, because of the delays.
    So I went through many of the usual troubleshooting steps, just in case. Trashed preferences, trashed the style, etc. I exported the file to IDML and created a new file from that. It helped, but I can tell that it's still not quite so snappy.
    My question, then, is if this is to be expected with what may be a large number of hyperlinks/text anchors? All the other files in the book act fine, so it's not an InDesign-wide slowdown. Are there any best practices when it comes to using hyperlink destinations?
    As an amusing aside, before I tried the troubleshooting steps I had a clever idea--to insert the cross references into a new, blank document and then paste them into the frontmatter file. Consist and ugly crashes to desktop resulted.

    George Krompacky wrote:
    Peter,
    Thanks for your reply. Yes, the TOC could do this and would be an easier approach. But I hadn't anticipated using it and so didn't have my ducks in a row as far as having the styles consistent for chapter titles, figures and tables. Next time I will do so. I can guess that as a TOC doesn't generate live links, it shouldn't have a performance impact like dozens of cross-references do.
    Yes, the TOC is inert except when it's being generated.
    Regardless of how "creatively chaotic" or "chaotically creative" your chapter, table, and figure title paragraph styles are, as long as all chapter titles are tagged with style names that are not used for figures or tables, and similarly figures and tables are not tagged with styles used for the "other," you can still generate a usable TOC. The idea is to capture all the paragraph styles for each category, and display each category's captured paragraphs as uniform TOC entries - i. e., all chapter title entries are the same, all table title entries are the same, and all table title entries are the same. If you don't want the categories intermixed, create a separate TOC for each category, place each TOC separately, unthreaded to other document frames.
    If you'd like to try a few things to see if it's possible to quickly remake the TOC and regain a responsive working document, before doing anything else, save the whole project to a secure place, and work on the copy. Then:
    * Move the Text tool insertion point to each cross-reference's destination by selecting the reference in the cross-reference panel and clicking  the right-pointing arrow on the panel status bar; then verify that the paragraph is tagged with an appropriate style that doesn't belong to the other category of TOC items.
    * After all the TOC-to-be items are identified and verified that they're tagged correctly, delete the text frame(s) that contain the TOC that's created with cross-references. All the references will break, of course. You've got the secure original project somewhere, right?
    * Set up the TOC roughly; just pick the paragraph styles for each category - chapter, figure, table, and generate a TOC for the book. Drag to place the TOC on a clean new page, and DO NOT THREAD THE TOC TO NON-TOC TEXT FRAMES.
    * If the extracted paragraphs are in their correct categories, you can create new TOC styles for the TOC entries, or, if they exist, assign them in the TOC setup dialog box, and regenerate.
    If this result gives you a sense of what needs fixing, and you have the time, refine the TOC styles so you can get the exact appearance you want. By avoiding changing the source paragraphs in the main document, you'll avoid any risk of reflowing anything. Finally, after the project's completely done and handed off, you can spend time refining the rogue source paragraph styles, IN A COPY, for use going forward.
    HTH
    Regards,
    Peter
    Peter Gold
    KnowHow ProServices

  • Cut and Paste Cross References

    As some of you know, I'm updating a book composed of chapter files, with cross references between chapters. This used to be incredibly buggy, with crashes and broken references common. Some of that is improved in CS5.5, but a couple of big issues remain, and I'm wondering if anybody has any suggestions.
    Two problems:
    You generally can't cut and paste a cross reference. I have text that says "see page 27". I want to move this somewhere else in the same document. Cut it. Paste it. The paste comes in looking like this: "see <?>" -- and you get a broken link in the Hyperlinks panel. That really limits text editing. It doesn't always happen. Sometimes you'll paste and your cross reference works. But that's rare. And you can never copy and paste. That always breaks.
    Cross references refer to absolute file pathnames. I'd like to rename some chapter files. But I dare not because I assume that all cross references to destinations in those files will break.
    Anybody have any suggestions for either of these things? Number 1 is a real work-stopper right now.
    Many thanks,
    Steve

    Okay, guys -- I've made some progress. And I really appreciate your support, now, and in the past.
    Upgrading from 7.5.2 to 7.5.3 -- no improvement,
    Save a new copy of the file via Save As -- no improvement,
    Export as IDML and then just double-click the IDML to open it -- worked! (Is that the correct procedure? Anything else I need to do?)
    It's still just about suicidal to try and edit text in any story containing multiple cross references to chapter files that aren't open. And adding a new cross reference is super-slow, during which time you're sure you're going to crash. But with the imported file, the new cross ref held.
    One other point of confusion: new cross references display differently than ones created in older versions of the software. The old ones have dark grey boxes around them. New ones have light blue boxes. No mention of this in the help file that I could find. Even if you update an old cross ref, the dark grey remains. Only starting from scratch produces light blue.
    Something corrupted that file, which IDML got rid of. It was corrupted by doing little more than adding or updating a bunch of cross references, and doing some minor text editing. No images in the file, so that had nothing to do with it.
    Chapter file sizes, since you asked, are anywhere from 3 to 40 mb. The file I was having problems with is only 2.5 mb. The book contains 22 chapters. Long ago I converted it from one big file to separate chapters. Easier to manage, chapter numbering works more logically and chapter starts are easier to handle. But cross references worked a lot better with the single file.
    In any event, problem solved for the moment, so thanks very much again. But Adobe really needs to look at this. It's been broken for way too long.
    Steve

  • Cross references not picking up character styles in source text

    I'm getting some annoying odd behaviour with cross references in Frame 12.
    I have some tables, where the paragraph style in the cell is called "Cell Body" (nothing odd there).
    Quite a few of the cells only have one word in them, and that word is set to courier font with a character style (called "Code").
    Then, elsewhere in the document, I am referring to this text using cross references. I am referencing the paragraph style Cell Body, and the cross reference format applied is like this "<hyperlink><$paratext><Default ¶ Font>"
    "hyperlink" is another character style that makes the text go green.
    So, the cross reference out to take the text from the cell (in Courier) and reproduce it, coloured green.
    However for about half of these cross references, it isn't picking up the Code character style in the source text, so the cross ref is just green, no green courier.
    Things are further bamboozled when I output to HTML Help.
    In the CHM file, the cross refs which appear to work OK (green courier) are now just courier.
    The ones which failed to pick up the courier look the same as they do in Frame (just green).
    Any ideas as to what's going on?
    I've tried troubleshooting by clearing the cells, reapplying the para style and default character style, then reapplying the code character style, then replacing the cross reference - which sometimes seemed to fix it but didn't always.

    Arnis Gubins wrote:
    Using two character tags in-line together (a la <hyperlink><Code>) is asking for trouble. IIRC, FM doesn't re-apply these in order on an update and depending upon how they are defined (and what is set to AsIs), the outer one usually wins. .
    So why does the blimmin' dialog invite me to do precisely that, by providing me with a list of all the character styles I have, and allowing me to select as many of them as I like??? /sulks/   Indeed, if Frame still shipped with a printed user guide instead of  stupid "optimised for viewing on iPhones" online webhelp nonsense, I suspect I might very well be able to find an example in the manual of using multiple character styles in that dialog!  If it doesn't want you to use more than one, why doesn't it grey out after you add the first one? /sighs/  The concept is called "cascading styles", it's a fundamental web paradigm! And it works in the main body text - why not in Xrefs!
    Also, I have been very scrupulous to keep my character styles orthogonal so none of their AsIs's mash each other up.
    But, rant over, I shall follow your splendid suggestion for a "Code Hyperlink" style.
    Arnis Gubins wrote:
    Also, x-ref formatting may behave differently in the new Publishing modules depending upon ....
    ...Depending on how badly designed and buggy this new Frame12 feature is, I should say!   The Publish module should not randomly stop behaving in a WYSIWIG manner in completely undocumented fashion just because Adobe couldn't be bothered to code it properly.  /sighs/
    Frankly, for my current project, I've given up trying to jump through hoops for Publish - I'm concentrating on getting the Frame source right and assuming these quirks will be fixed in Frame 13 (or 14, depending on how superstitious they are). Because if I put in ad hoc workarounds for them in Frame 12, I (or a colleague) will only have to undo them later when they're fixed, and by then we'll all have forgotten what the original problem was.

  • Cross reference markers are deleted for content in text insets

    Cross reference markers are deleted for content text insets. I currently have a chapter that is built from several Import by Reference files. I added an introductory paragraph with cross reference links to heading 2 titles in these text insets. Everything works and saves normally, although the cross reference markers disappear from the chapter when files are checked out a few days later. An extra Heading 2 is also added to the end of the document.
    Steps to reproduce:
    1. Create a chapter composed of several text insets.
    2. Create a list of cross references to headings in these text insets at the beginning of the chapter.
    3. Check in/check out the files from a source control product.
    What went wrong?:
    The cross reference markers are gone, resulting in broken cross references. An empty Heading 2 is also added to the end of the document following the final text inset
    What should have happened?:
    The markers should remain and the heading 2 tag should not be applied to the document.
    Product version:
    Product: FrameMaker
    Version: 7.2
    Platform information:Windows XP
    Hardware: Dell Latitude D620
    OS Version: Windows XP Professional Version 2002, Service Pack 3.
    RAM: 1GB

    Thanks for the information, Van. We did try several techniques including adding the insertion point immediately after the text inset before the normal paragraph tag, but none seemed to consistently work. I will investigate this scenario futher, though, in light of your comments.
    We have managed to determine a workaround for this issue by avoiding a string of text insets. For some reason, using multiple text insets without separating them with normal text causes most of the problems after we add the files to our source control system. The situaton is not ideal, but it does work for the time being anyway.
    Steve

  • Cross references from a word file

    I've already read on this forum Indesign (CS6) has problems with cross references in Word files. (I mean dynamic references like "see page/paragraph/chapter x".) Whenever I see them, I just delete them in Word and update them manually in the final draft. (By the way, as a standard, I save Word files as Word 97-2003.)
    The problem is (luckily, I should say), this Word feature is hardly used, so for the book I'm working on, I forgot to check.
    I only noticed when I had worked for a full day on it in Indesign. The next day I could't open the Indesign file anymore. Well, **** happens, so I started anew. Next day, same problem, so I contacted the Adobe helpdesk; they couldn't reopen the file either.
    Third try. Now I made copies before closing the document, first testing if I could reopen them. I already had guessed these cross references were the problem. They appeared as a tiny blue double dot in the text (a bit like the upper half of the marking for index codes). I couldn't find a way to search for them, so I searched the Word file for field codes and removed them manually in the Indesign file. All of them, I thought.
    I closed it and reopened it a few times, no problem. No need to check anymore and first make a copy, I thought. I sent a pdf of the first draft to the author, processed his corrections, closed the document.
    The next day I couldn't reopen it.
    Now I'm not the kind of guy that gives in too easily, but before I start doing this book for the fourth time, I would like to be sure it will be the last time. So:
    -     Is there a way to reopen this InDesign file?
    -     Is there a way to search for these corrupted (?) reference codes in the Indesign file? (I still have a 80% ready copy of the Indesign file I can use.)
    -     Will removing all of these codes be the final solution,or should I remove the codes in the Word file and start completely anew? Of course that wouldn't make me very happy.

    Forum participants are not Adobe employees. We're users like you who volunteer to share what we know.
    Thanks for the added details.
    Usually someone somewhere in the forum's global audience is awake and eager to participate at almost any hour. However, "super storm" Sandy in the USA has caused massive losses of power, transportation, and communication, so responses may be delayed for some time.
    HTH
    Regards,
    Peter
    Peter Gold
    KnowHow ProServices
    Fritschy wrote:
    Thanks for your compliments, although they don't bring me any further.
    The version is 8.0.1, I always update when I'm prompted to do so by the update centre. As far as I know it is an international version.
    Still, I would guess the InDesign developers could tell me something about that ':' marker. I suppose the software didn't invent it itself.

  • 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.

  • Indesign CS6 Very slow - cross-references?

    Dear All,
    I have been struggeling with this for over 2 days now..
    I've treid the following solutions on the Adobe website
    http://helpx.adobe.com/indesign/kb/slow-performance-indesign-cs5.html
    and http://indesignsecrets.com/why-is-indesign-soooo-slow.php
    It does not seem to work.
    My document is around 40 pages, with some images (around 20), but it has a lot of cross references to a table in the same document.
    I have untreaded a lot of information. Currently only 10 pages maximum is threaded.
    My pc has 8 gb ram, 2.5 Ghz and around 40 GB free HD space.
    I think it might be my cross references, but I don't know how to fix it..
    I don't want it to be removed out of the table (because i need my references sorted on alhabatical order).
    Hope you guys can help
    Thanks,
    Daan

    @Daan – I do not much with cross references, but several users here and in other forums report performance issues when working with cross references.
    There is a 3rd party solution by DTP Tools:
    http://www.dtptools.com/product.asp?id=crin
    You could test a trial version.
    (And report back here how fast it is :-) )
    Uwe

Maybe you are looking for