XML Bookmarks & Cross References Broken
Problem: Bookmarks and cross-references created in XML output
files generated using RoboHelp X5 do not work. Any suggestions?
Hi Lynnca,
The text of a cross-reference is a property of the FrameMaker xref object that is expected to be autogenerated, so it is not included in the markup. The XML version of an xref is similar to the internal FrameMaker model, where you insert an xref an the text is automatically created and controlled internally. An xref saves as an empty element with information about how to find the source and regenerate the text, but no indication of what text was originally displaying when you exported the markup.
Properly configured, the xref text will autogenerate when you reimport to Frame, so the empty element is OK there. If you are using the XML with some non-Frame post-process, that process will need to accommodate this convention for representing xref links.
Note that the refint tag is actually closed, as indicated by the trailing slash just before the final angle bracket. This is a shortcut for representing elements with no content.
Russ
Similar Messages
-
Broken bookmark cross references in Printed Documentation
Hi,
I'am using RH 10 to generate a printed documentation output. What i notice is that the book marked cross references are broken in the Printed Documentation output. Other cross references are linking fine, but, the bookmarked cross references do not link to their destination.
I generated a chm file for the project and the bookmarked cross references appear fine there. Is there anything that could be tried to rectify this problem.
Please note that i'am using HTML files as the source files to convert to a Word output.
Thanks,
RupeshThere's no easy way to do this. RH doesn't include any
sequence that will convert to a cross-reference in Word, and
inserting multiple cross-references in Word isn't as easy as
executing a find-and-replace command. The best workaround I've
found so far is this:
1. In your RH doc, include a reference that is easily
distinguished from other text. For example, "For information on
Project Beta, see page BETA."
2. Generate the Word document.
3. Find the first instance of "BETA."
4. Insert a cross-reference to the page number of the Beta
heading.
5. Toggle the field code.
6. Copy the field.
7. Find the next instance of your special text ("BETA" in
this example).
8. Paste the field reference.
9. Repeat this process until you're finished.
Unfortunately, the field code references change each time you
generate the document. Equally unfortunately, Word won't recognize
regular braces and text as a field code reference - you have to use
the Ctrl+F9 sequence to generate them manually. So you can't just
generate the document, insert the first cross-reference, and then
replace "BETA" with {PAGEREF _Ref### \h} across your entire
document - it won't work. Instead, you must visit each reference
and paste the field code sequence manually.
If someone else can improve on this process, I'm sure a lot
of people would be happy. If not, it's the easiest workaround I've
seen here, so you might find it useful. -
Need to know xml flow cross references, Its Very Urgent Help me
need to know xml cross references coding and sample files for indesign cs3
As far as I know, cross references are available in CS4/5, not in CS3. It is possible to write a script that creates hundreds, thousands of them very quickly taking the necessary information, let's say from tagged text. You wrote only one line, so it's difficult to me to imagine what XML structure you have and what your requirements are. But here is a script I wrote a while ago -- probably you need something similar, and here's the source code (not final version, of course) to show the approach I used.
Kasyan -
Cross-References Broken In RoboHelp 10 Output
We are using FrameMaker 11 to author our documentation. We have some cross-reference links that do not work when the FrameMaker book is imported into RoboHelp. Upon import, the href information is not included in the link in the HTML code. The text looks like a link, however. When the help is generated, the text is not a link. The following is an example of a non-functioning link:
see <a>Link</a>.</p>
Here is an example of a cross-reference that is functioning correctly:
<a href="#XREF_90399_Heading_Text">Link</a>
There are no errors in FrameMaker. The cross-reference is updating correctly in FrameMaker. In addition, when a PDF is made form the same book, the cross-reference works in the PDF.
Troubleshooting steps I have taken:
I have tried going to MIF and back for both the source and target documents.
I have recreated the cross-reference and marker.
I have tried linking to a heading cross-reference marker, as well as a manually create cross-reference marker.
I have renamed the file.
I have renamed the marker.
I have used different cross-reference formats.
I recreated the file by copying all the text to Notepad and pasting the text back into a fresh FrameMaker file.
None of the steps I have attempted have corrected the issue for the cross-reference I focused my troubleshooting on. I hope that someone can point me in the right direction to correct this issue.I have been trying everything I can think of to move the files around to resolve the issue. 35 characters is very disappointing. Is this for the file and cross reference or the whole file path? I am not sure how you are going to be able to link from one Framemaker file to another, including a cross-reference name (especially when you can use heading for the cross-reference name) with a limitation like this. We also have a large library with many directories. We utilize single sourcing, so some files are in completely other directories from the file that is cross-referencing to it. From what you are telling me, it sounds like we no longer have the ability to use cross-references from one file to another in our library structure. Are you saying that all cross references basically need to be in the same file to allow cross references to work properly in RoboHelp? We moved from a WebWorks solution and we never had any issues with our links.
What I don't understand is the marker is in the destination file in the converted RoboHelp files, but the link is completely missing the <a href="#XREF_name ofmarker"> code in the cross-reference link. When I go in and manually link the cross-reference in RoboHelp, it works. This seems like a bug. I think having a 35 character limit on a filepath, filename, and cross-reference name is not going to work for anyone that has any sort of complex directory structure with multiple authors, sharing content and since it isn't a limitation of HTML, I don't see why this functions this way. Manually linking isn’t a reasonable option for us. We have a publishing system that publishes all of our output. We have hundreds of files that are generated automatically. -
How to find broken links or cross-references in a PDF file?
Hi,
Recently I have been trying to figure out if there is a way to find out any broken link(s) in a PDF file. I'm aware that in FrameMaker we can search for Unresolved Cross-references and fix them, but is there such feature in Acrobat?
Any suggestions on this would be highly appreciated.
Thanks.There's nothing in Acrobat itself, but there are 3rd-party program plug-ins that do the job. I use 'Autobookmark' (http://www.evermap.com/autobookmark.asp) which does a very good job of finding and marking broken links and allows keyboard-entry editing without having to re-browse the link if you already know the correct path. It also facilitates a lot of other useful functions that Acrobat makes rather tedious (like changing the zoom setting on all links or bookmarks).
-
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 -
Hi,
I try to generate a report using a template. In my template I use some cross-reference to refer to one bookmark. For exemple in the first page I created a bookmark for my name and in the header I created a cross-reference refer to my name. The problems is when I run my VI the bookmark actualise perfectly but the cross-reference refer to the bookmark can't actualise with the same value and generates an error : "Error! Reference source not found".
Can somebody help me please!
Nki
Solved!
Go to Solution.
Attachments:
01.jpg 72 KBHi,
When i create the word template, the bookmaks and the cross-reference referred to the bookmark update correctely. The problem is when I try to change the bookmark using "report generation from template vi" the bookmark change but not the cross-reference and the error generated is "Error! Reference source not found".
I make coople reasherch and i think they have no solution for this because : "if the text in a heading referred to in a cross-reference is revised, the cross-reference to the heading may no longer work" (http://office.microsoft.com/en-us/word-help/troubleshoot-cross-references-HP005189368.aspx).
To "resolved" this problem I create an other bookmark in the template who have the same value white the principle bookmark.
I use Labview 2011 and Micosoft office 2010. -
TOC and Cross reference bookmarks
Hi. I recently finished work on a book that had front matter containing a brief TOC and a detailed TOC. The book also contained individual TOCs at the beginning of each chapter.
I updated all numbering across the book files before generating the TOCs in the front matter, then generated the brief and detailed TOCs using my TOC Styles. However, I assigned cross references for the individual chapter TOCs. May not have been the best choice.
Because there was special styling for some of the front matter TOC entries that wasn't easily specified using just the TOC Styles, I cut and pasted groups of entries from the generated TOC on the pasteboard into a new frame on the page. I checked in Story Editor to ensure that the invisible markers for the TOC entries had been copied into the new frame.
When I exported the files to PDF, the TOC entries no longer pointed to the correct pages. They simply pointed to the first page of the PDF when clicked. Furthermore, no bookmarks showed up the TOC entries in the Bookmarks panel, even though I had "Create PDF Bookmarks" checked in my TOC Styles.
I have three questions, then:
--Is there any way to reclaim the behavior of the TOC bookmarks, and their display in the Bookmarks list of the PDF, if the entries are copied and pasted into a new frame in InDesign, without doing this manually in Acrobat Pro?
--Is there any way to get cross references to display as bookmarks in a PDF, assuming that I needed to make individual PDFs of each chapter, without doing this manually in Acrobat Pro?
--I'm betting that all files should be exported from InDesign as a single PDF in order for all TOC and cross reference links to work properly, without manual intervention in Acrobat Pro? If so, and manual intervention is required, is this accomplished by cataloging/indexing in Acrobat Pro?
I need to be able to pass this information along to a publisher who is now requiring all of their compositors to submit bookmarked PDFs with their printer files. I'm pretty sure I know the answer to this one, but I would like verification from the pros here. Thanks!Hi. I recently finished work on a book that had front matter containing a brief TOC and a detailed TOC. The book also contained individual TOCs at the beginning of each chapter.
I updated all numbering across the book files before generating the TOCs in the front matter, then generated the brief and detailed TOCs using my TOC Styles. However, I assigned cross references for the individual chapter TOCs. May not have been the best choice.
Because there was special styling for some of the front matter TOC entries that wasn't easily specified using just the TOC Styles, I cut and pasted groups of entries from the generated TOC on the pasteboard into a new frame on the page. I checked in Story Editor to ensure that the invisible markers for the TOC entries had been copied into the new frame.
When I exported the files to PDF, the TOC entries no longer pointed to the correct pages. They simply pointed to the first page of the PDF when clicked. Furthermore, no bookmarks showed up the TOC entries in the Bookmarks panel, even though I had "Create PDF Bookmarks" checked in my TOC Styles.
I have three questions, then:
--Is there any way to reclaim the behavior of the TOC bookmarks, and their display in the Bookmarks list of the PDF, if the entries are copied and pasted into a new frame in InDesign, without doing this manually in Acrobat Pro?
--Is there any way to get cross references to display as bookmarks in a PDF, assuming that I needed to make individual PDFs of each chapter, without doing this manually in Acrobat Pro?
--I'm betting that all files should be exported from InDesign as a single PDF in order for all TOC and cross reference links to work properly, without manual intervention in Acrobat Pro? If so, and manual intervention is required, is this accomplished by cataloging/indexing in Acrobat Pro?
I need to be able to pass this information along to a publisher who is now requiring all of their compositors to submit bookmarked PDFs with their printer files. I'm pretty sure I know the answer to this one, but I would like verification from the pros here. Thanks! -
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 -
Cross references in custom XML
Hello!
We have a custom XML schema and a structured application that allows us to edit our XML documents in FM. The schema contains a definition for a cross reference element and a definition for a target element.
=============================================================
Example:
A cross reference element (say, documentA.xml contains this element): <cref target="documentB.xml#sect123"/>.
A target element (say, documentB.xml contains this element): <section id="sect123"/>.
Also I have a book in FM that includes both documentA.xml and documentB.xml.
=============================================================
FM outputs error messages when I try to save documentA.xml.
So, I have few questions concerning this issue.
How should I describe the cref element in EDD?
A manual says, that the @target attribute must be of the IDREF type. Sounds good but the # char is restricted for IDREF values. How can I resolve this contradiction? If I write <cref target="sect123"/> (target id without filename) FM outputs error messages when I open documentA.xml in FM.
Thank you!Dear Russ,
Thank you very much for the answer. I'm sorry for my replying you with a delay,
To make long story short, now it's OK: we can load a document with cross references to FM as well as we can save it form FM. Thank you once more.
I'd like to make some comments that might be useful for other readers of this forum.
As far as I understand the Structure Developers Guide mostly describes import/export transformations between an XML format and the FM format. But we never convert XML files to FM files and vice versa in our application. We open an XML file in FrameMaker, we edit the XML file in FrameMaker, and finally we save the XML file from FrameMaker. So, while reading the Guide I had a permanent doubt if import/export is the case I deal with.
After several probes and attempts we found out that the following format of cross reference is appropriate for our application:
<xref srcfile="fm-properties.xml#sys_psnt_part_number" format="CrossReference"/>
(We found this type of cross references on page 399 of the Guide).
The xref element must have an attribute of the IDREF type defined in a schema and in an EDD even while we don't use it. This attribute may actually be omitted in an XML file but we had to define it for xref.
The root element of a target XML document must have an attribute of the ID type even while we don't use it. -
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 or hyperlinking not working for InDesign CS5 Book to ePub
I cannot get hyperlinks or cross reference links to work when generating an ePub from InDesign CS5. (7.0.0.355, Mac OS 10.6.2)
Here's how to recreate a simple test demonstrating the issue.
1. Create a new InDesign Book (File -> New -> Book)
2. Create document one (File -> New -> Document)
3. Create a text box and type "Table of Contents"
4. Create document two (File -> New -> Document)
5. Create a text box in it and type "Story One"
6. Create a new paragraph style and assign it to the Story One text
7. Save document 2. I just kept the name Untitled-2.xhtml
8. Back in document 1, add a cross-reference and select document 2, the style you created, and then "Story One". "Story One" should now appear under the previously typed Table of Contents text, and when highlighed, should show it is an active cross reference in the Hyperlinks panel.
9. Save document 1. I just kept the name Untitled-1.xhtml
10. Add both documents to the Book and save the book.
11. From the Book panel, select Export Book to EPUB...
12. Save the epub file and open it in Adobe Digital Editions.
Note that the text "Story One" appears as a hyperlink but when clicked does not switch to the document 2. It does nothing apparent when clicked.
Looking at the XHTML source for the first document, it is immediately evident why. The filename for document 2.thml is missing. It looks like this: <a href="#anchor-anchor">
When it should be : <a href="Untitled-2.xhtml#anchor-anchor">
The same thing works if you create a hyperlink instead of a cross reference.
I note then when I use the option to go to the destinate reference in the Cross Link (hyperlink) panel, it does switch to the second InDesign docuemtn. So the cross reference is functioning (in InDesign). But the link is broken in the ePub for the above mentioned reason.
Bug? Something I'm overlooking?
Entire source of Untitled-1.xhtml:
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Untitled-1.xhtml</title>
<link href="template.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div id="untitled-1">
<div class="generated-style">
<p class="basic-paragraph" xml:lang='en-us'><span class="no-style-override">Table of Contents</span></p>
<p class="basic-paragraph" xml:lang='en-us'><span class="no-style-override"><a href="#anchor-anchor">“story one”</a></span></p>
</div>
</div>
</body>
</html>As far as I can tell, it has NOT yet been fixed in CS5.5. I'm having the same problem. I have about 90 hyperlinks to fix.
And the explanation that Teus Dejong gives indicates it's not going to be that helpful: "we have found that only the links in documents split by the CS5 exporter will be fixed. For books the script does only work for references to earlier documents in the book, not for forward references. This means in practice that for most books the script will not repair the links and should be seen as a means to add the year only. At the moment I see no way to repair this, because the book epub output of InDesign does not contain sufficient information to repair links referencing forward to others documents in a book."
It's pretty discouraging. -
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 -
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?
- BrianHi 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 go to facing page when PDF'd
Is there a workaround for this? Mac, CS5.5. (I also have CS6 but still can't get the file to open!!)
I have a large book file, with facing pages. Cross-references throughout, exporting to PDF via PDF (Print) to get separate pages rather than spreads.
The resulting bookmarks are all correct, but the cross-references go to what would be the right hand page instead of the noted page. So, if the cross-reference is supposed to go to left page 84, it actually goes to right page 85. That works fine if the PDF is viewed in 2-up view, or exported as full spreads, but not in single page view.
Is there a solution? Or is it fixed in CS6?Yes. There are five in one book. All the page links lead to pages in documents within the book.
The Contents page is in one InDesign document. It has links in it to pages within the other four InDesign documents.
Currently, clicking on the links in the exported PDF of the book takes you to page 1 - except for links to pages within the same InDesign document, and one link on the Contents page which leads to the correct page (that link is set up in the same way as the others).
EDIT: BTW - I will be leaving work in about 30 minutes, so I won't be able to try out any fixes until tomorrow, about 10am (London, UK).
UPDATE: When I checked the broken hyperlinks in Acrobat Professional, all of the page links that led to the cover were set to go to page 0. But in the InDesign document, they're all set to go to the correct page.
Message was edited by: richard_cosgrove
Maybe you are looking for
-
How do I delete a corporate e-mail account?
How do I delete a corporate e-mail account?
-
System variables in R/3 for the action from the portal
Hi, How can we know the action from the portal,i mean from the create expense report i want to throw an error message if the user press "Review" button based on my validation. i have written in the badi,but when the user press "Previous step" button
-
Design patterns for data access
. What design patterns can be used for data access to ensure that only a minimum amount of data is maintained in session
-
Either need ability to edit PS layer style in FC or allow for update check to the .psd file
There is not much control over look in FC of imported .psd file. So please allow for update import some how.
-
I keep getting an error message that says "iPod cannot be synced. The iPod is not connected."
I've restored it multiple times and I've had no luck! What do I do?