Reference all strings from scribe i18n

[angrezichatterbox]

Contributor checklist

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

---

Description

• The pull request adds the leftover strings from i18n to the app.
• It also corrects some layout issues in some pages which I could notice.

Related issue

• Convert all strings to Scribe-i18n keys #95

[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 Android 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-Android 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]

Awesome work, @angrezichatterbox! We'll be able to bring in the other strings for other languages and any other corrections that may be on the way! So great that localization is supported so early in the process 😊

[angrezichatterbox]

Awesome work, @angrezichatterbox! We'll be able to bring in the other strings for other languages and any other corrections that may be on the way! So great that localization is supported so early in the process 😊

Could we start working on the keyboard issues? I would love to get to know the keyboard codebase much more.

I also have some more detekt issues which I will be making today. It's the festive season here so I got a little busy.

[andrewtavis]

Sounds good, @angrezichatterbox! I can make some more issues for the keyboard soon :)

[andrewtavis]

Tons of new issues just made, @angrezichatterbox! Many of the new ones are for the keyboard as well :) Let me know what sounds appealing, and I've also already pinged you in the ones I think would be good to look into first 😊