Capitalize German nouns in autocompletions even if the keyboard is lower case

[Femimat]

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 German, all nouns are capitalized regardless of their position in a sentence. Since the autocompletion system (especially the fallback mechanism added in #556) pulls words from the nouns table, we can identify which suggestions are nouns and ensure they are presented with an uppercase first letter.

I have implemented the following logic in AutocompletionDataManager.kt file:

1. Noun Tracking: It now populates a germanNouns set whenever German (DE) data is loaded.

2. Smart Capitalization: In getAutocompletions, it checks if the language is German and if the word exists in the germanNouns set. If either condition is met (user started with a capital letter OR it's a known German noun), the suggestion is capitalised.

• Capitalize German nouns in autocompletions even if the keyboard is lower case #594

[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. The following are some important points:

• Those interested in developing their skills and expanding their role in the community should read the mentorship and growth section of the contribution guide
• If you're not already a member of our public Matrix community, please consider joining!
  • We'd suggest that you use the Element client as well as Element X for a mobile app
  • Join the General and Android rooms once you're in
• Also consider attending our bi-weekly Saturday developer syncs!
  • Details are shared in the General room on Matrix each Wednesday before the sync
  • It would be great to meet you 😊

Note

Scribe uses Conventional Comments in reviews to make sure that communication is as clear as possible.

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

• Tests for changes have been written and the unit test, linting and formatting workflows within the PR checks do not indicate new errors in the files changed

  • Tests may need to be reran as they're at times not deterministic

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

[Femimat]

Hi @andrewtavis, @DeleMike
I have open a PR for issue #594 would love to have your feedback on this when you have the time, thank you