Rationalization of Cross Reference or XRef

Hi Friends,
I would like to know what does rationalization of cross references mean and how to do the rationalization of Cross Refeence? Please be very detail. I will assign highest points for the person who can provide me a detailed answer.
I would appreciate greatly, if i can get the best answer.
Thanks
Venkata

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.

Similar Messages

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

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

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

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 within external Database using XREF API

Hi Experts,
Can we do Cross Reference within external Database using XREF API uses JDBC to access the Oracle Database Stored Procedures in SAP PI? How to use a JNDI Data source to access the DB and how to do the Connection Pooling will be done by the SAP J2EE server? Kindly let me know step by step proceedings.
Regards
Archana

Hello Archana,
It can be done with a Lookup call in a mapping.
Here's a little article about the topic in the SAP wiki:
http://wiki.sdn.sap.com/wiki/display/XI/HowtouseCrossReferencewithinexternal+Database
With kind regards
Sebastian

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

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

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

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

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

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

Hello!
I'm in real trouble, and I think that the answer is very close to me, but I can't get it by myself...
Here is my problem:
I'm currently improving the PDF parser that I've made, adding support for cross reference streams. After a careful reading of the ISO 32000 specification (with PDF 1.7 in background), I've wrote a piece of code that decode the stream and build the corresponding objects (I use Java).
But the decoded values are meaningless, and I don't understand why!
The data are like that:
filter predictor: 12
encoding : Flate
fields length : 1 2 1 (this is the W entry values)
column size : 4
I assume that there is one color per pixel formed by one byte.
First, I 'deflate' the data, then 'unfilter' them. Both operations look ok as I've made test for the Flate encoding (ok), and the for the filter I've use it with PDFBox source (and my work unfiltered well what PDFBox filtered...).
Note that I compared my outputs with those produced by PDFBox, and they are the same... Something may be wrong in the parameters I use, but I no idea now...
I think I missed out something as I read incorrect data as entry type 18...
I don't know where to go now, after a whole week of work!
If any have an idea, I'd be grateful to hear it!

This is ready algorithm to read PNG predictor styled Cross Reference Stream:
1. You need to read from PDF three variables: /Columns 5/Predictor 12 and /W[1 3 1] and of course stream
2. Deflate (encode) stream via zlib (without passing anything more than stream)
3. Divide encoded stream to rows, but length of each rows must be one bigger than columns variable (in this case is 6) because first value is type xref row
6. rows without first row go to UNprediction with this algorithm:
def self.do_png_post_prediction(data, bpp, bpr)
        result = ""
        uprow = thisrow = "\0" * bpr # just zero fill (byte zero - not char zero)
        ncols = data.size / bpr
        ncols.times do |col|    # just for each rows
          line = data[col * bpr, bpr]
          predictor = 10 + line[0]
          for i in (bpp..bpr-1) # just for each values of row without first value
            up = uprow[i]
            left = thisrow[i-bpp]
            upleft = uprow[i-bpp]
            case predictor
              when PNG_NONE
                thisrow = line
              when PNG_SUB
                thisrow[i] = ((line[i] + left) & 0xFF).chr
              when PNG_UP
                thisrow[i] = ((line[i] + up) & 0xFF).chr
              when PNG_AVERAGE
                thisrow[i] = ((line[i] + ((left + up) / 2)) & 0xFF).chr
              when PNG_PAETH
                p = left + up - upleft
                pa, pb, pc = (p - left).abs, (p - up).abs, (p - upleft).abs
                thisrow[i] = ((line[i] +
                  case [ pa, pb, pc ].min
                    when pa then left
                    when pb then up
                    when pc then upleft
                  end
                ) & 0xFF).chr    # AND 0xFF is very important, without this values growing extremely fast
            else
              puts "Unknown PNG predictor : #{predictor}"
              thisrow = line
            end
          end
          result << thisrow[bpp..-1]
          uprow = thisrow
        end
        result
      end
   7. Take bytes from UNpredicted rows, and in this case
   1st byte first byte is type
   2nd byte
   3rd-5th - is this what You want - offset in decoded PDF to objects (Xref table): offset = 2^9*5th + 2^8*4th + 3rd

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 that diplays only paragraph number

I need to create cross-references to numbered paragraphs. The auto number for the paragraphs includes not only a number, but a text character that is part of the number format. For example, a numbered list like 1) 2) 3) and so forth, where the cross reference display only the 1, 2, or 3, and not the closing paren.
FrameMaker has a building block <paranumonly> which ignores any characters other than digits in the auto number. InDesign doesn't seem to be able to do that. That is why I'm posting on the scripting forum. Perhaps there is a script that can do this?

In support of Niels' response, I'd written almost the same thing, but 1.__AG__, entered a more objective response (well put, AG!) before I sent my impressions.
I agree with Niels that
The reader might appreciate a more direct numbering system (the milspec standard of 1.2.2.2.2.1 would be the equivalent section to your 1B2b2a example
The tags used would be easier to navigate if they used a 1List 2List 3List convention, and that the punctuation used in numbering is a bit confounding at first glance
The xref format is straightforward if all levels are displayed at that point
Sadly, and as always, we can help with everything but the politics of your situation!
I do like Niels' suggestion of using the Running H/F to display the current section, if you're forced to use the numbering scheme as-is!
Best of luck navigating this with the powers that be.
-Matt

Cross-Reference to Multi-Level Paragraph

Hi,
Is it possible to create a cross-reference that does something like this:
'1.B.(1)(a)2) on page XXX' from the following:
I have created a cross-reference format as follows:
<$paranum[1. Heading]><$paranum[A. Text/Heading]><$paranum[(1) Text/Heading]><$paranum[(a) Text/Heading]><$paranum[1) Text/Heading]><$paranum[a) Text/Heading]> on page\ <$pagenum>
This works if I cross-reference from 'text10' to 'text9', which returns - '1.B.(2)(b)2)a) on page 6001',
and 'text10' to 'text2' returns '1.B. on page 6001'.
It fails when I go from 'text10' to 'text13' giving '1.C.(4)(b)2)b) on page 6001' instead of just '1.C. on page 6001'.
Any help on what I'm doing wrong?

In support of Niels' response, I'd written almost the same thing, but 1.__AG__, entered a more objective response (well put, AG!) before I sent my impressions.
I agree with Niels that
The reader might appreciate a more direct numbering system (the milspec standard of 1.2.2.2.2.1 would be the equivalent section to your 1B2b2a example
The tags used would be easier to navigate if they used a 1List 2List 3List convention, and that the punctuation used in numbering is a bit confounding at first glance
The xref format is straightforward if all levels are displayed at that point
Sadly, and as always, we can help with everything but the politics of your situation!
I do like Niels' suggestion of using the Running H/F to display the current section, if you're forced to use the numbering scheme as-is!
Best of luck navigating this with the powers that be.
-Matt

Cross Reference displays wrong Chapter

I have several FrameMaker files that will eventually be combined into one book. In some chapters there are references to outside chapters. At some point another person that was using these files had to switch the Chapter title; for example Chapter 7 became Chapter 6. Now when I open up, lets say Chapter 5, and I set up a cross reference to chapter 6 I got throug the following steps:
I make sure both files are open in FrameMaker, I put my cursor in the spot I want to make a hyperlink > Right click > Cross Reference
When the window Pops up I make the following selections:
Document: Chpater 6
Source Type: Paragraphs
Paragraph type: Heading1
Paragraphs: Page 7
I select the exact paragraph I want referenced
Format: CH XX, #
When I hit replace I am expecting the text on the screen to say something like "CH06, 3-1 Title" but instead it says "CH07, 3-1 Title"
The link goes to the location I want, it goes right to Chapter 6 but the visible text says Chapter 7 which is wrong. I assume this is happening because someone switched those two chapters.
Does anyone know how to edit what the text says or what I need to change in the switched chapters to make it work correctly. Something else I noticed is that the Document option in the cross reference is saying Chapter 6 with the old title, not the latest up to date title.

I think I may be having the same issue. I'm using Technical Communications version 3. I have a huge FM book composed of many books - over 3,000 pages if it were printed. I'm linking to the FM file in RoboHelp (RH). No broken xrefs in FM, but when I go to RH, there are odd xrefs or missing ones. I keep updating both FM and RH without any success. So, I generated a list of cross-reference markers in FM.
This is what I think is causing this. Even though you're supposed to be able to link to the FM file and if all is ok with the FM book (no errors, no broken xrefs), everything should chug along in RH. But, NO, it doesn't. When I put in cross-references in FM, I do them by the paragraph. But then you can also see the actual marker text, which doesn't always agree with the heading text. This is what RH uses. So, if you're having these issues, check the marker text to make sure it matches the paragraph text.
Below is an example where I had updated the heading, but the marker didn't match. FM didn't care and didn't report a broken cross-reference. RH just displayed the xref heading but it wasn't a link. Very frustrating. I'm looking for a way to get the xref markers to match the paragraph headings.
This is the heading: EContent in the PAC Patron Account
and this is the marker text: 28254:Heading 3: 3M eBooks in the PAC Patron Account - Items Out 768
BTW - I saw some snarky answers - just insecure people who want to show how much they know technically. For me, I just want the *******' tool to work! If I wanted to know all the sausage-making, I'd have been a programmer. I actually like to write and fiddling with RH is just tedious! In my experience, programmers are a dime a dozen; good writers are rare.
Make this a snark-free zone and help novices. Lord knows, Adobe's own documentation just doesn't get it. They tell you what something is but not how to do it! Oh, and the UX in RH is so cluttered and confusing! Do you use a pod or a menu item, what is important enough to get a pod? Why are there all these different ways to set up a project? It's like it was designed by hyped-up, overly-caffeinated people with really bad OCD. It's not about the tool, it's about the writers trying to get their jobs done!

Convert Cross-Reference to Text

Does anybody have a script that will convert cross-references to text? In other words, I want to be able to remove the linkage of the cross-reference but keep the static text in place.
Editorial comment: I set up on my local computer several books in CS6 and used cross-references, and everything worked fine. Then I moved the files to a network location and started suffering that painful slowdown that I had experienced in previous versions of InDesign. (I foolishly believed Adobe would have fixed this by now. My mistake.)

I'm guessing that the op want to convert the cross-references that you set in the Hyperlinks panel. Try this:
var xrefs = app.documents[0].crossReferenceSources.everyItem().getElements();
for (var i = xrefs.length-1; i > -1; i--){
xrefs[i].sourceText.insertionPoints[-1].contents = xrefs[i].sourceText.contents;
xrefs[i].remove();
Peter

Cross-References coming from Word in FM 7.2

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

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

Rationalization of Cross Reference or XRef

Similar Messages

Maybe you are looking for