Jump to content

Localisation Platform Research Summary 2022/Weblate

From translatewiki.net


Local deployment was quite simple via docker: Installing using Docker — Weblate 4.10 documentation


  1. Self hosted - Free
  2. Pricing - Weblate Pricing

Pricing is based on the number of source strings and target languages. A source string is a text unit defined in a translation format. It can be a word, sentence or paragraph.

Adding project to Weblate

  1. First add a project.
    • Translation instructions can be added when adding a project
  2. Then add components to that project. Components can be added from:
    • From version control
    • From existing component
    • Additional branch - Translation component for an additional branch of the existing translation component.
    • Upload translations files
    • Translate document
    • Start from scratch

All this can be done via the user interface.

  1. The entire project configuration can be done via the user interface
    • Possible to specify license for translations
    • Source languages other than English are supported
    • A component under a project can be marked as a glossary. A project can have multiple glossaries.
    • Supports continuous localisation via repository hooks - GitHub, GitLab, BitBucket etc
    • Adding a component automatically adds a glossary

Project Management


Repository maintenance

  • Displays information about the remote repo and branches being tracked
  • Manually trigger pushes and commits
  • Lock translators from doing changes
  • Reset local changes so that the repository matches upstream


Upload screenshots and use them in strings


Can set an announcement with type (info, alert, warning etc) and expiry time. It’s displayed to users when they open the component.

Translation memory

A component can choose to contribute to the “shared translation memory”. Custom strings (via JSON or TMX) can also be imported to the translation memory.


Add users to the project and give them administrative (management) access. In case the component is “restricted”, then only added users can see and translate the project.

Add Ons

Additional components that can be enabled for a project or a component. Eg:

  1. Statistics generator: Generates a file containing detailed info about the translation status.
  2. Stale comment removal: Set a timeframe for removal of comments.
  3. Bulk edit: Bulk edit flags, labels, or states of strings.


General information regarding the project. Also provides various statistics such as:

  1. Activity in last 12 months - Translations for the last 12 months
  2. Quick numbers - Hosted strings, words, translated and contributors
  3. Trends of last 30 days - Same as quick numbers but for last 30 days
  4. String statistics


  • Search and replace - Self explanatory
  • Bulk edit - Change the state of all strings matching a given type at once.
  • Data exports - Links to statistics and  RSS feeds for translation  updates
  • Failing checks - List of checks that are failing for the component
  • Matrix view - To compare different languages efficiently you can use the matrix view. First select all languages you want to compare and confirm your selection, after that you can click on any translation to open and edit it quickly.


  • History: List of changes made to the component / project including translation changes, new language addition. Certain changes can be reverted from this screen and users blocked from providing further translation..
  • Statistics (HTML / JSON): Languages statistics  or the component in JSON / HTML
  • Translation Reports
    • Credit / Project translators: Lists all translators contributing to this component in a given time period
    • Contributor stats: Reports the number of strings and words translated by each translator.


Important alerts for the project / component that need to be dealt with immediately. See list of alerts: https://docs.weblate.org/en/latest/devel/alerts.html#translation-component-alerts


  • Duplicated source strings in translation files
  • Parse errors in the translation files
  • Merge, update, or push failures in the repository
  • Etc …


  • Can set priority for components in the project. Components with higher priority are offered first to translators.
  • Mark the component as restricted(Restrict access to the component to only those explicitly given permission)
  • Specify translation license and contributor agreement.
  • Specify validations / checks that should be enforced.
  • Version control related settings - how often to commit, branch to commit to etc.
  • Customization of the commit messages

Supported File Formats

Weblate can automatically detect several widespread file formats, but this detection can harm your performance and will limit features specific to given file format (for example automatic addition of new translations).

List of supported file formats - https://docs.weblate.org/en/latest/formats.html#translation-types-capabilities

  • A =translation speed.  
  • Mark a string as “needs editing”: Similar to marking translations as fuzzy  

Translation Aids

All translation aids are available on the same page.

  • Nearby strings - Messages placed around this one.
  • Similar keys - Other strings with similar keys
  • Comments- User added comments.
  • Automatic suggestions - Based on translation memory. This section is searchable.
  • Other languages - Translation for this string into other languages
  • History - History of translations made for this string.


  • Make suggestions: Users can provide translations as suggestions.
  • Suggestion Voting: Users can only vote for suggestions and can’t make direct translations.
  • Auto Accept suggestions: Automatically accept suggestions with this number of votes, use 0 to turn it off.


Weblate employs a wide range of quality checks on strings. The following section describes them all in further detail. There are also language specific checks.

List of checks:


Translation Search

Supports an advanced query builder with flags and curren state such as:

  • Review strings changed by other users - changed:>=2021-12-21 AND NOT changed_by:admin
  • Translated strings - state:>=translated
  • Approved strings with suggestions - state:approved AND has:suggestion


Each component can have it’s own API access:


Key Highlights

  1. Project Glossary to help translators understand difficult terms.
  2. Self hosted, easy to set up, open source alternative to other localisation platform.
  3. Easy for developers to add projects to the platform. No interaction with the Weblate team is needed.
    1. Large set of predefined validations / checkers to choose from.
    2. Large file format system support
  4. Single page listing problems with all translations. Allows translators to quickly see issues and fix them.
  5. Translation on mobile is not perfect but feasible.
  6. Translating to different plurals is easy. No possibility of making mistakes since different textboxes are provided for different plural rules. Partial plural translations are not possible though.
  7. Large file format support: Qt, Go, HTML files etc
  8. Supports Add-Ons
  9. Possible to configure how often synchronization with remote repository happens.
  10. Discussions / Comments related to a message appear on the translation interface.
  11. Comprehensive translation search
  12. Concept of suggesting translations is interesting. After a suggestion has been approved a certain number of times, it’s used as a translator.
  13. Easily search and substitute (find and replace) strings in the component

Experience Review

As a translator

What is good

  1. All translations failing checks can be viewed from a single page.
  2. A small toolbox that can be used to insert some special characters such as tabs, no break space etc.
  3. Can suggest translations without actually making a change.
  4. Can mark a translation as fuzzy.
  5. Easy to select the type of strings they want to translate. Eg:
    1. Strings needing action
    2. Strings marked for edit
    3. Strings with labels
    4. Strings with comments etc..
  6. A lot more information is available to review before making translations, albeit they require some clicks to browse through.
  7. Bulk edit can be used to update the state (Do not change, needs editing, translated etc) of strings in a group / project.
  8. Easy search and replace tool available for translators
  9. Messages have associated comments sections for translators to discuss.
  10. Easy to add a screenshot to a string for documentation purposes.
  11. A single insights page displays the history of the project / component.
  12. A glossary feature is available.
  13. Can watch projects and receive notifications for various events.


  1. Not easy to switch between languages when translating
  2. The default translation editor reloads the page on every save, taking longer than usual to load more strings

As a project maintainer / developer

What is good

  1. Setting up a self hosted instance for translation of your software projects is easy.
  2. Adding and configuration of a new project is fairly simple and does not require any staff to be involved.
    1. All configuration for pushing, commiting changes can be done via the interface.
  3. Projects can configure shared translation memory. Also it can be exported out in JSON or TMX.
  4. Project maintainers can post announcements with an expiry date.
  5. It’s possible to mark a component as private and allow only certain users to translate it.
  6. Administrators can use labels to organize and group messages in a component.
  7. Minor: Supports notification hooks to allow external applications to notify Weblate that the VCS repository has been updated.
  8. Can “Enable Reviews” for a project so that dedicated reviewers have to review translations. See link.
  9. Ability to start a translation project from VCS, existing components, translation files and documents
  10. Contains a large number of checks that the maintainer can mark as enforced.
  11. Possibility to add translation flags in order to customize Weblate behavior.
  12. Can enable “suggestion voting”, where contributors can vote for suggestions after which they are marked as translated.
  13. Set priority for components.
  14. Support for Glossary via a separate component in the project.
  15. Can reset all recent translations / changes made in Weblate so the repository matches upstream.
  16. Supports continuous localisation so that translation closely follow development .


  1. Did not see an option to configure custom validators.