Added translation source language option to language setting screen

[ThousandYearGrind]

Contributor checklist

• This pull request is on a separate branch and not the main branch
• I have tested my code with the ./gradlew lintKotlin detekt test command as directed in the testing section of the contributing guide

---

Description

Added translation source language option to language settings screen
The actual selection does not work (just a clickable ui item)

I ran my code in Android Studio and saw the option in Settings > Select Installed Keyboard > English
I also ran the ./gradlew lintKotlin detekt test to check my code

Related issue

• Add the menu option to set Translation source #149

[github-actions]

Thank you for the pull request! ❤️

The Scribe-Android team will do our best to address your contribution as soon as we can. 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 Android rooms once you're in. Also consider attending our bi-weekly Saturday dev syncs. It'd be great to meet you 😊

[github-actions]

Maintainer Checklist

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 :)

• 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)

[github-actions]

First PR Commit Check

• 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-Android repo (can be set with git config --global user.email "GITHUB_EMAIL")

[angrezichatterbox]

Hey @ThousandYearGrind.

The issue actually wants you to show the different languages on clicking the select language menu option and then select the specific language and store it in shared preferences that could be accessed later on for different languages differently.

Would you like to do that in the same PR

[ThousandYearGrind]

Hi @angrezichatterbox
I tried to do that initially but did not know how to open up a separate menu for language selection. Maybe I can come back to it after I learn more, but for now it would probably be better to open it up so other people who do know how to do it could work on it.

[angrezichatterbox]

Should I make changes within the same PR for adding the individual languages or a menu or should a separate issue be made for it @andrewtavis

[andrewtavis]

I think we'd be good to make changes within this PR and resolve the issue, @angrezichatterbox :) Thanks for checking!

[angrezichatterbox]

Should The translation selection be a separate page or should an overlay with the options be present or just a drop down for the languages.

[andrewtavis]

I think the plan was a separate page so it's a bit consistent with going to sub menu pages, but then I haven't actually thought of other options 🤔 I think a popover would be better than a dropdown. See the designs here. If we want to switch to a popover, then we should think of a different interaction icon for these options than >, as that indicates that we're going to a sub-page.

Any thoughts on this, @angrezichatterbox? :)

[angrezichatterbox]

I think the plan was a separate page so it's a bit consistent with going to sub menu pages, but then I haven't actually thought of other options 🤔 I think a popover would be better than a dropdown. See the designs here. If we want to switch to a popover, then we should think of a different interaction icon for these options than >, as that indicates that we're going to a sub-page.

Any thoughts on this, @angrezichatterbox? :)

I think subpages would be good if we would have a lot of language at any point and the consistency would be maintained across the app.

[andrewtavis]

Good point that scrolling a popover would be really annoying 😊 Let's stick with sub pages as is in the designs then!

[angrezichatterbox]

It is ready for review :)

[andrewtavis]

Nice @angrezichatterbox! I'll get to this later today :)

[andrewtavis]

All's functioning really well, @angrezichatterbox! And thanks for the great start here, @ThousandYearGrind 😊 Glad to have the menu for keyboards so well set up 🥳