Problem to be solved
Description
With the shift to Sentence Case (e.g., Add realtime effects), identifying the context of UI strings (menu command, tooltip, error) has become challenging for translators, especially for languages like Japanese.
The Problem
- Menu Command: Requires a concise noun phrase (e.g.,
リアルタイムエフェクトを追加).
- Tooltip / Description: Requires a full, polite sentence (e.g.,
リアルタイムエフェクトを追加します).
Without context comments in the source files, translators on Transifex have to guess the usage, which reduces translation quality.
Your idea
Proposed Solution
I propose adding developer notes (// i18n-hint: ...) to the source code for ambiguous strings.
For example:
// i18n-hint: This is a menu command under the Effects menu.
_("Add realtime effects")This will ensure high-quality, professional localization.
Thank you.
Prior art
No response
Additional context
No response
Problem to be solved
Description
With the shift to Sentence Case (e.g.,
Add realtime effects), identifying the context of UI strings (menu command, tooltip, error) has become challenging for translators, especially for languages like Japanese.The Problem
リアルタイムエフェクトを追加).リアルタイムエフェクトを追加します).Without context comments in the source files, translators on Transifex have to guess the usage, which reduces translation quality.
Your idea
Proposed Solution
I propose adding developer notes (
// i18n-hint: ...) to the source code for ambiguous strings.For example:
This will ensure high-quality, professional localization.
Thank you.
Prior art
No response
Additional context
No response