Hello Patrik,
Thank you so much for this valuable feedback! You're absolutely right, and I completely understand the issue.
Using the same translation key in multiple contexts can indeed create grammatical problems in languages with declensions, cases, and gender agreements. What works in French doesn't always work in English, and it can make the translation sound unnatural or even incorrect.
I'll implement your suggestion by:
-
Creating context-specific translation keys - Each instance will have its own key, even if the English text is the same. For example:
auth.registration.form_title (for the form title)
auth.registration.button_text (for the button)
auth.registration.menu_item (for navigation)
auth.registration.success_message (for confirmation text)
-
Adding contextual comments in the JSON files to help translators understand where and how each term is used (noun vs. verb, subject vs. object, etc.)
-
Grouping related terms so translators can see the full context and maintain consistency where it makes sense
This will give you full flexibility to adapt each translation to its specific grammatical context - proper cases, singular/plural forms, gender agreements, and natural phrasing.
I really appreciate you taking the time to explain this. Native speaker feedback is invaluable for creating a truly localized experience rather than just a literal translation.
I'll work on this restructuring and will let you know once it's ready for review.
Have a wonderful day!
Edited on
Dec 25, 2025
By
Fred .