[OPEN-ILS-DEV] Translations for Evergreen 1.6

[Dan Scott]

Hello to all interested in contributing new or updated translations to
Evergreen. With the recent release of 1.6.0.0, it's time to call for
translations.

In the past we asked translators to work directly with GNU gettext PO
files. This is okay, as long as the translator is comfortable working
with tools like POEdit, but it can be hard to coordinate a distributed
effort with PO files.

I'm trying something new for 1.6.0.0. In hopes that translating
Evergreen strings could be quick and easy, I imported the PO files for
the existing translations into LaunchPad at
https://translations.launchpad.net/evergreen 

Some of the advantages of translations in LaunchPad are:
  * matching strings from any of the other 10,000 projects in LaunchPad
can be used as suggestions for Evergreen translations
  * anyone can create or update an Evergreen translation in any language
(well, most languages) - they just need to sign up for a LaunchPad
account
  * it's a Web-based interface, so it's easy to drop in and translate a
handful of strings, as time permits
  * at a glance, you can see the status of a given language and drill
down to see the status of the individual templates per language

There are a couple of caveats, though:
  * we're currently pulling the strings from trunk, rather than from the
true 1.6.0.0 releases; this means that some strings might be out of
sync. In most cases it means that you may translate some extra strings
that won't be part of 1.6.0.0, but will be part of a future Evergreen
release.
  * any translations made in LaunchPad have to be made available under
the BSD license to other projects in LaunchPad; that's how the suggested
strings from other projects can be made available to Evergreen in
LaunchPad, because the BSD is one of the most permissive (and
compatible) licenses

As noted, right now anyone can sign up and add or change translations
for any language. If translation teams are interested in exerting
control over their particular language, it's possible to grant review
rights to one or more people on a per-language basis. It's even possible
to prevent submissions of suggested translations if a team wanted to go
that far.