{resent about an hours after first try)
---
Can be done. Will discuss with Nikerabbit tomorrow. He just left for bed.
This means that 'human readable i18n' will be a thing of the past. To us it
was already that, anyway :)
Would you suggest a rebuild of all localisation files in one go to get rid
of your observed obscurity, or would you like it to trickle through over
time?
I suggest we make the proposed changes only after the 1.13 release (read:
release, not branching, so that we can do a backport to 1.13 just before
release with the current code base).
Cheers! Siebrand
-----Oorspronkelijk bericht-----
Van: wikitech-l-bounces(a)lists.wikimedia.org
[mailto:wikitech-l-bounces@lists.wikimedia.org] Namens Brion Vibber
Verzonden: dinsdag 15 juli 2008 22:41
Aan: Wikimedia developers
Onderwerp: [Wikitech-l] On localization file formatting
I think it would greatly simplify change tracking if we used more
consistent spacing in the localization files, eg changing this:
+ 'Search' => array( 'Sichen' ),
+ 'Resetpass' => array( 'Passwuert zrécksetzen' ),
to this:
+ 'Search' => array( 'Sichen' ),
+ 'Resetpass' => array( 'Passwuert zrécksetzen' ),
While it's cute, and sometimes helpful, to align columns in files that
are manually maintained, this:
1) Has no benefit to localization done via BetaWiki
2) Obscures the actual changes made in a commit when the number of
columns gets bumped, making overall code maintenance more difficult.