[schooltool-dev] translation workflow

[Tom Hoffman]

Let's try to work out the future workflow -- from the user's point of
view -- for SchoolTool translations and releases, starting with how it
should work once we have a regular cycle of six-month releases:

I'm a user in, say, Vietnam.  SchoolTool 10.10 came out a few months
ago as a stable release.  There is no Vietnamese translation at this
point.  I navigate to
https://translations.launchpad.net/schooltool/2010.10/+translations
and translate the whole thing to Vietnamese.  Hopefully this is a
complete translation for everything I get when I 'apt-get install
schooltool-2010.10'  Nonetheless, if I want to use these translations
in my new install of SchoolTool, some wrangling of files into the
proper locations on my system will be necessary, but there is
documentation.

The alternative to this is having just a "schooltool trunk"
translation template.  The drawbacks of this would include the fact
that this might include changes since 10.10, so it might be
incompatible with the released version(s).

When SchoolTool 11.4 is approaching release there will be a string
freeze, and new translation templates will be uploaded to Launchpad.
The translations that I did for 10.10 need to be included
automatically, and this time I just have to translate new strings.  If
I get this done before the deadline for submitting translations, these
will be included in the 11.4 release, so I won't have to do any
additional file downloading and copying to use my translation.

Sound right (and doable)?

--Tom