start => pootle

# Important Changes

These are the critical changes that have happened in Pootle, these may affect you. Also be aware of the important changes in the translate toolkit as many of these also affect Pootle.

## trunk

This section describes the changes in the (unreleased) development files. It should reflect upcoming changes in the next version of Pootle.

## 1.0

### XLIFF support

Pootle 1.0 is the first version with support for XLIFF based projects. In the admin interface the project type can be specified as PO / XLIFF (this really just tells Pootle for which type of files it should look - it won’t convert your project for you). This property is stored in pootle.prefs in the variable “localfiletype” for each project.

### Configurable logos

You are now able to configure the logos to use in pootle.prefs. At the moment it will probably be easiest to ensure that the same image sizes are used as the standard images.

### Localised language names

Users can now feel more at home with language names being localised. This functionality is actually provided by the toolkit and your system’s iso-codes package.

### Treestyle: gnu vs nongnu

Pootle automatically detects the file layout of each project. If you want to eliminate the detection process (which can be a bit slow for big projects) or want to override the type that Pootle detected, you can specify the “treestyle” attribute for the project in pootle.prefs. Currently this can not be specified through the admin interface.

## 0.11

If the user has the appropriate privileges (ovewrite right) he/she will be able to upload a file and completely overwrite the previous one. Obviously this should be done with care, but was a requested feature for people that want to entirely replace existing files on a Pootle server.

The server administrator can now specify the default access rights (permissions) for the server. This is the rights that will be used for all projects where no other setup has been given. See pootle.prefs for some examples.

The default rights in the default Pootle setup has changed to only allow suggesting and to not allow translation. This means that the default server setup is not configured to allow translation, and that users must be specifically assigned the translate (and optionally review) right, or alternatively, the default rights must be configured to allow translation (see the paragraph above).

The baseurl will now be used, except for the /doc/ directory, that currently still is offered at /doc/.

The default installation now uses English language names in preperation for future versions that will hopefully have language names translated into the user interface language. To this end the language names must be in English, and names with country codes must have the country code in simple noun form in brackets. For example:

    Portuguese (Brazil)

in other words, not “Portuguese (Brazilian)”

## 0.10

### Statistics

The statistics pages are greatly reworked. We now have a page that shows a nice table, that you can sort, with graphs of the completeness of the files. This is the default view. What is confusing is that the stats page does not work directly with editing. To get the editing features, click on the editing link in the top bar.

The quick statistics files (pootle-projectname-zu.stats) now also store the fuzzy stats that are needed to render the statistics tables. Your previous files from 0.9 can not supply this information. Pootle 0.10 will automatically update these files, but if you (for some reason) want/need to go back to Pootle 0.9, you will have to delete these files. Not all .stats files need to be deleted, only the ones starting with pootle-projectname.

### SVN and CVS committing

You can now commit to SVN or CVS. A default commit message is added, you cannot edit this message. Your ability to commit depends on the rights you have on the checkout and since you cannot supply a password it needs to be a non-blocking method. This feature is probably not useful for a very public server unless it is managing multiple translations of your own project and you have direct control over it and CVS/SVN accounts. It will work well in a standalone situation like a Translate@thon etc, where it is a public event but the server is controled by yourself for the event and then you can simply commit changes at the end. For more information, see version control.

### Terminology

Pootle can now aid translators with terminology. Terminology can be specified to be global per language, and can be overriden per project for each language. A project called “terminology” (with any full name) can contain any files that will be used for terminology matching. Alternatively a file with the name “pootle-terminology.po” can be put in the directory of the project, in which case the global one (in the terminology project) will not be used. Matching is done in real time. Note that this does not work with GNU-style projects (where all the files are in one directory and have names according to the language code).

### Translation Memory

Pootle can now aid translators by means of a translation memory. The suggestions are not generated realtime - it is done on the server by means of a commandline program (updatetm). Files with an appended ‘.tm’ will be generated and read by Pootle to supply the suggestions. For more information see updatetm.

## 0.9