🚀 go-pugleaf

Understood, but from your posts improved support for Word tables and support (that did not exist before) for Excel files seemed like features that you'd find useful on a regular basis. 

Other than that, you can map a master page to a paragraph tag, if you want to use a custom layout for "page left blank," for example, and the improved Save as PDF option is pretty slick and reliable--it's something I'll use regularly. 

$200 for those things . . . yeah, I'd say it's worthwhile. I mean, I agree the upgrade is incremental, a small evolutionary step and not nearly revolutionary if you exclude the SGML/XML change, but I measure the worth of an upgrade in time--my time--and not by how disappointed or excited I am. If I can save myself from having to print XLS to PDF to get the spreadsheet into FrameMaker, if I can avoid the step of converting Word tables to tab-delimited text to bring them into FrameMaker, and if I can import *AI files directly, rather than having to create EPS and then keep source AI files and EPS files around, I'm going to make up that $200 at some point in the next 3-6 months. 

For example, how much time did you spend on the Word table about which you came to this forums? 30 minutes? If (remember, I said "if," I don't know what your source Docs look like), FrameMaker 7 just handled that issue for you, it saved you 30 minutes and your company $25. You're on your way . . .. 

Combining the products into one seems pretty cool on a personal level, because now I get to play with enforcing structure and also with XML--things I personally wasn't willing to commit money to before. That is, I don't see it as an adventure in marketing, although unifying the installed base was probably a good idea from many perspectives, including marketing and support. 

Cheers, 

Sean