Skip to main content
Wanda Jane
Inspiring
Mar 15, 2021 6:11 PM UTC
Answered

Cross-reference xrefs not numbering correctly for figures

I'm using FrameMaker 16 (2020) with DITA 1.3.

I use a settings file with customized templates. Between 2 versions of the settings file, I've lost some formatting in my table titles and cross-reference links.

My figures number correctly (figure numbers are <$chapnum>-<n+>) but the links indicate that the figures are in chapter 1. I defined the link using <$paranumonly> which used to work.

My table title is defined the same way as the figure title and appears correctly in the documents but not the PDF output. In the PDF they appear with just the <n+> value.

I've poked about in the definitions in various templates but I cannot change the output.

Please help.

I'm sure it's something simple that I'm just too tired to see.

Wanda

This topic is closed to new replies. Start a new post to keep the conversation going.
Wanda Jane
Wanda JaneCorrect answer
Inspiring
Mar 17, 2021 8:54 PM UTC

Hi,

I loaded a working version of the settings file, exported the working ditabase template, and rebuilt my settings file. Everything works fine now. There were 2 changes between the working version and the broken version. In the working version, my link was to the <$elemparanumonly> and the broken version had the link definition pointing to <$paranumonly>.

All is well, now.

Wanda

2 replies

Wanda Jane
Wanda JaneAuthorCorrect answer
Inspiring
Mar 17, 2021 8:54 PM UTC

Hi,

I loaded a working version of the settings file, exported the working ditabase template, and rebuilt my settings file. Everything works fine now. There were 2 changes between the working version and the broken version. In the working version, my link was to the <$elemparanumonly> and the broken version had the link definition pointing to <$paranumonly>.

All is well, now.

Wanda

Translate
Bob_Niland
Community Expert
Community Expert
Mar 16, 2021 1:07 AM UTC

Wanda Jane: I'm sure it's something simple that I'm just too tired to see.

The usual suspect is something resetting the $chapnum, either an autonumber in some prior text, book  number for component, or component file numbering properties.

Translate