| -----Original Message----- | From: [EMAIL PROTECTED] | [mailto:[EMAIL PROTECTED] On Behalf | Of Joel de Guzman | Sent: 26 November 2006 10:54 | To: [email protected] | Subject: Re: [Boost-docs] [quickbook] Indented section, almost. | | Paul A Bristow wrote: | > | Will it help if we allow: | > | | > | [section One] | > | [ section Sub One] | > | | > | ...some stuff here... | > | | > | [ endsect Sub One] | > | [endsect One] | > | | > | | > | * make white space after the markup tag legal | > | * allow optional titles for endsect which, when present, | > | enforces validity of sect/endsect | > | > I like both of these, but I think the second with titles | especially is the best - means more typing but worth it IMO. | > | > (Aside I strongly recommend using explicit section names | like[section:subone Sub One] because experience shows that with the | > automatic names generated the links to section otherwise | become far too long, for example | > | > [section:subone Substantial One Title on the Important of | using Quickbook] | > | > leads to links going way off the page). | > | > My reasoning is that there is often lots of stuff inside | sections, so it is easy to get confused. | > | > I think it will also have the side effect of reducing the | unhelpful messages from unmatched []s. | | Good points. | | > I presume the name matching is to 'manual' short name? | | If present, yes. If not, then the normalized title, as usual. | Thus: | | [section:id This is the section's title] | | [endsect id] | | or: | | [section This is the section's title] | | [endsect This is the section's title]
This would be excellent. Paul --- Paul A Bristow Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB +44 1539561830 & SMS, Mobile +44 7714 330204 & SMS [EMAIL PROTECTED] ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Boost-docs mailing list [email protected] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
