Weblate Blog / Funktioner
Translate more with Weblate. Localize your static pages easily with Weblate CDN.
Weblate is now able to handle the files without a connection to the external repository.
We have a new feature in Weblate we already mentioned in 3.7 release announcement.
Upcoming Weblate 3.3 will bring new feature called alerts. This is one place location where you will see problems in your translations. Right now it mostly covers Weblate integration issues, but it will be extended in the future for deeper translation wide diagnostics.
Next release on Weblate roadmap is called 3.0 and will bring some important changes. Some of these are already present in the Git repository and deployed on Hosted Weblate, but more of that will follow.
Upcoming Weblate 2.17 will bring improved access control settings. Previously this could be controlled only by server admins, but now the project visibility and access presets can be configured.
Weblate should be released by end of February, so it's now pretty much clear what will be there. So let's look at some of the upcoming features.
Today, new version has been deployed on Hosted Weblate. It brings many long requested features and enhancements.
The long requested feature for Weblate is here - it now has API which you can use to control it. It's scope is currently limited, but it will expand in future releases. The API is currently available in Git, deployed on both Demo server and Hosted Weblate, our hosted solution. It will be also part of 2.6 release, which should not be that far away.
Weblate has started as a translation system tightly bound to Git version control system. This was in no means design decision, but rather it was the version control I've used. But this has shown not to be sufficient and other systems were requested as well. And Mercurial is first of them to be supported.