<snip>Just to follow up on this, I'm plan to check this in if no one objects or has a better approach. I've put up a wiki page to demonstrate the effect of the changes:
<http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl?Boost_Documentation_Format/CSS_Change_Proposal>
If it is necessary, could these two (programlisting & screen) be split up where one has the padding but no margin?
I don't know, I kind of like having the code indented. It helps it stand out against the background text, and it's consistent with other elements, like tips and notes, which are also indented. And I really don't like the idea of having a margin on screen but not programlisting. Seems inconsistent to me. But I'd like to hear other opinions.
Are you just worried about code in tables? If so, you can hack the CSS to avoid the margin when the programlisting is in a table cell.
-- Eric Niebler Boost Consulting www.boost-consulting.com
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Boost-docs mailing list [email protected] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
