On Tue, Feb 20, 2007 at 12:49:16AM +1100, Steve Bennett wrote:
On 2/18/07, Jay R. Ashworth <jra(a)baylink.com>
wrote:
Well, one suggested solution was piping the
==section header tag|secthead==
One obvious weakness with this is we don't have a way of terminating
sections. Granted, that's a problem in general with sections of this
sort, but it crops up here. Perhaps we would allow something like this
as a terminator:
==|==
(pretty isn't it :))
Sections terminate at either the next section header marker, or the
next one at that level -- doesn't matter which, as long as it's
declared at release time. Both have advantages.
but while I
understand why that is most intiutive to people who *get*
Wikipedia, I suspect it's a bit too breakable when confronted with
people who don't--and there are a lot more of them. So I like a
template or parser function that takes an argument and expands to the
appropriate hidden markup to support the pointer, myself.
So something like this?
{{section header tag|secthead}}
Or do you mean:
==section header tag==
{{sectionmagicword|secthead}}
The latter, yes. If you're tagging something for remote retrieval, you
want the tag decoupled from both the accidental section number, and
the human changeable section header text.
Cheers,
-- jra
--
Jay R. Ashworth jra(a)baylink.com
Designer Baylink RFC 2100
Ashworth & Associates The Things I Think '87 e24
St Petersburg FL USA
http://baylink.pitas.com +1 727 647 1274