Using AMOS tool for language pack translation

How to review latest integrations in a language pack?

 
Picture of German Valero
Re: How to review latest integrations in a language pack?
by German Valero - Wednesday, 20 June 2018, 10:35 PM
Language pack maintainers

Hi Séverin and David,

Could it be possible for the language pack maintainer to have two AMOS usernames: one as a maintainer and another as a mere contributor ?

This way the maintainer would send all the work as any other contributor would do, but when he/she logs in as maintainer, could fast-track approve the work.

And there should be a #xxxxx number for all the work the maintainer_working_as_a_mere_contribuitor did.

It sounds cumbersome, but it might be a good way to keep a record of translations done in a needed hurry (too aften the case), so that the maintainer can later carefully slowly re-check and fix any human error (e.g, on a quiet weekend).

I reckon I have made some very silly typos in many strings in the few years I have maintained my language pack, but I had never thought about a way to double-check myself.

Picture of Séverin Terrier
Re: How to review latest integrations in a language pack?
by Séverin Terrier - Thursday, 21 June 2018, 4:36 PM
 

Hi German,

I feel it's a bad idea that the maintener should have two accounts!

But it could be a good idea if addition he makes are tracked the same way as other users.

For that, does he need to (and can he) create a stash, and a contribution (that he would check himself) ?

Séverin

Picture of Iñigo Zendegi Urzelai
Er: Re: How to review latest integrations in a language pack?
by Iñigo Zendegi Urzelai - Thursday, 21 June 2018, 5:56 PM
 

Hi there,

Would there be a (better, easy) way to see details of recent integrated language string, to be able to review them, and correct them if needed?

We'd really appreciate that feature: in the Basque language pack nowadays we're several contributors translating strings, and there is only one maintainer approving them. We're thinking on changing this process and upgrading two contributors to maintainers in order to share out the work, but we want him to remain being the lead maintainer. To achieve that, it would be great if he could see and easilly review all maintainers' changes.