🚀 go-pugleaf

My sincere thanks to everyone for their lively and well presented opinions. First, let me note an interesting inconsistency: Only text insets that are imported by reference have their clickable x-refs damaged when the container documents are generated as PDFs; if a text inset is converted to text within the container document before PDF creation, the inset's cross-references will remain clickable. I consider this behavior vis-a-vis insets imported by reference to be operationally inconsistent. This in turn reminds me of the time I had the misfortune to work with an individual who thought nothing of regularly spending two hours scheming of ways to avoid one hour's worth of work. That is to say that elaborate ratiocinations for why a straightforward and operationally consistent feature ought not to work may be a misapplied effort of analysis. I still strongly believe that the "breaking" of clickable x-refs in text insets that have been imported by reference, then exported as PDF, is a FrameMaker implementation omission, and that FrameMaker would be *much* improved by correcting it. Stated another way, intellectual purity bordering on altruism notwithstanding, neither FrameMaker nor Adobe's revenues will be improved by leaving the anomaly as it is in the hopes that it will encourage users to learn about and migrate to "real" content management systems.