Still WIP:

• is it fine to keep one domain for plugin? I didn't get the exact outcome of the task;
• this still miss the Messages.sh files to extract the translations.

I will update the review with the Message.sh files when the it's clear how to split the translations, and also when we have a solution on the problem of the credits for the translators for the old translations.

In D8049#150249, @ltoscano wrote:

Still WIP:

• is it fine to keep one domain for plugin? I didn't get the exact outcome of the task;

I'm not really sure what that means, but I guess it's ok.

I will update the review with the Message.sh files when the it's clear how to split the translations, and also when we have a solution on the problem of the credits for the translators for the old translations.

I can only get names of all translators currently in teams, ignoring if they actually contributed. Would that be enough?

In D8049#151465, @drosca wrote:

In D8049#150249, @ltoscano wrote:

Still WIP:

• is it fine to keep one domain for plugin? I didn't get the exact outcome of the task;

I'm not really sure what that means, but I guess it's ok.

It deserves a better explanation, I agree.
Before the import there was a translation file for each plugin. One translation file == one translation domain.
This patch uses the same structure. The other possibility is to use a unique translation file for every message in the repository.
Should I proceed using this structure or should I go for one file?

I will update the review with the Message.sh files when the it's clear how to split the translations, and also when we have a solution on the problem of the credits for the translators for the old translations.

I can only get names of all translators currently in teams, ignoring if they actually contributed. Would that be enough?

Uhm, my experience with transifex is the people registered in a team are much more than that the people that contributed.
I've seen in other projects that when translations are defined/exported in gettext format, the credentials for people who contributed are added in the comments of the file. But I never managed transifex projects, so I'm not sure if it's possible to just export in gettext or it depends on some settings defined for the project.

If you want, I'm willing to check how it works on the transifex side if you want to give me access to the project.

In D8049#151865, @ltoscano wrote:

It deserves a better explanation, I agree.
Before the import there was a translation file for each plugin. One translation file == one translation domain.
This patch uses the same structure. The other possibility is to use a unique translation file for every message in the repository.
Should I proceed using this structure or should I go for one file?

This is fine, it should use unique file for each plugin.

Uhm, my experience with transifex is the people registered in a team are much more than that the people that contributed.
I've seen in other projects that when translations are defined/exported in gettext format, the credentials for people who contributed are added in the comments of the file. But I never managed transifex projects, so I'm not sure if it's possible to just export in gettext or it depends on some settings defined for the project.

If you want, I'm willing to check how it works on the transifex side if you want to give me access to the project.

I've sent you Project Maintainer invitation now.