How to make a cross-reference

Hi,
I am converting a printed exercise book to IBooks Author. The original printed book has a couple cross-references and we would like to reproduce those in the IBooks version. It would not use page numbers but links to the exercise.
Format for exercise text...
Exercise Title
Muscles Targeted
Degree of Difficulty
1) The first cross reference would be by muscles targeted and displayed as follows...
   Main Muscle Group
     Muscle Targeted
       Exercise Title 1
       Exercise Title 2
2) The second cross reference would be by degree of difficulty and displayed as follows...
   Main Muscle Group
     Degree of Difficulty
       Exercise Title 1
       Exercise Title 2
1) Can this be automated based on styles or is this a manual process? I have 1200+ exercises to reference, twice.
2) Can I have multiple hyperlinks (2) to the Exercise Title?
Any thoughts and suggestions would be appreciated.
Thanks!

The problem with CR-ing to the captioning is that then in my body paragraphs the link shows up with the Figure Call (i.e. Figure 5.1, Figure 2.3) and with the caption as well, "...generated LHD matrix and export the specified subselection (as in Section 4.3: Insert a range matrix)."
I would like it to ideally be "...generated LHD matrix and export the specified subselection (as in Section 4.3)."
What is this invisible para hidden in a text frame technique you speak of? I'm very new to Framemaker, so the struggles are becoming self-aware.
Thanks!

Similar Messages

How to Create a Cross Reference of an item in an E-Business Suite

Hi ,
I need Help ,how to Create a cross reference of an item in an E-Business Suite
Regards
Srini

Hello Srini,
Prerequisite to create a cross reference for an item in eBusiness suite is that the item should be created in the master organization and assigned to your organization.
Navigate to screen Inventory > Items > Cross references. Enter a name for your cross reference.
Then, click on Assign : a screen is opened. In this screen, you can enter Item and Cross reference value. Note that a cross reference can be defined for an organization or common to all organizations.
Another kind of cross reference you can create is Customer item (it defines how a customer designates your item). It can be defined through screen
Inventory > Customer item > Customer Item and Customer item cross references.
Please refer to Inventory user guide for more detail about this functionalities.

Frame Maker 9 Cross References Question

Howdy,
I got two documents the original and a translated version of it. The original has a bunch of working cross references and it's all fine and dandy. The translated one on the other has a bunch of broken cross-references, chapter headers, headers in general and what not. Almost all of the "code" broke when the translator did it.
Either way, that's easy enough to fix it, I can just copy the working code from the original and paste into the translated document and it will generaelly fix the error.
Now for the question - Since my translated document is a couple of pages longer than the original due to the translation can I still copy of the cross references from the first document over, and it will be all fine and dandy?
Basically I didn't write either docuements I'm just fixing formatting and other errors, and I'm not entirely 100% how Frame Maker does it cross references are they based on a page number/paragraph parameters, or something like under X subheading go here and that's how it links.
TL;DR How do Cross refernces work in FM9? And if I have a translated doc longer than my original, can those same Cross references work in both docs?
Thanks much for any help/insight.
Dean,

Almost all of the "code" broke when the translator did it.
They probably deleted the Cross-Ref Markers when over-typing the text. If Text Symbols were off during edit, that's pretty easy to do.
... and I'm not entirely 100% how Frame Maker does it cross references are they based on a page number/paragraph parameters, or something like under X subheading go here and that's how it links.
Unless you are Xref'ing a hand-created Marker, Frame auto-creates a Marker, of type "Cross-Ref" at the start of the target paragraph. It also auto creates an Mtext tag, which contains what appears to be a unique number string, the Paragraph Format name and the paragraph text (including any auto number). There is also a <Unique> tag with another unique number string.
When resolving references, my impression is that Frame first searches for the <Unique> number, and if not found, then for the Mtext string, and then possibly for the Mtext string without the leading number string.
If the translators do two things, I would expect the Xrefs to port:
Don't disturb Xref Markers. This can be tough, because it's sometimes hard to select text and not nab leading Markers, and because all Marker symbols look alike, and the Index markers do need to be messed with.
Don't translate text defined by Markers. That text will auto-translate from the source text at Update.

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

Make Indesign cross references link to the top/above the destination paragraph?

Cross references in InDesign create interactive hyperlinks that link to a position in the resulting PDF where the targetted destination paragraph is right at the very top of the page. Often, it's too far up - sometimes the paragraph text is actually off the top of the page, and usually it's partially off the top of the screen.
When someone follows such a link, the most prominent text in the middle of the page has nothing to do with the link they clicked, and the heading corresponding to what they clicked is often partially off the top of the page as if it has been scrolled past. In my experience this looks like a mistake - they often won't see where they are supposed to start reading until, in confusion, they scroll back up the page a little.
Is there any way to control this - to make cross references jump to a point with a decent amount of padding at the top, so that what the user is looking for appears in a prominent position on the screen?

After some experimentation I've found something that could help make a workaround: The 'Baseline Shift' value for the first character of the destination paragraph determines where the incoming cross reference scrolling will land. This might be the break character and might (invisibly) have the baseline shift value of an earlier paragraph.
Give that first paragraph a high positive baseline shift value, and there will be a corresponding amount of padding above the text when the incoming scroll lands.
Give that first paragraph a very negative baseline shift value, and it will be pushed up above the top of the screen a corresponding amount.
In my problem paragraphs that weren't even on the screen when an incoming link landed, their first character (a tab between the 'bullets and numbering' paragraph number and the text) had somehow acquired a negative baseline shift from an earlier unrelated paragraph.

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

InDesign CS6 Crashes When I Make a Cross-Reference

I've downloaded CS6 from the Cloud, and have been quite happy with it, until yesterday when I attempted to do a simple cross-reference to create endnotes. I use Bob Bringhurst's method — http://blogs.adobe.com/indesigndocs/2009/03/endnotes_in_indesign_cs4.html , and when I get to Step 4, InDesign crashes. I've pasted the crash report on pastebin.com http://pastebin.com/pbeSWU0t . I'm on a MacBook Pro, running system 10.6.8. Thanks for any and all help. I've created a goofy work-around that will get me through this job, but is not going to work in the long run.
Note: The first thing I did was replace the preferences. This did not help.

Sorry, I had meant to reply earlier, unfortunately I didn't have much to say.
Yes, it looks like it is crashing in an area of the code that deals with hyperlinks/crossreferences.
That is unfortunately not a surprise
So I think you get to open a case at http://adobe.com/go/support or file a wishlist bug at http://adobe.com/go/wish. Sorry.

How to make Geological Cross Sections in Adobe Illustrator?

I have been tasked with producing a geological cross section in Adobe Illustrator. It is a lengthy process, as I am new to the software. I never learned it in my GIS studies. I know that there is plenty of GIS software out there to produce x sections automatically (we have Petrel for example), but they want it done in Adobe Illustrator as it's not a data driven x section.
Does anyone have any familiarity with doing such a thing? I am having to basically use the cutting tool to divide up a box into the sedimentary layers. Then I fill the cut shapes with the correct colour. Complications arise, however:
I have to show wavy lines between some sedimentary layers to indicate a gap, or layers which aren't shown. I am using the distortion tool to automatically produce the wavy line, which means I need to:
a. copy/paste the original area
b. change the appearance so there is no fill, delete all strokes except the one which will turn into the wavy line, apply distortion
c. copy/paste the original area
d. change the appearance so there is no fill, delete the stroke that will turn into the wavy line, change stroke to black line
This means I have 3 elements whenever there is a part of the cross section showing a wavy line:
the area which has a fill but no stroke,
the wavy line (derived from the area by deleting the fill and strokes which aren't wavy),
the rest of the stroke around the area.
Does anyone know of a faster way to do such a thing?
I wish I could just draw a shape using some sort of line tool and AI would detect when there is a closed off area so I could then select a colour fill.
Another problem is the cutting tool does not make it easy to produce matching curves:
In this image you can see that there is a wrinkle across many sedimentary layers, but my cutting skills in Illustrator mean that the lines do not follow a nice uniform shape. Of course this is the case in the real world as well, although at the moment the image has a bit too much of a 'hand drawn' look to it. Part of the problem is that the cutting tool, usually helpfully, smooths out the cut line as one goes (digitising a smooth curve with a mouse is impossible!). Sometimes this smoothing has undesired effects. It would be good to know if I can apply an offset to another line when cutting.
Is it right that I should be using the cutting tool as my primary way of setting up a x section, anyway?
I'm thinking a better way to do all of this would be to somehow have a tool that enables me to select vertices across multiple lines in sedimentary layers, then drag them up or down. This would then apply the same amount of curve across the layers.

Once you've set up your Pattern Swatches, this should take only a few minutes:
Draw your paths with a minimum of anchorPoints. Click (mousedown, mouseup) to place a corner point. ClickDrag (mousedown, drag, mouseup) to place a smooth point.
The top and bottom paths are now identical. When used to define a Blend, the program interpolates the paths between. The anchorPoints of the two original "key" paths of the Blend can still be selected and manipulated while the Blend is live; and the interpolated steps update accordingly.
t
There are several Libraries of pre-built Pattern Swatches you can load. Or you can create your own if none of the provided ones are what you want. The help files will show you the basics of creating a Pattern Swatch. Create one for each different pattern you want in the strata. Select the rectangle and the paths. Get the Live Paint Tool. Set the current Fill to one of the Patterns. Click between two of the strata lines. The selected objects will be converted to a so-called LivePaint Group, and you can proceed to apply other Pattern Swatches to the various areas.
The Shape Builder tool can then be used to trim away the outboard portions of the strata lines, back to where they intersect the rectangle.
JET
Strata

How to make a file reference

Applescript file reference causes me more confusion then normal in Applescript.
How do I construct a user reference free file reference.
-- set fn to path to file "my speaking document.rtf" of documents folder
-- set fn to "my speaking document.rtf" of folder "Documents" of folder "mac" of folder "Users" of startup disk
-- set fn to POSIX file (get "~/Documents/my speaking document.rtf")
set fn to POSIX file (get "/Users/mac/Documents/my speaking document.rtf")
log "fn = " & fn
tell application "TextEdit"
open file fn
end tell

You could also have a look at [Aliases and Files|http://developer.apple.com/mac/library/documentation/AppleScript/Conceptu al/AppleScriptLangGuide/conceptual/ASLRfundamentals.html#//appleref/doc/uid/TP40000983-CH218-SW28] in the [AppleScript Language Guide|http://developer.apple.com/mac/library/documentation/AppleScript/Conceptu al/AppleScriptLangGuide/introduction/ASLRintro.html#//appleref/doc/uid/TP40000983-CH208-SW1].

How to make use of reference site to cut down the volume of data

I am exploring the option to convert the current article master.
I understand there is something like reference article.
Is this tied to reference site?
What about grouping a series of PP conditions to be shared by a few sites?
I need more info on this. Can someone shared their experience on this and also provide me with some useful links?
Thanks

No reply after 2 weeks

How do we duplicate FM books and retain cross-references?

We are using FrameMaker 10 in a Windows 7 environment.
This post is related to an earlier post of mine:
http://forums.adobe.com/message/4237821#4237821
Note: To resolve this issue, we are willing to completely reorganize our folder structures or our user guides themselves.
We have the following contraints:
1. Our clients often require us to give them user guides in Microsoft Word, so they can edit the content as they customize the product over the years.
2. So, to avoid giving our clients Word documents that are in the vicinity of 500 to 600 pages in length (which often makes Word documents unstable), we break apart our user guides into two different guides: A procedure guide with step by step processes, and a guide that lists all windows and all window elements (tabs, fields, buttons, etc.).
3. The procedure guide has several dozen cross-references to the windows guide.
4. When we create WebHelp with RoboHelp, we combine the two guides together so the cross-references in the procedures are working hyperlinks to the corresponding window descriptions.
And then we have one more constraint.
Because we customize our product and user guides/online help for all of our clients, we start with a "baseline" starting point. We have a "baseline" procedure guide, and a "baseline" windows guide. So, we have to duplicate both of those guides to start customizing it for each client. The customization changes about 40% of the starting "baseline" content, and we have several concurrent contracts with various clients (so, we don't want to solve the problem I describe here by continually adding new conditional text to the baseline content every time we start customizing content for a new client).
So, we duplicate the two books when we start the customization process for a new client. We duplicate the procedure guide, and we duplicate the windows guide.
As you can imagine, we can use the "save as" technique in FM to preserve the cross-references that are internal within a single book, but we cannot figure out how to preserve the cross-references from the procedure guide to the windows guide. We end up having to manually fix all cross-references in the procedure guide that point to the windows guide.
Does anyone have an idea how we can regularly duplicate the original "baseline" books, and preserve the cross-references from the procedures guide to the windows guide?
Thank you in advance for any ideas.
Tim

I believe that might work if you used the master document method. That said I strongly recommend that you research Word's master document method as everything I have read indicates the Word gurus suggest it has problems.
Why would you want all these links working? If that is needed, shouldn't the user be accessing the online help?
See www.grainge.org for RoboHelp and Authoring tips
Follow me @petergrainge

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 references in structured documents

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

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

Cross References in ID CC

I've seen cross reference questions, but none dealing with ID CC, which, I believe is 64-bit.
We've greatly expanded our use of cross-references with this new more power version with overall good success. However, ID still seems to insist on updating every cross-reference with every keystroke. What a pain.
I work with all book documents open to minimize this, but since it's across a network, it can still be pretty painful. In addition, some documents are used in multiple books so I use layers to control which cross-references are active any any given time.
It's getting very trying. Does anyone have experience with using 3rd party xref management software with ID CC?

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-references in HTMLHelp

I currently have a help project which includes popup help
topics for a large number of fields in a software suite. They are
formatted as follows:
Field Name
Field Description
I also have a number of help topics that act as summaries for
sections of the software. They include field listings (using
tables) that are formatted as follows:
|
Field Name | Field Description |
|
Field Name | Field Description |
|
Field Name | Field Description |
Each field can be referenced in several different summary
pages.
Periodically, I have to update many of the field
descriptions. Is there a way for me to automatically fill in the
field descriptions in the tables, in HTML help, so that they
automatically update when I modify the descriptions in the popup
topics? The current project is in WinHelp - I am using bookmarks
and cross-references in Word to achieve this, but we're switching
over to HTML help and I haven't been able to find a way to do it
there.
Any ideas?
- Brian

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

How to make a cross-reference

Similar Messages

Maybe you are looking for