New strings can be made available for translation when they appear in the base file, called Template for new translations (see component). If your file format doesn't require such a file, as is the case with most monolingual translation flows, you can start with blank files).
New languages can be added right away when requested by a user in Weblate, or a notification will be sent to project admins for approval and manual addition. This can be done using Start new translation in component.
Note
Project admins can always start translation within Weblate directly.
Language files added manually to the VCS are added to the component when Weblate updates the repository. About repository update settings, see update-vcs.
Variants are useful to group several strings together so that translators can see all variants of the string at one place. You can define regular expression to group the strings in the component:
In case the Key matches the expression, the matching part is removed to generate root key of the variant. All strings with same root key are then part of single variants group, including the translation exactly matching the root key and not matching the expression.
The following table lists some usage examples:
| Use case | Regular expression variant | Matched translation keys |
|---|---|---|
| Suffix identification | (Short|Min)$ |
monthShort, monthMin, month |
| Inline identification | #[SML] |
dial#S.key, dial#M.key, dial.key |
The variant is later grouped when translating:
Split component translation strings into categories by text and colour in the project configuration.
Hint
Labels can be assigned to units in additional by bulk editing, or using the addon-weblate.flags.bulk addon.