On 04/19/2010 11:52 AM, Strainu wrote: then create a template {{man|command}} for example masti

On Mon, Apr 19, 2010 at 12:13, masti <mastigm(a)gmail.com> wrote: Sounds like a good solution, to me. Though I would go for {{man|N|foo}} as some manpages exist in several namespaces. Though the next problem you will encounter is that not all manpages are the same across Linux, *BSD, other Unices leading to {{man|Linux|N|foo}} But then, you have problems with different distributions and versions leading to {{man|Linux|Debian|N|foo|$foo_version}} or {{man|Linux|Debian|N|foo|$debian_release}} or other combinations of all the above. I am not saying this is not a worthwhile goal, I think it is. Very much so, even. Still, getting this right might not be as trivial as it may sound, initially. Richard

Platonides wrote: I might even go for {{man|passwd|5}} instead of {{man|passwd|section=5}}. Numbered parameters can be optional too. -- Ilmari Karonen

* Chad <innocentkiller(a)gmail.com> [Mon, 19 Apr 2010 13:10:46 +0200]: only Perhaps something like this (an extension, core is unmodified): $wgParserConf['class'] = 'MyParser'; class MyParser extends Parser { function doMagicLinks( $text ) { ... parent::doMagicLinks( $text ); ... } function _checkMagicWords( &$text ) { $man = false; $mw = MagicWord::get( 'MAN' ); if ( $mw->matchAndRemove( $text ) ) { $man = true; ... } return $man; } } Dmitriy