Welcome to the new Pootle 2.7.3 final¶

Not yet released

Bugfix release for 2.7.2.

Changes in Requirements¶

Below we provide much more detail. These are by no means exhaustive, view the git log for complete information.

The editor for static pages now highlights the content’s markup and displays a live preview of the rendered contents (issue 3346, issue 3766).
Pulled latest translations.
update_tmserver:
- Renamed --overwrite to --refresh.
- Translations from disabled projects must be explicitly included with --include-disabled-projects.
- Added support for Elasticsearch-based external Translation Memory servers, which can be populated from translation files. This effectively brings the ability to display TM results from different TM servers, sorting them by their score.
POOTLE_TM_SERVER:
- The default TM server has been renamed to local. Make sure to adjust your settings.
- Added a new WEIGHT option to raise or lower the TM results score for each specific TM server.
import:
- Added a new --user to allow setting of user to attribute changes to on file import.
The Apertium MT backend has been dropped.
Report string errors form subject and body can be overriden.
InnoDB is the only accepted MySQL backend. Deployments using MyISAM must migrate to either MySQL (InnoDB) or PostgreSQL.
Close a database connection before and after each rqworker job once it exceeds the maximum age to imitate Django’s request/response cycle.
Language managers can now edit their language’s special characters.

...and lots of refactoring, new tests, cleanups, improved documentation and of course, loads of bugs were fixed.

This release was made possible by the following people:

%CONTRIBUTORS%

And to all our bug finders, testers and translators, a Very BIG Thank You.