Adding new translations¶
New strings can be made available for translation when they appear in the base file, called Template for new translations (see Component configuration). 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 configuration.
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 Updating repositories).
Shapings 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 configuration:
The expression is matched against Context to generate root key of the shaping. All matching strings are then part of single shapings group, including the translation exactly matching the root key, even if that is not matched by the regular expression.
The following table lists some usage examples:
|Use case||Regular expression shaping||Matched translation keys|
The shaping is later grouped when translating: