Adding Context for Translations on Crowdin

[virgile-dev]

Enhancement Request

Is your feature request related to a problem or unsupported use case? Please describe.
Currently, translation keys on Crowdin lack context, which leads to translation errors. For example, the word "Open" in the dropdown menu for filtering comments was translated as "Ouvrir" in French, when the correct context should have resulted in "Ouverts" (to indicate a state, such as "open comments"). Without clear context, translators struggle to choose the correct interpretation.

Describe the solution you'd like

1. Add a context field for each translation key on Crowdin. This field could include:

   • A brief description of where the key is used (e.g., "Dropdown menu for filtering comments in the side panel").
   • Usage examples or screenshots if possible.

2. Create specific keys for ambiguous cases. For example:

   • comments.filter.open for the filter "Ouverts" ("Open" as a state).
   • comments.action.open for the action "Ouvrir" ("Open" as a verb).

Expected Benefits:

• Fewer translation errors.
• Improved terminological consistency.
• Time savings for translators and reviewers.

Considered Drawbacks:

• Initial effort required to document existing keys.
• Slight increase in complexity for developers adding new keys.