To further refine some answers here about publishing, as mentioned, Print Preview does require <u>either</u> a Print Composer add-on installed (and licensed) on the client<u>or</u> access to the Pubishing Engine somewhere on your network to use. If you have access to PE, you don't need the Print Composer Add-on installed.
Without either of these options, your only output would be the "Editor View" being sent to any installed print driveron your computer, which obviously does NOT give you a "published" output. (Editor View is also sensitive to which window the cursor is in, meaning if the cursor is in the docMap window, that will be the output source.)
Assuming you can compose and get to Print Preview, the "View=> Options=> Extended Pages" only shows you information on the printed page that oversets the pageset. I've had oversets that were enough to fill 5 more pages run off the bottom of the page without the system crashing. Point is that the option won't prevent a crash in and of itself. Using this option is great if you have data running off the bottom of the page due to some problem with your stylesheet or the content and need to see it. It won't print, but you can at least see it on the screen. However it makes navigation through the Print Preview a bit more cumbersome. Normally, it is left off unless you specifically need it.
The DCF file is only involved here with your original question about the "allowComposeStylesheetList" option. This option set to "yes" will turn on a drop-down list of available stylesheets to use at composition time. If set to "no", there is no list and the default "print" stylesheet is used. However, you won't get to the "Print Compose" dialog if you don't have one of the above-mentioned composition options installed.
Hope this helps,
When you do get Print Preview up and running, don't forget to select View->Options->Extended pages in Print Preview if it keeps crashing on you after a few pages.
Thanks to Mr. Nagai for posting my question. I will try the solutions suggested. Looks like I can't do a lot about print preview since the company installed without a license.
Ifound a .dmp file on my system andsent it to PTC. PTC had someone review it and identified the problem as being related to tables in generated text. My stylesheet generates semantic tables for various semantic information. There appears to be a problem saving these documents when a table is shown in generated text. There is, apparently, no workaround other than upgrading to 5.3 M140 or later. I can’t guarantee that will help, but it’s worth a try.