feat(i18n): add translation resources

[ocBruno]

I plan on looking for bilingual volunteers to help properply translate these documents and correct the mistakes if anyone has any suggestions please let me know!

Changes proposed in this pull request:

• Add 8 other most used languages on the internet to static i18n translation resources with initial
  rough translations from google tranlsate.

[jackcmeyer]

This is an awesome pull request! Thanks for going through and doing this. It will be crucial to have these files continuously updated as new features get added

[fox1t]

First of all, thanks for this PR! It is really appreciated :)

Secondly I think we need better folder and file structure. We can use "app sections" as top level folder and the inside it create language sub-folders. What do you think about that?

Structure changed since review

[jackcmeyer]

As @fox1t mentioned, we should organize the translations by app sections.

For example instead of the app-sections folder there would be a patients folder and appointments folder.

[vercel]

This pull request is being automatically deployed with ZEIT Now (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://zeit.co/hospitalrun/hospitalrun-frontend/ilqprkh66
✅ Preview: https://hospitalrun-frontend-git-fork-ocbruno-add-translation-resources.hospitalrun.now.sh

[fox1t]

Hello @jackcmeyer @fox1t @irvelervel and @tehkapa,
Despite a couple difficulties, I updated this branch and refactored the translations into their own separate folders as requested and fixed a couple test and lint issues along the way.
If anyone has any ideas on the next steps we should take to improve the integration of i18next and internationalization leave me a comment!

An idea I have is for the static resources we should gradually add the necessary translations with the help of other bilingual people. We can place a good first issue to leave pinned on the issues page which attracts new contributors worldwide with a simple first issue.

Nice idea. I completely agree that we need an issue to track all languages we support, where we can update a checklist (pinned). Then we will open an issue for a single language.

[jackcmeyer]

Looks like there is some missing translations (check out the preview and you can see the ones that are missing)

[ocBruno]

Looks like there is some missing translations (check out the preview and you can see the ones that are missing)

Hey @jackcmeyer,
I'm going to try to keep the english and portuguese translations up to date and I can help search for some bilingual contributors to help us out, create some good first issues or something along those lines.
Still have to fix some tests that are failing.

[matteovivona]

@ocBruno any news?

[ocBruno]

@ocBruno any news?

@tehkapa
I had updated english and portuguese to all necessary translations, not sure what else, if anyone has any other requests drop them here .
Just noticed the conflicting files so I will take a look at it later and resolve that later

[fox1t]

@ocBruno Any news about this PR? I think this is a needed feature and you done a good job.

[ocBruno]

@ocBruno Any news about this PR? I think this is a needed feature and you done a good job.

Hey @fox1t,

I started working two weeks ago at a new company and have less free time, if someone wants to keep working on this feel free but for now I will be working on one issue at a time and I am trying to wrap up the input-validation on components library before returning to this one.

Last time I checked this I was unsure exactly what else was needed to finish. I think we should create an issue for separate languages for new contributors to do some translation for the static website data.

[fox1t]

@ocBruno there is only one thing left to do: resolve the conflicts. After it, we can land it on master! :)

[jackcmeyer]

Moving this to #1892