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
The translatable content is extracted from the OpenDocument files and offered for the translation. Weblate configuration:,, Typical Weblate Component configuration,,, File mask, path/*.odt,, Monoli...| Weblate
JSON format is used mostly for translating applications implemented in JavaScript. Weblate currently supports several variants of JSON translations: Simple key / value files, used for example by vu...| 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
Android specific file format for translating applications. Android string resources are monolingual, the Monolingual base language file is stored in a different location from the other files – res/...| Weblate
Weblate supports a wide range of translation formats. Each format is slightly different and provides a different set of capabilities. Automatic detection: Weblate tries to detect file format during...| 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
Welcome to the official documentation of Weblate, the libre software web-based continuous localization system. The table of contents in the sidebar should let you easily access the documentation fo...| 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
Translation organization: Weblate organizes translatable VCS content of project/components into a tree-like structure. You can additionally organize components within a project using categories. Th...| Weblate
Custom automatic fixups: You can also implement your own automatic fixup in addition to the standard ones and include them in AUTOFIX_LIST. The automatic fixes are powerful, but can also cause dama...| 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
All settings are stored in settings.py(as is usual for Django). ADMINS_CONTACT: Configures where contact form sends e-mails. If not configured, e-mail addresses from ADMINS are used. Configure this...| 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
Thank you for your interest in translating with Weblate! Generally, there are two most used modes of translation: Project accepts direct translations, Project accepts the suggestions made by users....| Weblate