Weblate 블로그 / 이정표
Major version, major glossary change: 4.5
Weblate 4.5 brings the new approach to the glossary, adding features and some fixes.
New Weblate: it is major, it’s 4.0
The new major version of Weblate brings significant performance improvements thanks to entirely new translation memory backend and search feature, together with new features in API, checks, source strings improvements.
New Weblate: 3.10
New Weblate version 3.10 is out, with brand new app UI, improved performance of backend and frontend, better search feature, and more.
Weblate is changing its look
Weblate has grown a lot since the first lines of code in 2012, and we finally found some time to not only make new features but also create a new website. One that will serve better to the users and visitors, look modern, and represent well. I am not going to describe here all the pretty things of the site, this is a story about the creative process and things that happened around.
Weblate 3.4
Weblate 3.4 has been released today. The most visible new feature are guided translation component setup or performance improvements, but there are several other improvements as well.
Weblate 3.0
Weblate 3.0 has been released today. It contains brand new access control module and 61 fixed isssues.
Weblate 2.20
Weblate 2.20 has been released today. There are several performance improvements, new features and bug fixes.
Weblate 2.19
Weblate 2.19 has been released today. The biggest improvement are probably addons to customize translation workflow, but there are some other enhancements as well.
Weblate 2.17
Weblate 2.17 has been released today. There are quite some performance improvements, improved search, improved access control settings and various other improvements.
Making Weblate more secure and robust
Having publicly running web application always brings challenges in terms of security and in generally in handling untrusted data. Security wise Weblate has been always quite good (mostly thanks to using Django which comes with built in protection against many vulnerabilities), but there were always things to improve in input validation or possible information leaks.