Quoting chris <jugg@xxxxxxxxxxx>:
Yet if the Syntax page could be generated, rather than static, then perhaps plugin's syntax could be inserted into the normal Syntax page layout. Plugins could specify what heading their syntax falls under in the Syntax page, and whether they override the default syntax. eg. Control Macros syntax section could be appended to by other plugins implementing such markup. Other Syntax Highlighting plugins could be inserted into the correct location (or even override the default Syntax Highlighting section).
Exactly! Yes, more work for the core developers (to create a framework to do this) and more work for the plugin developer, but it would make life a *lot* easier on wiki admins, especially the technically challenged admins.
... probably should just be the responsibility of the local wiki admin to update their syntax page accordingly.
One one level, yes. But then, how many people use Dokuwiki because it's easy to setup and use and have little or no idea how to update the syntax page. Yes, they can learn, but...
Although that is a lot of duplicate work for wiki admins. So even just having text in dokuwiki markup format that each admin could copy/paste into their syntax page would go a long ways.
Sure, an adequate stop-gap measure for sure. But like most stop-gap measures, they become a standard, and then "that's the way we do it!"
Walter -- DokuWiki mailing list - more info at http://wiki.splitbrain.org/wiki:mailinglist