"Simetrical" Simetrical+wikilist@gmail.com wrote in message news:7c2a12e20803051623r6641fc3exb0b70201808220b2@mail.gmail.com...
On Wed, Mar 5, 2008 at 1:16 PM, Mark Clements
gmane@kennel17.co.uk wrote:
If no string is defined, then hyphens become spaces and each word is capitalised (or
rather,
put into appropriate title-case for the interface language).
I don't see any reason to avoid our usual method of printing messages that <arent-defined>. It's ugly, but it should be, because something or other has broken. I doubt it would be an issue anyway, so adding special logic to handle it is pointless and bloaty.
This is slightly different though. As the section names are extensible, we would be in a situation where every extension that is not in one of the built-in section would need to include the interface text for it's section heading. If two extensions in the same section differ in their default text, which one has precedence? What happens if this section name is later added to core? If extensions can just use a sensible English name knowin that the default rendering is normally sufficient then it makes things a lot easier to maintain, plus we still have the full flexibility of the localisation system. Once this is in use, I envisage that sections that have a sufficiently high number of common extensions in them will have default labels added to core, even if core doesn't have any extensions in that section itself.
A global variable $wgSpecialPageSectionOverrides allows sections to be overridden if necessary (key is name of special page, value is new
section
to put it in).
I'd say just go with a hook in the SpecialPage constructor. It seems simpler and more flexible. I don't think such a narrow feature needs its own config variable.
To be honest, I added that in response to the e-mail, where it seemed to be desired functionality. I'm not sure how useful it would be in practice. I will leave it out for now.
- Mark Clements (HappyDog)