Ruby Rust translation

[collinskoech11]

Make sure you go through the Contributing guide.

Please delete options that are not relevant.

Title

This pull request (PR) is made in reference to:

Description

What does this PR do?

Recommendations for how to test this?

Motivation and Context

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

Testing

• My submission passes the tests?
  • If you did additional testing, please describe in detail how you tested your changes
• I added new tests for core changes, as applicable?

Screenshots (if appropriate):

[welcome]

💖 Thanks for opening this pull request! 💖

We use semantic commit messages to streamline the release process. Before your pull request can be merged, you should update your pull request title to start with a semantic prefix.

Examples of commit messages with semantic prefixes:

• fix: don't overwrite prevent_default if default wasn't prevented
• feat: add app.isPackaged() method
• docs: app.isDefaultProtocolClient is now available on Linux

Things that will help get your PR across the finish line:

• Follow the JavaScript, C++, and Python coding style.
• Run npm run lint locally to catch formatting errors earlier.
• Document any user-facing changes you've made following the documentation styleguide.
• Include tests when adding/changing behavior.
• Include screenshots and animated GIFs whenever possible.

We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can.

[madiedgar]

Hi @collinskoech11, I'd love to add you as a translation contributor. Follow the instructions in #191 to add a translation review. When that gets merged in, I'll merge this one in as well! 😄

[collinskoech11]

@madiedgar @wambugucoder kindly review.

[madiedgar]

Hi @collinskoech11, this is a great start 👍🏾

Due to the nature of the repo, adding a translation actually requires 2 different PR's:

1. The translation into the language-translation branch for a specific language
2. The all-contributors update to master

I'd suggest creating another PR to add your actual translations sw.yml to the swahili branch and then we'll revisit this one to add you to the all-contributors list on the master branch. :)

Some Helpful Tips
When adding a translation, you'll need to start from the swahili-translation branch on your local fork and create a new branch from that specific language's branch (not from the master branch). you can then add your opinion of the translations for the keywords in relation to previous reviewers. I raised #306 to update the style of the locale/sw.yml so it is aligned with our updated style guide (like how it's explained in the #191).

Let me know if you have any questions.

[wambugucoder]

LGTM

[madiedgar]

Thank you for contributing the keyword translations for Ruby and Rust. Could you update the format to the new style for your translations? This will make it easier for people to add their review for the translation.

  False: "uwongo"
    # ✅ @collinskoech11 

[madiedgar]

@collinskoech11 would you be able to raise another PR for Python keywords and builtin translations as well? Our first priority is getting Python reviewed by 5 more people. By the end, it might look like this:

  False: "uwongo"
    # ✅ @wambugucoder
    # ✅ @collinskoech11
    # 🤔 @user1 what about this word ______
    # ❓ @user2 not sure this is the right word
    # ✅ @user3 
    # ✅ @user4