🚀 go-pugleaf

A few clicks back someone mentioned that the pressure on Adobe would increase if another product could overcome this bug (a I regard it). 
Ventura 10 (and previous) can! So the competition is there (even though Ventura users hardly know how and hence don't use the funcionality (it's no a feature). 

Personally this particular bug is somewhat annoying (i.e. disasterous) in my line of work. Among others I have a job that: consists of 78 products. Each product has 22 predefined documents in a book file. 
   Each document is then build up and around text insets solely. The reason is that one text-inset can be anything from lines to pages in size, and are being reused in any one the 78 products. 

To add to this each manual has to be written in 12 different languages. 

Since any kind of x-ref including markers are inoperable using text insets the idea of creating PDF files has for the present been put aside for better times. 

Now I don't what Adobe needs in order to fix this. What/when is a company a major company? In this case the total number of pages is awesome. The entire refrigeration industry world wide are dependent on this functionality (but can learn to live without). But since FrameMaker is an excellent piece of SW only three licenses are enough to control this system of products, manuals, text insets etc. 
Imagine that these manuals had to be done in MS Word. No doubt that Microsoft would correct the bug, from the mere fact that it would require tons of licenses in order to meet the quality, timeframes etc. The revenue from these licenses alone would warrant the correction of the bug. 

I too have found the discussion to be interesting and least has proven to me that Adobe clearly regards FrameMaker as a product that does need that much attention. Adobe seems to have gone into an InDesign orbit. Of course InDesign is of own breed, while FrameMaker is the ugly duckling they felt they had to acquire. 

keep smiling 
thomas bro