Welcome to the new Pootle 2.7.3-rc1¶

Released on 24 November 2015

Bugfix release for 2.7.2.

Major Changes¶

MySQL’s MyISAM support has been dropped. Use InnoDB instead.
The editor for static pages now highlights the content’s markup and displays a live preview.
Added support for Elasticsearch-based external Translation Memory servers.
Changed connection logic and added checks for misconfigured Translation Memory servers.

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

Details of changes¶

Pulled latest translations.
Static pages and announcements:
- The editor for static pages now highlights the content’s markup and displays a live preview of the rendered contents (issue 3346, issue 3766).
- Project and language announcements are now also displayed on their respective overview pages.
Translation memory:
- 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 or directories on disk. This effectively brings the ability to display TM results from different TM servers, sorting them by their score.
  - Translations saved from Pootle now include a timestamp.
  - Fixed missing index error issue 4120.
- 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.
  - Added several checks to ensure this setting is not misconfigured.
- Changed connection logic for Translation Memory servers to handle connection issues and misconfigurations on the settings.
Database:
- 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 issue 4094.
Editor:
- Non-critical checks can once again be muted/unmuted.
- Fixed units sorting issue for admin users issue 4116.
Import/export and upload/download:
- Fixed running export command without options.
- Added a new --user to import to attribute changes to specified user on file import.
- Ignore non project filetypes when uploading zip files issue 4124.
- Only authenticated users with translate rights can upload translations.
- Any authenticated user can now download translations.
The Apertium MT backend has been dropped.
Report string errors form subject and body can be overriden.
Language managers can now edit their language’s special characters by using the Special Characters page accessible through the browse dropdown in the language overview page.
Quality checks for newly created Translation projects are not calculated in order to speed up its initialization.
Added extra data to reports.

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

Credits¶

This release was made possible by the following people:

Julen Ruiz Aizpuru, Leandro Regueiro, Dwayne Bailey, Ryan Northey, Taras Semenenko.

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