openerp-expert-localization team mailing list archive

[Raphaël Valyi <rvalyi@xxxxxxxxx>]

Hello Lionel,

First, some 3 months ago, I proposed Fabien to flag specialized commits
fixing things like translation keys with a special flag to explicit what the
commit exactly consists of. For instance, like we have [MERGE] or [FIX]
would could have [TRANSLATION_KEY]. That would make it dramatically easier
to track the commits and update what should be updated rather than getting
the chaos of all commits to analyse...
But I'm afraid, he refused under the pretext Tiny can't change their habits
of non qualified commits (which unfortunately I can believe)...
Now he told that he wanted this to be automated. Right, still, nothing is
automated and rather than the better solution, I would have been happy with
a good only solution...
So if somebody want to automate such a bot, be my guest...
My idea is that it could be a Google Wave bot commenting with
special filterable tags on a Google Wave (or similar product with same
richness) that would be subscribed to the trunk commits feed and hence have
an entry for each commit.

Second, I think using a "sed" script to automatically change all wrong
English terms in the whole source tree (including po translation files) and
replacing them by the correct terms is valid. Don't you think so? If not,
why? I think it would just change all occurrences, including translation
keys, then it will just work, no?
We did that here and as far as we tested that worked:
https://bugs.launchpad.net/openobject-addons/+bug/326160

Of course, this doesn't remove the need for fuzzy translation tools, but may
be we can already fix lots of things using sed, no?


Raphaël Valyi
http://www.akretion.com


2010/2/16 Équipe informatique <informatique@xxxxxxxxxxxxxxxx>

> Dear l10n experts,
> In the IRC meeting last friday, I expressed my concerns with the current
> state of English strings in OpenERP.
> A lot of strings should still be fixed or clarified, but we must try to
> keep the existing translations as much as possible.
> Does anyone have an idea of how we can change the English strings in the
> source code, and still keep most of the translations?
> GNU gettext has a feature called "fuzzy strings" to adresse this, but
> Launchpad doesn't support this and this is not top priority for them - see
> https://blueprints.launchpad.net/rosetta/+spec/rosetta-fuzzy-merge .
> Any idea?
> Yours,
> Lionel.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-expert-localization
> Post to     : openerp-expert-localization@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-expert-localization
> More help   : https://help.launchpad.net/ListHelp
>
>