[OSM-dev] Improved i18n diff script for railsport translators

[andrzej zaborowski]

2009/6/23 Vitor George <vitor.george at gmail.com>:
> On Tue, Jun 23, 2009 at 10:34 AM, Ævar Arnfjörð Bjarmason <avarab at gmail.com>
> wrote:
>> And what's so bad about editing .yml files directly anyway? Of all the
>> apps I've translated. Some with launchpad, some with .po, and some
>> with home-made systems translating the railsport has been the least
>> pain of all of them. I can use my editor directly without any
>> translation app or web UI getting in my way.
>
>
> I've no problem in editing directly the file. The problem is that if the key
> structure changes, it's difficult to keep track of them in the already
> translated files. We had this problem when we were translating the main site
> to Portuguese. The en.yml changed a lot so we had to spent some time just to
> fix the correct places of the strings.

That's a frequent problem in big projects not specific to
translations: when you're adding a new feature for some time you have
to work on a copy of the project while upstream evolves.  So as long
as your files are not merged upstream you'll have to track all changes
and update your code yourself and that's why it's good to attempt a
merge as early as possible and only work with small unified diffs
later.  Hopefully once your file is in the SVN (and pt-BR.yml is)
someone who makes a big change in en.yml also adds or restructures all
the keys in the other files and you only have to worry about adding
translations for them, so the first problem goes away.

Cheers