Function issue of Cross-Reference

Hi,
thanks for your attention on this topic.
there is function issue of Cross-Reference.
when click the Cross-Reference after re-installed the software (adobe Framemaker 7.10), the function is not working. please kindly check the screenshots below:
Error message below:
Please help to check this issue.
software: Adobe Framemaker 7.10
System: windows xp sp3
thanks in advance for your support .
Message was edited by: Lu Steven

Fire the error log off to the e-mail address indicated in the error message and then contact Adobe Support.

Similar Messages

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

Cross reference or hyperlinking not working for InDesign CS5 Book to ePub

I cannot get hyperlinks or cross reference links to work when generating an ePub from InDesign CS5. (7.0.0.355, Mac OS 10.6.2)
Here's how to recreate a simple test demonstrating the issue.
1. Create a new InDesign Book (File -> New -> Book)
2. Create document one (File -> New -> Document)
3. Create a text box and type "Table of Contents"
4. Create document two (File -> New -> Document)
5. Create a text box in it and type "Story One"
6. Create a new paragraph style and assign it to the Story One text
7. Save document 2. I just kept the name Untitled-2.xhtml
8. Back in document 1, add a cross-reference and select document 2, the style you created, and then "Story One". "Story One" should now appear under the previously typed Table of Contents text, and when highlighed, should show it is an active cross reference in the Hyperlinks panel.
9. Save document 1. I just kept the name Untitled-1.xhtml
10. Add both documents to the Book and save the book.
11. From the Book panel, select Export Book to EPUB...
12. Save the epub file and open it in Adobe Digital Editions.
Note that the text "Story One" appears as a hyperlink but when clicked does not switch to the document 2. It does nothing apparent when clicked.
Looking at the XHTML source for the first document, it is immediately evident why. The filename for document 2.thml is missing. It looks like this: <a href="#anchor-anchor">
When it should be : <a href="Untitled-2.xhtml#anchor-anchor">
The same thing works if you create a hyperlink instead of a cross reference.
I note then when I use the option to go to the destinate reference in the Cross Link (hyperlink) panel, it does switch to the second InDesign docuemtn. So the cross reference is functioning (in InDesign). But the link is broken in the ePub for the above mentioned reason.
Bug? Something I'm overlooking?
Entire source of Untitled-1.xhtml:
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Untitled-1.xhtml</title>
<link href="template.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div id="untitled-1">
<div class="generated-style">
<p class="basic-paragraph" xml:lang='en-us'><span class="no-style-override">Table of Contents</span></p>
<p class="basic-paragraph" xml:lang='en-us'><span class="no-style-override"><a href="#anchor-anchor">‚Äústory one‚Äù</a></span></p>
</div>
</div>
</body>
</html>

As far as I can tell, it has NOT yet been fixed in CS5.5. I'm having the same problem. I have about 90 hyperlinks to fix.
And the explanation that Teus Dejong gives indicates it's not going to be that helpful: "we have found that only the links in documents split by the CS5 exporter will be fixed. For books the script does only work for references to earlier documents in the book, not for forward references. This means in practice that for most books the script will not repair the links and should be seen as a means to add the year only. At the moment I see no way to repair this, because the book epub output of InDesign does not contain sufficient information to repair links referencing forward to others documents in a book."
It's pretty discouraging.

How to use the Cross Reference fields in P4P

I have been receiving questions related to the Cross Reference section from many different customers and partners. This post represents my attempt to describe the Cross Reference Section and the Equivalent Numbers stored within.
Identity
A term that Kelly uses and I will borrow is “identity”. A given specification can have many identities. The basic identity is the specification number generated by GSM. This is useful during early stages of design. Once we get past a draft or development status in the workflow the organization quickly wants to identify the specification in other ways. Examples include:
Execution System Number: Operations and Supply Chain quickly need to formalize an item or material for forecasting, inventory and purchasing…
Custom Numbering Conventions: Sometimes an organization has very specific custom logic for identifying materials. Usually terms like smart numbering are used to describe their methods.
Data Migration Identifier: In some cases customers have extensive data clean up projects. As part of the effort systems and processes are developed and an identity is created. In my experience we loaded a “Base Stock” number to represent Packaging Materials. The label stock that was commonly used was historically not represented so we created a number as part of the migration project.
Identity Functionality:
The Fields: The four major fields that make up the Cross Reference section are as follows:
>>System Name: This field describes the system generating the identifier. Examples I like to use are Oracle EBS or SAP Material Master. Sometimes geography must also be concatenated to the system, i.e. Oracle EBS – NA. This occurs when the customer is a large multinational where multiple ERP implementations exist. Therefore the same material may be known by many different numbers, i.e. Oracle EBS – NA = 77432, Oracle EBS – EU = 88883.
>>System Code: The system code is merely the syntax used during integration. Using CSS or various APIs you may chose to identify the system using an abbreviation, EBSNA or SAPMM.
>>Equivalent: The value representing the identity within a given system.
>>Externally Managed: If you are using CSS or an API to receive Cross Reference data you can define the field as "Externally Manged". When a cross reference is marked in this manner the general user community will not be able to edit the field. Administrators associated with the role [Externally_Managed_Cross_Ref_Admin] can edit the field if needed.
Syndication: While some users enter equivalent numbers manually, others use integration tools to generate and transmit identities. If a given cross reference is marked as “Externally Managed” then users are unable to manually enter data. On initial syndication the specification will not have a given equivalent. The specification is sent to middleware, a number is generated by the appropriate system and the response is sent back to GSM to add the System Code to the specification with the appropriate identity value.
Copy verses Issue:
>>Copy: When a user copies a specification the Cross Reference data is NOT included. Since the identities refer to the originating specification it does not make sense to carry over to the copy. If we did then users would quickly need to delete the data.
>>Issue: When a user issues a specification it maintains the Cross Reference data. This is an important concept because it is expected that a system like GSM will have many issues related to a single ERP #. ERP systems are usually not interested in many of the fields stored in the Product Data Management system.
Reference: As raw materials are consumed as inputs into Formulation or Trade Specifications the organization may come to identify the materials based on equivalent numbers. Therefore GSM allows for an equivalent number to appear next to the GSM number.
Implementation Issue: Ingredients In Packaged Quantities
Some customers run into a situation where the ingredient specification does not represent a packaged quantity. From an R&D perspective the developer does not care if the material comes in a box or a tanker. In this situation the GSM ingredient may be represented in the ERP system by many items and therefore more than one cross reference value. These items represent packaging differences that are important to purchasing, manufacturing, warehousing, and other execution systems.
I hope this helps describe some of the purposes and implementation issues around the Cross Reference field.

You need to get jmf.jar in your CLASSPATH, either on the command line, in an environment variable, by putting a symlink in $JAVA_HOME/lib/ext, whatever works for you. Have you done that? Once it's in the classpath, you can run jmstudio from any directory with the command "java JMStudio".
Items in the bin directory are just shell scripts, run with "sh jmstudio" or whatever suits your shell (on Mac OS X, copy one of these guys and append ".command" to the filename to make him double-clickable in the Finder).
--invalidname

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

Error in cross reference creation urgent

Hi,
I am trying to create cross reference in SOA11g. I created xref tables(DEMO_CONTACT) first. when i try to populate data into that table using xref:populateXRefRow1M() function, it is showing following error:
XPath expression failed to execute. An error occurs while processing the XPath expression; the expression is xref:populateXRefRow1M("DEMO_CONTACT.xref","SBL8_ID","bpws:getVariableData('ContactVarTMP1')","SBL6_ID","bpws:getVariableData('ContactVarTMP2')","bpws:getVariableData('xrefAction')"). The XPath expression failed to execute; the reason was: internal xpath error. Check the detailed root cause described in the exception message text and verify that the XPath query is correct.
can anyone help me to solve this issue.
Thanks

Make sure the URL is accessible. Can you provide below information -
1. Which version of OSB and SOA are you working with?
2. Which type of service have you defined on OSB?
Regards,
Anuj

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.

Error while creating Cross-reference table using Xreftool (PIP Ins)

Error while running xref.sh script unable to create cross reference table.
**Error: Exception in thread "main" java.lang.NoClassDefFoundError: oracle/tip/xref/tool/AdminTool**
Could not find xref directory within tip folder (/OracleAS_1/bpel/docs/workflow/oracle/tip)
searched for similar issue in OTN it says issue fixed by upgrading Oracle AS, we are using 10.1.3.4 MLR#8
http://kr.forums.oracle.com/forums/thread.jspa?threadID=835446
steps followed.
Creating Cross-Reference Tables
Complete the following procedure to create cross-reference tables.
To create cross-reference tables
1 Navigate to the following directory:
%SOAHOME%/SiebelODOPPIP/scripts/
2 Open the following file for editing:
xref.sh
3 Set the userid and passwd for logging into BPEL console on the appropriate lines.
4 Set the correct SOA_HOME location on the appropriate line.
5 Save and close the file.
6 Make the file executeable:
chmod +x xref.sh
dos2unix xref.sh
7 Change directory (cd) to integration/esb/bin under %SOAHOME%.
8 Execute ../../../SiebelODOPPIP/scripts/xref.sh.
I am using SOA suite 10.1.3.3 and getting same error
Error: Exception in thread "main" java.lang.NoClassDefFoundError: oracle/tip/xref/tool/AdminTool

Hi Abhijeet,
please check in transaction FI01, about your data consistencies. You can use this wiki help in terms of Address, it it found any useful facts for you
Address Checks - Business Address Services (BC-SRV-ADR) - SAP Library

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 failure when converted to PDF

One of my clients uses FrameMaker 7.1 to author their product documents, and convert everything to PDF before releasing it. I often see problems where cross-references within the document work in FrameMaker, but do not work as links in PDF, even though they show as links and the cursor in Acrobat changes correctly as it should when pointing to a link. I have now encountered a FrameMaker file where the cross-references worked as links in the first revision of a PDF, but a random selection of them didn't in the next revision, even though no changes were made to any cross-references in the original FM file. It's not an issue with my PC or that of the person who generated the files - we have tried the conversion on multiple installations and they all produce the same result. To fix it we've had to locate each failed link in the PDF and put it right manually in the FM source file. Has anyone else encountered this? Any thoughts on the cause?

DxCooper (not your real name, I guess),
The rigid approach is to check in the PDF Setup dialog, last tab "Links", whether the option "Create Named Destinations for All Elements and Paragraphs" is selected. This helps but the size of the PDF may increase considerably.
Another thing which may help, especially (but not limited to) if the documents originally were authored in previous versions of FrameMaker, is the use of what is described in the prose of the above mentioned dialog: Optimize the PDF size by running the described routines once for every file. As far as I remember you can select a book file for that feature.
HTH,
- Michael (who feels better, if he can write to people with a name)

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

Cross reference in ID CS4 goes to wrong destination in Acrobat

I am creating a 108-page document in ID CS4 with lots of cross references (a new feature in CS4 after using the scripting work-around in CS3). I created a new cross-reference type which is only the page number of the destination in an invisible box.
Now that the document is finished, I created a PDF. The version of Acrobat on my PC is Acrobat 9 Pro Extended.
Most of the cross-references work as expected. A handful, though, while they show the correct page number in the text, when clicked in Acrobat Reader take the user to the wrong page. For example, the text says "see page 88" but a click takes the reader to page 99.
I have opened this pdf in Reader on multiple PCs: same problem. I have erased the old X-ref and re-added it: same problem. I tried installing the recent InDesign 6.0.1 update and replacing the X-ref and re-exporting to Acrobat: same problem. If I temporarily use a different X-ref type that includes the paragraph text, I see the correct text. Bottom line: everything seems OK EXCEPT when clicking in Reader.
Any thoughts on what to try to make this problem go away?

Try opening the PDF in Acrobat, and examining the links with the links tool. That may help you figure out the problem. It will show the specific text anchor to which the link is pointed. From my experience, it just references to a page number, unless you link to a specific text anchor within ID.
I had a similar problem in Framemaker, and I couldn't resolve the issue unless first deleting the marker from the destination and letting FM regenerate it.

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, Paragraph Style conflict?

I'm created an epub file and have a cross reference for one of my chapter titles. When I export it to ADE the final product has the cross reference in the file but the paragraph style for the text that I linked lost all of it's styling somehow. The paragraph style is supposed to be centered and have space after it but it is completely gone but the code is still in the xhtml file.
I have opened the xhtml file and cannot see where the issue is. Has anyone else had this problem exporting from CS4? If so, how do you fix it?
Thank you so much!

According to the FM7 Help, the variables for background text frame use might be:
<$paranumonly[paratag]>
to pick up the first instance on a page, and
<$paranumonly[+,paratag]>
to pick up the last.
The "+," bit is the key. I've never tried it myself.
This presumably also assumes that the paras of interest all have the same format name.

Cross-reference mixup after package

Hi,
I've got a question regarding InDesign cross-reference.
Here's the background:
The original source is stored in F drive.
Packaged source is stored in C drive.
For each of my drafts, I need to attach the packaged source with the PDF.
I have 10 cross references in a 100 page document.
The question is this:
When I package the InDesign files, I assumed that my cross references will be updated to the InDesign files in the packaging directory.
But when I checked them out, the cross references were still linked to the original source. So I had to manually update each cross reference to the packaging directory.
Although the PDF works fine, I have some concerns about this situation.
Does any one else had this problem? If so, are there any solutions to this issue?
Any help is greatly appreciated.
Thx.

Books are funny creatures. Another thing that confuses a lot of users is that if you make a copy of the .indb file and all the component .indd files, the copied .indb does not point to the copied .indds, but retains the links to the original locations.

Function issue of Cross-Reference

Similar Messages

Maybe you are looking for