Completed the HECommandVariables file

[DanielGevaZA]

Contributor checklist

• This pull request is on a separate branch and not the main branch

---

Description

Completed the HE file from the EN version. Added all the translations for the needed terms.

Related issue

• Add Hebrew keyboard #134

[github-actions]

Thank you for the pull request!

The Scribe team will do our best to address your contribution as soon as we can. The following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :)

If you're not already a member of our public Matrix community, please consider joining! We'd suggest using Element as your Matrix client, and definitely join the General and iOS rooms once you're in. Also consider joining our bi-weekly Saturday dev syncs. It'd be great to have you!

Maintainer checklist

• The commit messages for the remote branch should be checked to make sure the contributor's email is set up correctly so that they receive credit for their contribution

  • The contributor's name and icon in remote commits should be the same as what appears in the PR
  • If there's a mismatch, the contributor needs to make sure that the email they use for GitHub matches what they have for git config user.email in their local Scribe-iOS repo

• The linting and formatting workflows within the PR checks do not indicate new errors in the files changed

• The CHANGELOG has been updated with a description of the changes for the upcoming release and the corresponding issue (if necessary)

[andrewtavis]

Minor suggestions on your PR workflow for the next time, @DanielGevaZA :)

• Putting #ISSUE_NUMBER at the start of your commit is good practice as it then links the commit to the given issue
• It's be great if you filled out the commit message template in the future for your PR commit
  • I'll edit yours for this issue so you can see what we're looking for :)

[andrewtavis]

Also I'm realizing that for this it'd make sense for us to be working on the Scribe-Data issue for this as well now, as we're trying to set up commands, but we haven't set out what the verb tenses are going to be for conjugate :)

Would you want to update the Wikidata query for Hebrew verbs at the following link (directions below):

• Scribe-Data/src/scribe_data/language_data_extraction/Hebrew/verbs/query_verbs.sparql

You can find a Hebrew verb on Wikidata via a special search with L: at the start of it like the following:

• https://www.wikidata.org/w/index.php?go=Go&search=L%3A+%D7%9B%D7%AA%D7%91&search=L%3A+%D7%9B%D7%AA%D7%91&title=Special:Search&ns0=1&ns120=1

From there, could you let me know what you'd say would be the ideal verb tenses to get from a verb like the following (as I understand it it's something like "to write", which should have good conjugation coverage):

• https://www.wikidata.org/wiki/Lexeme:L212243

And then we can reference the queries for other languages to get all their verbs and edit the Hebrew verbs query so that it returns all the conjugations we need 😊

Once we have that set, we'll then have a better understanding of what data we're trying to model, and then we can update the PR here so that all the conjugations will have appropriate setups.

[andrewtavis]

So here we'll need to update this list based on what conjugations we'll get from Wikidata :)

[andrewtavis]

This should specifically only have one tense for each case statement :)

[andrewtavis]

Do you want to continue on this issue now, @DanielGevaZA?

[andrewtavis]

Went through and added in the conjugation flow to this PR here, @DanielGevaZA :) We can pick this up further once the data is added into the project. We're also working on RTL support for the menu, with this laying the groundwork for the same for the keyboards.

Thanks for this!