UI text improvements for +translations-upload

[Matthew Revell]

Present inline:

 * Must have .pot file
 * Key elements of the translations import policy:
  * English .pot
  * Layout should be one directory per template -- give an example in a pop-up (see below)
 * Explain can upload single file but BEST TO upload tarball
  * Probably don't mention .po files -- encourage tarball upload, gives paths and layout -- solves approval problems

Example layout (applies to tarball and auto imports):

template1/template1.pot
template1/de.po
...
template2/template2.pot
template2/de.po
template2/fr.po

etc.

[Matthew Revell (matthew.revell)]

Also on automatic imports page -- +translations-settings

Explain that layout similar to that used by .mo files is unacceptable. Example:

template1/LC_MESSAGES/de/template1.po <-- we don't support this.

[Matthew Revell (matthew.revell)]

Thank you message when you've uploaded file: we will be reviewing it but we don't know when. "Thank you for your upload"

Automatic approval happens in two phases:
 Step 1: approves only templates
 Step 2: approves translation files -- if there are no template files that have been approved in step 1, it won't approve anything.

There's a delay between those two steps.

Existing templates when re-uploaded will not be approved if they're using a different path. For example, someone starts with a tarball and then uploads a single .pot file, or vice versa. Basically, just use automatic imports.

[Jeroen T. Vermeulen (jtv)]

All this still mentions tarballs a lot... bzr imports are now the preferred route!