🚀 go-pugleaf

RE: using the "inset" as part of a book file. If I'm not mistaken any book file entry can only begin at the top of a page / column; this creates a large gap if a given "inset-cum-book entry" follows a short (say 6-15 lines) bit of content on the preceding page. At least it does in all the experiments I've performed). Having said that, allow me to offer an intepretation of the situation: it is only recently that serious professional users of FrameMaker began aggressively modularizing content into text insets for viewing as PDF files. As this new usage model grows it is uncovering omissions in FrameMaker's implementation. Rather than make mumbled apologies or look for ways out, Adobe should recognize that FrameMaker can either (A) be updated and improved so as to provide a bridge into the world of managed content, or (B) pretend that everything's fine and watch its most sophisticated FrameMaker customers migrate to "real" content management systems like ArborText's Epic. Why on earth would Adobe choose path "A" when a repaired FrameMaker could provide both the company and its customers a wonder starting point into the future of managed modular content? From my point of view it's a simple implementation omission (happens every day) and it needs to be fixed.