Each project can include one or more glossaries as a shorthand for storing terminology. Glossaries help to maintain consistency of the translation. A glossary for each language can be managed on it...| Weblate
Most widely used format for translating libre software. Contextual info stored in the file is supported by adjusting its headers or linking to corresponding source files. Showing source string chan...| Weblate
To present different translations properly, info about language name, text direction, plural definitions and language code is needed. Built-in language definitions: Definitions for about 650 langua...| Weblate
There is infrastructure in place so that your translation closely follows development. This way translators can work on translations the entire time, instead of working through huge amount of new t...| Weblate
Adding new strings: 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...| Weblate
Add-ons provide ways to customize and automate the translation workflow. Admins can add and manage add-ons from the Operations ↓ Add-ons menu of each respective translation project or component. Ad...| Weblate
The quality checks help catch common translator errors, ensuring the translation is in good shape. The checks can be ignored in case of false positives. Once submitting a translation with a failing...| Weblate
Suggestion voting: Everyone can add suggestions by default, to be accepted by signed in users. Suggestion voting can be used to make use of a string when more than one signed-in user agrees, by set...| Weblate
You can export files from a translation, make changes, and import them again. This allows working offline, and then merging changes back into the existing translation. This works even if it has bee...| Weblate