Backported fix for XSS reported by Psicomante. Strings output for JavaScript display were not escaped properly. Due to how the Drupal.org policy limits security announcements to 'stable' software (that is not alpha packages like l10n_server), this fix is not accompanied by an SA.

Support for 7.x modules. Should be used with an up-to-date potx development version (as of a few minutes ago), since that supports a 7.x parsing mode. Further 7.x support issues are the domain of potx.

#281282 by meba: add a convinience feature to toggle the information pane via the magnifier glass icon; add tooltips and fix missing icons in explore views with text headers

#252175 by yhahn: community translation UI improvements. A little bit still rough around the edges, but it should really be brough to everyones attention.

#231927 by claudiu.cristea: if only one language is set up, then don't bother with displaying one radio button

#234878 ingnited change in l10n_server: use about:blank instead of about: for client browser redirection to make all browsers happy and not block our request as something malicious

#231409 by brmassa any myself: use drupal_http_request() instead of copy() to retrieve project tarballs, the later which is probably limited to local file operations anyway

follow up to #231435 by myself: inform users about error conditions, if the translation submission failed on the server (client already ready to handle this, no need to modify that)

#231435 by myself: make it possible to get string suggestions by remote invocation (from l10n_client); this is the sister task of #231439

#203510 patch by meba and myself: 0 byte files were generated when there were no strings; inform the user instead

#218260 reported by hass, patch by myself: serve PO files as text/plain, not application/x-compressed

#225436 by rak: approving a suggestion on the AJAX interface made all other suggestions in other languages disappear (critical)

a quick and temporary hack for #212594 so that translators can export their translations in the format which works with Drupal 6

#208771 request by pvasili, implementation by myself: more granular setup for number of projects scanned, >20 is irrealistic, so getting rid of that

#209517 report by Sutharsan, solution by myself: installer strings were not properly identified and exported;
 - store string type (runtime, installer, both) in a type field on file-line-string associations
 - included update path for existing sites
   (but they still need to rescan everything unfortunately)
 - on export, unless the all-in-one format is used, output installer only strings to installer.po and output installer and runtime strings to installer.po as well
 - obey flat mode and some special handling for core file placement as well