Flash cross reference

Does anyone make a cross reference tool for a Flash FLA file?
I have quite a bit of experience with flash but I recently got
talked into making some changes to a full Flash site. I'm pretty
sure the site was made from one of the commercially available
template and like a lot of people I'm having a hard time figuring
it out. I can find some of the clip s that are being launched but
there is no obvious script on the main scene timeline that seems to
launch them. There is one reference to what must be a instance
label call "scroller" as in
_root.scroller.gotoandplay(2) but I can't find the origin of it. I
tried using Movie Explorer but it does not even show all the
scipts. Some sort of cross reference would be nice.

Similar Messages

How Can I Avoid Losing Cross-References?

We have multiple .book files that contain multiple .fm files, many of which contain cross references. Is it possible to work with those files outside of their network location (i.e from a flash drive) without losing the cross references? My employees frequently take work home or work remotely; however, we do not have remote access to our network, so they either e-mail the necessary .fm files or save them to a flash drive to work from. But when they return to the office and "save as" those files, the cross references become unresolved. Is there a way to avoid this?

> They are taking single .fm files home with them ...
How are they "taking" them?
Safe way:
Save and close all files on the office system.
Use file browser or command line to copy the files of interest to the transport medium.
Open the files at home, edit. Do not attempt to fix any broken Xrefs.
Save in place at home (not to transport medium)
Copy to transport medium.
This preserves the original filepath references, which should survive the trip even though unresolved at home.
Fail ways:
Save to transport medium at office, and.or
Save to transport medium at home.
Doing this re-writes the Xref filepaths relative to the current directory hierarchy. Unless you mimic the office tree at home, doing either of the above will make some or all Xrefs unresolved.
When you save an FM document to a new filepath, it revises the <XrefSrcFile 'filepath'> data structures to point to the new locations of Xrefs (and other imported content) relative to the new location. If you don't want this to happen (sometimes you do, sometimes you don't), then copy or move the closed document.

Please help! Broken internal cross references.

I'm creating a 20-page PDF from a PowerPoint file. In the source PowerPoint document, I've embedded internal cross references that DO initially carry over when the file is saved out as a PDF. However, whenever I rename the resulting PDF or move it to a new location, all of its internal cross references cease working. I can click on them, and they "flash" once, but they do not take me to a different page. I've been able to replicate the issue on other computers, both inside and outside my organization, and in both Mac and PC environments.
Is this something to do with relative vs. absolute links? Is the issue likely on Adobe's end? Or on PowerPoint's? Is there some setting I need to change somewhere?
Thanks in advance for any thoughts. I've spent hours trying to research and diagnose this problem, to no avail.
For what it's worth, here are some of the tech specs of my system:
- Acrobat v7.0
- PowerPoint 2007
- Windows XP
- To save the PowerPoint as a PDF, I'm selecting the Windows button from the upper-left corner, hovering over "Save as", selecting "PDF or XPS", selecting "PDF" as the file type, selecting my desktop (or other location) as the destination, and clicking "Publish".

Some observations.
Acrobat 7 — PowerPoint 2007
Office 2007 applications are not supported by Acrobat 7's PDFMaker
See: http://helpx.adobe.com/acrobat/kb/compatible-web-browsers-pdfmaker-applications.html
MS "Mac Office" — Acrobat 7
Acrobat 7 supported Office X and Office 2004 only.
Scroll to the bottom of the link above.
You'll see that, with contemporary releases of Mac Office and Acrobat there is no PDFMaker support.
From what you've posted it appears you do not have compatible software combinations on either the Windows or the Mac boxes.
Be well...

Cross Reference Source text options

Creating a Cross Reference linking to a Paragraph. In the paragraph where the cross-reference source is inserted, may the cross-reference link be applied to existing text in that paragraph so that the cross-reference destination text does not appear? Text anchors can be created to accomplish this, but that is an extra step (I can create a cross reference linking to a paragraph all in one dialog box). Thanks in advance for any suggestions.

Hi, Seir:
I agree that it's confusing. Here's how I do it:
To create a text anchor at the insertion point location:
* Open the Hyperlinks/Cross-References panel's menu (also called "flyout menu." It's the small icon at the upper-right of the panel, below the double-arrow (>>) icon that collapses the panel.
* Choose New Hyperlink Destination. THIS SHOULD BE NAMED NEW TEXT ANCHOR!!!
* Choose Type: Text Anchor
* Name the anchor as you like Click OK.
To create a cross-reference to a text anchor:
* Place the insertion point where you want it.
* Click the Create new Cross-Reference button on the bottom of the Hyperlinks/Cross-Reference panel.
* Choose Link To: Text Anchor
* Choose the target document
* Choose the text anchor
* Choose the Cross-Reference format
* Choose Appearance properties
* Click OK
I'm not sure what could cause the straight/curly quotes problem other than perhaps the font doesn't have curly quotes. Have you tried other fonts?
HTH
Regards,
Peter Gold
KnowHow ProServices

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

Look up ESB Cross-Reference within ODI

We have a need to look up ESB cross reference table that is populated by AIA PIPs. I saw ESB Cross-Reference KM mentioned in "Oracle Data Integrator Knowledge Modules Reference Guides 10.1.3". My question is that can this KM be used to do ESB cross reference table look up. We don't need to populate xref table, just need to look up.

Hi Ace2-
Thanks for your quick response!
I can able to reterive unmatched records by using “Left outer join” but it will multiple the record counts for “matching condition”.
PRODUCT_ID,PRODUCT_NAME,SALES_QTY,SALES_AMT
101,SEGATE-HD,10,100
101,SEGATE-HD,10,100
102,TOSHIBA-HD,20,5000
103,TRANSCEND-PENDRIVE,10,2000
104,SONY ERICSSON,10,100000
105,NOKIA-7710,20,20000
106,TOSHIBA-HD,10,9000
107,NULL,NULL,NULL
The above records will be the output of outer join. If you see the 2nd record it is getting duplicated as 1st record. I have to exclude the 2nd record as it increases the record count of “PRODUCT_SALES.csv” file.
Thanks, Prabhu

InDesign Tagged Text for Cross-reference Entries

I'm transforming XML to InDesign Tagged Text. The XML has index codes. For regular page entry type entries I'm having no problem outputting to the appropriate InDesign Tagged Text markup. However, I cannot figure out how to code cross-reference type entries. The document "Using Adobe InDesign Tagged Text CS5 Tagged Text" is extremely limited in its usefulness as it does not list all possible values for tag type tags, etc. I've tried dozens of tag combos and guesses at values. None have worked. Also, for some reason, even though I can create a "See x" type reference in the InDesign document, when I export to InDesign Tagged Text to look at the code, those tags are not included in the export.
Does anyone have a more definitive list of possible IDTT index tag values?

I have been exporting various things to IDTT to see what the result would be, with nothing really helpful as a result. I'll try hyperlinks, but reading of the Adobe guide to InDesign Tagged Text and also just looking at the InDesign scripting object model leads me to believe that there must be specific tags to create index-specific cross-reference tags.

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

Why is a single Cross Reference text turning red after doing an Update?

After updating a large book in FrameMaker10, the same cross-reference made in a couple of chapters is turning to red text. It is set as Heading 2. I tried to deleted the heading and re-typing it. I tried to change the style to Body and back to Heading 2 but all references to it are turning to red text after I update the book. Any idea what is wrong and how do I fix it? I am using unstructured version. See image.

Apply a Character Format of Default ¶ Font. Then re-apply the desired Paragraph Format. If the red goes away, it was either a Character Format that had been applied or a local color override. If the red is still there ...
Look at the Special > Cross-Reference > Format > Definition itself. Look for any <character-format-name> and see if any of those have a red Color defined in their Format > Character > Designer. If so, remove that building block from the definition [Change] [Done] [Replace].

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

Flash cross reference

Similar Messages

Maybe you are looking for