Updating to add support to other languages

[oocf]

Thanks for contributing to Gambit! Before you submitting or reviewing a pull request, check out our guidelines for contributing.

The person submitting the PR should ensure it has an informative title and update the headers below, before marking the PR as ready for review and assigning reviewers.

Issues closed by this PR

Add any issues that are being closed by this PR to the list. Use "Closes" or another keyword followed by the issue number.

• Closes #ISSUE_NUMBER

Description of the changes in this PR

Update the description of the changes made in this PR. You can delete this section if the changes are already fully described in the linked issues.

This PR adds support to multilanguage platform, adding a translation in spanish and in french

How to review this PR

The gambit repository contains source code and documentation for several different components. Explain how a reviewer should approach reviewing the specific changes made in this PR.

For example, you might include instructions like:

• "Review code changes and ensure tests cover edge cases"
• "Rebuild the GUI from this branch, then test features X, Y, Z work as expected"
• "Click the link to the documentation page and sense check by reading"

[tturocy]

Thank you for this. i18n is something we have had on our wish list for a long time.

Two points/questions:

1. There are still a lot of moving parts in the GUI as we prepare for 17.0. Because the changes are so major we're unlikely to add i18n for the release because coordinating with the message catalog might be a bridge too far (but we will consider it depending how long it takes for us to do all of our final checking)
2. Would you be willing to help maintain these catalogs as we develop the GUI going forward? We have a bit of competence in the two languages in the development team but no native or truly fluent speakers of either.

[oocf]

Thank you for this. i18n is something we have had on our wish list for a long time.

Two points/questions:

1. There are still a lot of moving parts in the GUI as we prepare for 17.0.  Because the changes are so major we're unlikely to add i18n for the release because coordinating with the message catalog might be a bridge too far (but we will consider it depending how long it takes for us to do all of our final checking)

2. Would you be willing to help maintain these catalogs as we develop the GUI going forward?  We have a bit of competence in the two languages in the development team but no native or truly fluent speakers of either.

@tturocy for

1. I think we can wait until you finished your chagnes in the UI
2. I am glad to help with maintaining the languange I am fluent with Spanish and basic French that is why I added both of them but not in other but we add more community once this has at least these 2 other languages