Some translation work: fixes and languages

[mgesteiro]

The initial goal was to translate into Spanish the new additions from my previous commits, but I discovered some problems and tried to solve them:

• Some translation blocks weren't working correctly: they were lost when extracting the labels. After some digging and reading the documentation I managed to solve the issue simplifying how the translation annotations were being made (and correcting them), mainly in the design.html file.
• Many language files where outdated: after the template is updated, the *.po files should also be updated. There is now a complete English and Spanish translation.
• The translation percentage table in the README.md wasn't updated: there is now a tool to automate/simplify the process (and is now up to date).
• Some typos and LOTS of trailing white-spaces and non-uniform indentations.

Please, review this PR carefully and let me know if any change is required.

[cavearr]

Hi team!!! you're incredible! i'm reviewed the changes and like a lot, to start to try i merge now but @mgesteiro please read some @TimRudy 's comments about the translations and apply in new pull request i think are very good appointments.

Thanks again!

[mgesteiro]

I have checked all @TimRudy comments and will send a new PR with the updates (as you asked @cavearr). Some additional notes:

• Changes in the en.po file come from changes in the source code: when reviewing this file, please include the commentary line indicating the original source file and line number to go directly to it (helps!)
• When executing the translation scripts/tools, many files get changed, but that doesn't mean I have done any work on them, so bear with me if something breaks and just let me know to get it fixed.
• Thanks @TimRudy for the review: I appreciate the effort and time you've put into it.

[TimRudy]

This reminds me I saw a “python” and perhaps all should be “Python”, thanks

…

Sent from my iPhone

On Feb 3, 2023, at 5:49 AM, mgesteiro ***@***.***> wrote:  @mgesteiro commented on this pull request. In app/resources/locale/en/en.po: > msgid "Invalid <i>Pull up</i> connection:<br>block already connected" msgstr "Invalid <i>Pull up</i> connection:<br>block already connected" -#: app/scripts/services/graph.js:304 +#: app/scripts/services/graph.js:312 msgid "Invalid <i>Pull up</i> connection:<br>only <i>Input</i> blocks allowed" msgstr "Invalid <i>Pull up</i> connection:<br>only <i>Input</i> blocks allowed" I prefer pull-up (Arduino influence here). Actually as I'm writing "pullup" github is trying to correct me saying to use "pull-up" or "pull up" 🤦🏽‍♂️ Tricky word, very context dependent... — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

[mgesteiro]

This reminds me I saw a “python” and perhaps all should be “Python”, thanks

welcome!
I'm learning as I go (English is not my mother language), and "pullup" is also valid (at least dictionary wise), but with idioms (and language in general) is always a very subjective matter.