Jerry Schwartz escribió: >> -----Original Message----- >> From: dokuwiki-bounce@xxxxxxxxxxxxx [mailto:dokuwiki-bounce@xxxxxxxxxxxxx] On >> Behalf Of Chris G >> Sent: Tuesday, February 23, 2010 12:45 PM >> To: dokuwiki@xxxxxxxxxxxxx >> Subject: [dokuwiki] Re: Can one make a heading also a link? >> >> On Tue, Feb 23, 2010 at 01:53:30PM -0300, Luis Machuca wrote: >>> Chris G escribió: >>>> On Tue, Feb 23, 2010 at 11:49:05AM +0100, Michael Klier wrote: >>>>> On Tue, Feb 23, 2010 at 10:44:48AM +0000, Chris G wrote: >>>>>> Is there some easy way of making a section heading also a link? It >>>>>> would seem that this is a pretty normal requirement but I can't see >>>>>> any obvious way to do it? >>>>> No this is not possible due to how the parser works because headlines >>>>> are >>>>> "special" - also this has been asked and answered a gazillion of times >> here >>>>> on the mailinglist as well as the forum - and sursprise surprise - it's >> even >>>>> a faq entry: >>>>> >>>>> http://www.dokuwiki.org/faq:headerlinks >>>>> >>>> Oops, sorry! Doesn't actually help much though as the tips it points >>>> to show lots of ways of changing the style of a heading but no way to >>>> get a link in a different style. >>>> >>>> There is a workaround if you do it in HTML though:- >>>> >>>> <html><h3><a href="http://www.somewhere.com";>Heading >> Text</a></h3></html> >>>> Maybe this could go in the FAQ? I'm quite happy to add it if it's >>>> thought reasonable. (It needs htmlok to be ticked of course) >>>> >>> That's understandable -- no links or any other sort of content in headers >>> is >>> *wanted behaviour*, since titles are titles, and also a god thing >> accesibility >>> wise. >>> >> Well I wanted it! :-) >> >>> A link in a / as a header, IMHO, essentially says: "sorry, what goes below >>> here should go into its own page instead, but can't get myself to move it". >>> It strongly deviates attention from the current content, and what is linked >> in >>> a header may not even be in sync with what the encompassing article says. >>> >> I agree with you that in many/most cases one doesn't want a link as a >> header but it can be sensible sometimes. >> > [JS] I agree. In my particular case, I want the links to appear in the TOC; > but they can't. This requires redundant entries: > > ===== Publishers ===== > ==== Arrow ==== > [[arrow]] > ==== Bow ==== > [[bow]] > ==== Bullet ==== > [[bullet]] > > And so forth. It would be a lot cleaner if I could put the links themselves > in > the TOC, somehow. > > Regards, > > Jerry Schwartz > The Infoshop by Global Information Incorporated > 195 Farmington Ave. > Farmington, CT 06032 > > 860.674.8796 / FAX: 860.674.8341 > > www.the-infoshop.com > > > > > >> In the case in point it's on a page which is a collection of >> information about businesses and such, the headers would be links to >> the business' own web sites and the text underneath is extra >> information that I have collected. It feels very logical to me in >> this case to have the header being a link. It's a very commonly used >> approach, I found an example very quickly:- http://www.htmlhelp.com/ >> >>> The practical way to solve the issue is, of course, not a link in a header, >>> but a link right below a header with some indication such as "See also" or >>> "Main article". >> IMHO that's a bodge working around something you want to do but can't do. >> >> >> -- >> Chris Green >> >> -- >> DokuWiki mailing list - more info at >> http://www.dokuwiki.org/mailinglist > > > Wait... you say you want *links to external content* in the *document TOC*? Now *that*'s bad design. The TOC is expected to have another kind of functionality. Click a link, take you to a specific section in the document itself. There's also the structure and accessibility problems that a header link causes. See not only "Navigation Mechanism" on the W3C Accessibility Glossary (http://www.w3.org/TR/WCAG10/#glossary), but also Wikipedia's stance on section headings. -- DokuWiki mailing list - more info at http://www.dokuwiki.org/mailinglist