[Feature Request]: Keep localization files up to date

[mrbass21]

Is your feature request related to a problem? Please describe.

Recently I put up a MR for for some changes to an article and decided to make the same small change in the es/ folder, but then noticed that file does not yet exist for es.

I decided to create it and use Google Translate to pre-fill it with what was already in the English file. In creating that new file, the new file linked to a couple more files that existed for en, but did not exist for es.

I used the same strategy, but in reviewing, I even found an es page have in Spanish and half in English.

It seems fairly obvious that the es docs have become a second class citizen and are either non-existent, or inaccurate. I'm happy to contribute to try and address this, but got to a point of personal POC where I thought I should get input from maintainers.

Describe the solution you'd like

I think a good thing to do would be to create a Github Action to check for any missing localization changes and give that feedback on the MR. I've already started building a script to try any create this logic, but there are some questions about process that I don't think I can answer myself.

I don't know it should fail the build if it detects, for instance, that an en file was mutated, but an es file was not. It could be intentional. Maybe it should fail and the maintainers can simply ignore the failure and merge anyway, but I hate normalizing job failures.

An alternative would be to simply post a comment to the PR with a message that lists the files missing localization changes as a "heads up".

Describe alternatives you've considered

I did not consider any other options. I generally don't like importing more libraries or software. I wanted something simple to just inform the MR author that localization was missing.

There is also the obvious problem that Google Translate is not a reliable translator, but given this is an open source project without significant dedicated resources for localization, I think it would be better to use Google Translate for a "best effort" translation and let native speakers open subsequent PR's to fix bad translations and at least have some correct localization rather than it not exist at all.

Additional context

No response

[TheSCREWEDSoftware]

Same as the OS's one, English the official and maintained one, we used to have @pangolp to keep ES one update to date, it's up to anyone to provide fixes / changes / pr to it.