Added interface variables strings constant to be used in the keyboard

[Saifuddin53]

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

In this PR, I’ve added all required interface variable strings to the keyboard constants for each language. Based on the new approach, these strings are now hard-coded into each keyboard file rather than being localized via Weblate.

Related issue

• Add in all needed interface variable strings to the keyboard constants #214

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

[Saifuddin53]

@andrewtavis @angrezichatterbox I've implemented all the interface variables for Spanish (for now). Could you please review this and let me know if this is the implementation you had in mind? Please let me know if any modifications are needed or if you have any suggestions 🙂

[angrezichatterbox]

Looks good to me. The organization is perfect for constants.

[Saifuddin53]

@angrezichatterbox @andrewtavis ready for review

[andrewtavis]

Could we discuss really quick the linting errors that are suggesting that we do screaming snake case for variables that won't change? That makes sense to me :) I guess that Swift doesn't have that convention, but if that's what ktlint suggests then I'd say we'd be good to follow it 😊

[Saifuddin53]

@andrewtavis I’ve updated the variable names to follow the screaming snake case convention. Thank you for your feedback ☺️

[andrewtavis]

Thanks for the work here, @Saifuddin53! I switched over these files to have succinct marks as sections that will show up in some code editors :) That's a more clean way of doing sections, as comments that are their own lines would ideally be fully punctuated sentences.

Looking forward to the next time we work with you!

[andrewtavis]

What I get for using VS Code to do something quick 😅 I'll fix the linting errors and then bring this in :)

[Saifuddin53]

Thanks for the review and help @andrewtavis 🫡🫡
Can I work on the migration of the About page to compose if the assignee is not currently working on it
Also are we going to migrate the keyboard layout to compose as well?

[angrezichatterbox]

If we are migrating the keyboard to compose we would have to rework the entire MyKeyboardView.kt and The IME. I am not sure if it is something necessary to be done as most keyboards are still using XML layouts as it wouldn't be easy to work with the IME using Compose.