Neither your word processor nor your spreadsheet program can compete with FileMaker Pro at handling structured data, but by the same token, FileMaker Pro can’t compete with your word processor if you need to print very large blocks of text. If you have fields that contain, say, essay-length (or longer) blocks of text, your best bet might be to export that data and merge it in Word.
I agree that Word would handle large blocks of text better but attempting to do a merge in Word seems to raise several issues as well.
The biggest issue is how to do something similar to the sub-summary report where each new author/edition is rolled up under the hero/composer field. My initial attempts result in each record being put onto a new page not combined as a summary. This actually seems to make the problem worse because at least with the sub-summary report I'm getting the records grouped together and only starting a new page when the next sub-summary won't fit.
In addition, it appears that Word 11 for Mac won't recognize the FMP12 format which requires the data to be exported out into another format to be merged. This would need to be done and updated each time there is a change in the original data in the database.
If I can figure out the sub-summary aspect and the pagination problem in Word, I'd be fine with going that route.