On 9 October 2011 21:52, Daniel Friesen <lists(a)nadir-seen-fire.com> wrote:
On 11-10-09 11:20 AM, Platonides wrote:
What I've been thinking isn't so much putting
translations in another
repo, or even TWN doing any commits anywhere at all. Frankly the whole
idea of TWN reading and writing .php files has felt completely messed up
to me anyways. Sure our canonical message forms can be in .php, but
having the semi-automated system we use to translate to every other
language we support output php files feels like a relic of a time before
it existed and a band-aid hack just to make it possible for TWN to do
translations back then.
Huge +1. I would sincerely welcome a move away from PHP-based i18n
files. Having data in executable format is just stupid imho.
I'd like to make TWN the proper source for all the
translations. Rather
than TWN spitting out php for non-en, we have a proper generated output
format for translations, and MediaWiki uses that instead of .php for our
translations. Instead of TWN having to make this a commit somewhere, I
think we should pull those translations right from TWN once we need them.
I'm not sure I want to add that burden to TWN right now. It's just
single vserver with no uptime guarantees.
I'm not opposed to the idea though - having efficient l10n update in
the core, enabled by default, providing always up-to-date translations
and perhaps also loading new languages on demand[1] would soo awesome.
But like I said, that would need some serious effort to code and to
make stable and secure content distribution channel. Any volunteers?
:)
[1] This would also satisfy those who think that including all l10n
makes the tarball too big
-Niklas
--
Niklas Laxström