Lately I've seen a lot of diffs to .i18n files
that look like this:
- (50 lines with one number of spaces in them)
+ (51 lines with a different number of spaces in them, and one of the
lines is new)
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.
-- brion
Can be done. Will discuss with Nikerabbit tomorrow. This means that 'human
readable i18n' files will be a thing of the past. Nothing new to Betawiki
folk, though :).
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 fter the 1.13 release (after
release, not branching, so that we can do a backport to 1.13 just before
release with the current code base).
Cheers! Siebrand