RFC: add more details on translations and moderators

[dwmkerr]

Hi translators, I'd love to tidy up the links to the translations, ensure that there's an option to sponsor the moderators, and make it clearer to contributors how to either update a translation, or create a new one. I'd love your comments and thoughts - also would it make sense for the moderators to be able to be reviewers/mergers so that they can update the actual translations? See PR #220 for an example of why this is important!

@LeoFC97 @nusr @viktodergunov @KevinBockelandt @0gap @csparpa @codeanddonuts @solarrust @manuel-rubio @umutphp @yoneda @arywidiantara @troyane @iegik

BTW - @umutphp and myself are chatting to the GitLocalize team and they've already made some updates to the platform for us, so if anyone wants to suggest improvements or changes for GitLocalize then just give me a shout. I want to make it as easy as possible for this group to manage changes. I'd also love to do anything I can to make this rewarding - so if you've got ideas on how to get sponsorship, support, anything, just let me know!

[umutphp]

Hi @dwmkerr,

As the repo is becoming very popular, the list of translations is getting bigger and bigger. So It started covering the topmost section of the content. Having a separate section at the bottom for translations and linking it makes sense :). Additional to this, I think having a review step in translation process will really help to improve the translation quality.

[KevinBockelandt]

Hello everyone,

would it make sense for the moderators to be able to be reviewers/mergers so that they can update the actual translations? See PR #220 for an example of why this is important!

I think it does yes. Or you could ask for each language moderator to check the corresponding PRs before merging them yourself, which is fine by me too.

if anyone wants to suggest improvements or changes for GitLocalize then just give me a shout.

Yep, after using it for a few hours there are few things that could make the task easier I think:

All the links internal to the documents are given as-is without any kind of automatic treatment.

For example:

When translating I need to change:

1. the title of the link (that one is obvious)
2. the slug (not sure if it's the right word, ex: loi-de-moore). When it could actually be generated from the new title
3. every reference to that new title needs to be changed by hand in the whole document.

It feels like a lot of time spent on something that could be done automatically. Especially since the way the application is done prevents you to be able to do some kind of search & replace.

Search & replace

Related to that but not only. A search & replace function would be really nice. For example in this document we have a bunch of "See also:". It's always the only thing in the block and it's always translated the same way.

It would be nice to process all of them at once instead of having to do it manually for each one.

Possibility of marking the blocks as not finished

Right now as soon as you work on a block to translate it's not grayed out anymore. For most blocks it's not a problem since they are small enough that you can complete them in one go. But the list shown in the previous screenshot for example is quite massive.

It would be nice to be able to work on the block and still indicate the work is not completed so you don't have to remember it yourself.

[dwmkerr]

Thanks @KevinBockelandt and @umutphp - I'll mail the GitLocalize team and see if they've got someone who can join this convo and take the issue requests.

Unless anyone has any objections over the next few days, I'll also merge this update as I think with the number of translations increasing, it's useful to move the detailed table lower down, with just the flags as links at the top.