Egil Kvaleberg wrote:
1. How should translations for extensions be handled?
It would of course
not be a problem adding to the existing resources in phase3/languages,
but does translations for extensions belong there?
You can hook in to the main localization system by defining messages
like this:
$wgMessageCache->addMessage("searchnumber", "<strong>Results $1-$2
of
$3</strong>");
but there afaik isn't a clean standard way of defining different
defaults for each language yet.
2. Should extensions be put in the extensions module
or in the
phase3/extensions directory?
Extensions that go into our main CVS should go in the extensions module.
The MediaWiki distribution bundle is built directly from the phase3
module and should have a clean, empty extensions subdirectory.
At some point it would be nice to have more accessible releases of
individual extensions...
3. Should these 3 extensions be put in the same place
(requiring only
one include in Localsettings.php to enable), or in 3 different
directories?. I am currently using 3 different extensions, but I think
having just one is better. I am also wondering about naming and policy.
"Geo" seems to be taken.
If they go together well and you wouldn't expect to enable/disable them
separately (for instance, for different security needs etc) then it
might make sense to bundle them together for convenience.
extensions/geo currently holds some experimental stuff Magnus was
working on; I'm not sure if this is current.
-- brion vibber (brion @
pobox.com)