Wikimedia Bugzilla is closed!

see also the mail in mediawiki-i18n.
http://mail.wikipedia.org/pipermail/mediawiki-i18n/2006-September/000125.html

Created attachment 2741 [details]
patch for trunk

Patch that does localizable the Makebot extension + Kazakh translations

You obviously didn't read the aforementioned thread, where I objected to this
particular approach. Specifically, I object to cramming a load of messages into
the same file, which raises the overhead unnecessarily for people who don't want
foreign language translations to be available. I also object to the
inappropriate use of a global variable.

(In reply to comment #3)
> You obviously didn't read the aforementioned thread, where I objected to this
> particular approach. Specifically, I object to cramming a load of messages into
> the same file, which raises the overhead unnecessarily for people who don't want
> foreign language translations to be available. I also object to the
> inappropriate use of a global variable.

You are welcome to propose a better solution.

(In reply to comment #4)
> You are welcome to propose a better solution.

The callous:

All extensions are provided with English-language messages for interface
provision purposes. Local wikis can edit the MediaWiki namespace if it's needed,
as before.

The less FITH:

Extensions can provide a number of optional .i18n files in some format
(serialized?) which act as stubs called to override the English translations, in
a similar, but smaller-scale method, to what we use for the software proper.

The implementation that many extensions currently use is rather slapdash, and as
I recall, was the last (and least damaging) of a series of changes which broke
the core code unpredictably, and had to be reverted. It should be regarded as a
short-term measure.

Perhaps a discussion should be started on the mediawiki-i18n mailing list to
achieve this aim?

As of r18375, MakeBot can be internationalised in a decent fashion.

(WONTFIX because I didn't apply that patch)