🚀 go-pugleaf

I have a text inset that consists of 16 sections: each section describes a command line parameter. At the start of the inset I have a 16-row table that lists (a) each parameter: (b) a one-line description of the parameter; (c) the page number -- as a clickable x-ref -- to a detailed description. This text inset is used in three documents. The final documents are viewed as PDFs by most users. As it stands, the ability to use the text inset's "jump table" in a container document is *broken* unless I also create separate Hypertext links to each section(?) I have a better idea - Adobe corrects the obvious oversight in FrameMaker's handling of x-refs in text insets. It's the right thing to do.