How do I get correct values from the %refpage variable and partial (Range+) composition?

RE: How do I get correct values from the %refpage variable and partial (Range+) composition?

Bart Terryn — Sat, 08 Aug 2020 11:58:14 GMT

Cheran,

As Jonathan explained to you, compose will not solve your problem if you want to continue to use compose range pages.

But there is always xyPerl that can help you.
You could write out the relative page number of your (end-1?) reference point(s) into a file.
And then use that value to calculate how many pages you are away from that point.

You will still need to do at least 2 composes to get the correct answer.
But once the end point is set, you can do any compose you like, you will get the correct answer.

Kind Regards

Bart

RE: How do I get correct values from the %refpage variable and partial (Range+) composition?

Cheran Shunmugavel — Fri, 07 Aug 2020 20:14:24 GMT

Jonathan,

Thanks for the detailed response. We are indeed using Auto-looseleaf, and we do have "Compose Changed Cross-References" set to "yes". I must not have been paying close enough attention during my auto-looseleaf tests, because it is getting the correct page number. I can also see that doing "Xref Errors" after the Range+ compose also gets the page numbers that I expect to see.

RE: How do I get correct values from the %refpage variable and partial (Range+) composition?

Jonathan Dagresta — Fri, 07 Aug 2020 14:08:37 GMT

Hi Cheran,

Due to the way that the composition engine works, the %refpage value will not always be correct when you are not composing the whole division (and with forward references you may even need to compose the whole division twice).

Details: the pages being composed are made into a separate "input stack" that is composed, and that affects the in-progress page numbers. Even if composition tried to do a better job of accounting for this in the page numbers saved for <rx>/<rf>, while the composition is in progress it will never be able to fully account for cases where there are forward references and e.g. the compose Range+ operation might result in fewer pages or more pages (before the <rx> occurs).

It's the purpose of the Compose Xrefs function (compose -sx for command-line or Xref Errors from compose menu), that is performed after the "regular" composition is done (and all the composed pages are reassembled back with the other pages), to account for this and "fix up" (or recompose) the lines with <rf> macros on them.

So in your Range+ testing (outside of Looseleaf), try doing the "Xref Errors" composition after you do the Range+ composition and see if that doesn't get you the desired results.

In Looseleaf mode (and I assume you mean Auto-looseleaf), if you have the "Compose Changed Cross-References" field in the ALL spec set to 'yes' then Looseleaf composition will perform the Compose Xrefs function on just the composed pages (after it is done with the Looseleaf composition of them).

Hopefully that will help you get the desired results.

Jonathan Dagresta
SDL XPP Engineering