and you will see that the left side bar with the navigation buttons is not reproduced and in general a very crude version is printed.
With Freeway, the printed version is normally the same as the screen one.
This is because Rapidweaver’s ‘Themes’, which are a combination of Templates and CSS and possibly script, and which determine the look and feel of the web page, use external CSS, with separate, often very crude CSS for printing.
Freeway uses inline CSS, with the possibility of adding additional external CSS.
I was trying to make a hard copy so that i could measure the site elements, to reproduce and better it in FWPro. I found this impossible due to a limitation in RW… One more reason to switch to FW.
I will now use a screen dump.
I know that CSS was designed with screen displays in mind and that a web designer has to resign himself to giving up a lot of control as to how the viewer chooses to adjust his browser, ie switching off the printing of background images to save ink… All I was trying to show was a possible advantage to FW’s use of internal CSS. I have seen FW slated for this.
“if it is important that a page prints correctly, a print specific stylesheet should be used”
Do you mean that you can over-ride a user’s background switch-off setting with a suitable external print CSS?