Skip to main content
T
Trevor-Nicholls
Inspiring
December 18, 2018
Question

How do I get this functionality back in FrameMaker 2019?

  • December 18, 2018
  • 1 reply
  • 1659 views

The XML schema we are using maps two different elements onto FrameMaker cross-references. One of them is a link to an ID elsewhere in this or another document, and the other is a footnote reference (where e.g. a table has two footnotes, and multiple cells in the table share the same footnote). The two types of cross reference have their own element tags and formats, on loading an XML document the elements are mapped to the correct type of cross-reference via rules, and when a document is saved the cross-references are translated back into link and footnoteref elements with all the appropriate attributes and content. So far so good.

In a previous version of FrameMaker I had the software set up so that if a user inserted a link element in the structure view, the "insert cross reference" dialog would automatically pop up, and the element tag and format would be correctly primed for a link; similarly if they inserted a footnote reference element in the structure view, the dialog would appear primed for a footnote. I cannot see how to make this happen in Frame 2019. Can anyone give me a tip?

Something similar is already happening with images; when a user inserts an img in the structure view, the insert > image dialog opens immediately. I didn't have to code or set anything to trigger this, it seems to be built in. But I definitely had cross references doing the equivalent thing in FrameMaker 8, and I'd like to get Frame 2019 doing the same, if possible.

Thanks in advance

T

This topic has been closed for replies.

1 reply

Ian Proudfoot
Ian Proudfoot
Legend
December 18, 2018

Trevor, I do see some unexpected behaviour when trying this out with the S1000D application. However I'm not sure it's the same as you see. I can insert an internalRef and it correctly inserts the correct initial structure and allows me to select the target from the Element list in the Cross Reference pod. This works as expected except that the Element Tag dropdown now only shows footnoteRef which is incorrect as the internalRef should be available too. This looks like a bug to me, but I'm not sure if we are seeing the same problem.

Ian

T
Trevor-NichollsAuthor
Inspiring
December 19, 2018

I need to correct something I said above. Our schema actually only has one element  for links, but our preprocessor stylesheet converts links which resolve to footnotes into a separate element. So as far as Frame is concerned links are cross references, and footnoterefs are, well, footnoterefs. Then our post-processor stylesheet folds them back into links again. All of that is working just fine.

There are two issues with cross-reference creation (and I think one of them is what you mention in your reply).

Firstly, when the user inserts a link or footnoteref element into the structure view, FrameMaker used to immediately open the Insert Cross-reference dialog. It doesn't do this now, the user has to open it from the toolbar menu.

Secondly, when the cross-reference dialog opened, the element tag used to say link for a link and footnoteref for a footnoteref. Now it says footnoteref (although link is available as a choice in the dropdown).

It's quite possible that in our previous Frame install I had set some user preference or saved some configuration data that caused this dialog to open, but if I did the details are lost in the mists of time, and I can't find anything about it in the developers guide or reference.

Ian Proudfoot
Ian Proudfoot
Legend
December 19, 2018

The pre-processor XSLT shouldn't really have any effect on the behaviour of the cross refs in FrameMaker because:

  1. XML is manipulated before FrameMaker 'sees' it. That assumes that the resulting XML is correct for Frame's cross-ref model. It's safe to assume that the results from XSLT are fine because it worked previously.
  2. While working in the FrameMaker environment there is no direct link to XML.

It seems that we are seeing different behaviour because the Cross-reference dialog is opening when I insert any type of cross-ref element. The Element Tag dropdown is initially populated correctly too. Only after insertion of a cross-ref does that list become limited to footnoteRef.

It could be an EDD thing? How are your xref elements defined? Are they single elements, or do they have sub-structure to allow for text content?

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices