Use this workflow to localize release notes from one base-language draft into your project's non-base languages.
What This Covers
This guide is for release-note localization where you:
- Write one source note.
- Generate localized versions for project languages.
- Review and copy final text into your release channel.
How the Flow Works
- Open your project's Release Notes area.
- Enter the source note text.
- Submit to queue localization jobs for non-base languages.
- Wait for localized rows to move out of processing.
- Copy each locale's output and publish.
Input Validation Rules
Release-note input is validated before localization:
- Maximum length:
3000characters - Emojis are rejected
- HTML tags are rejected
Keep copy plain-text and concise for reliable store-channel formatting.
Tone, Prompt, and Term Protection
Release-note generation follows project-level localization settings:
- Tone preferences
- Custom prompt guidance
- Protected Terms (Glossary) locking behavior
If your brand or product terms must remain unchanged, configure Protected Terms before running localization.
Quotas and Limits
Monthly release-note creation limits are plan-dependent.
If limit is reached, create is blocked until the next cycle or a plan upgrade.
Troubleshooting
If localized output is missing:
- Confirm the project has active non-base languages.
- Check input text against validation rules (length, no emojis, no HTML).
- Re-submit after correcting input.
If terminology is inconsistent:
- Add/update Protected Terms.
- Re-run release-note localization.