Set up automatic translations import
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| SchoolTool |
Fix Released
|
Medium
|
Gediminas Paulauskas | ||
Bug Description
Currently there are three templates:
template branch # of messages
-------
schooltool schooltool 1010
schooltool.
schooltool.
This setup requires manual work - uploading the templates, downloading
and uploading translations. With recent improvements to launchpad
(see http://
part of this can be automated - specifically automatic import of templates
and translations from the branch. But we cannot do that if we have
several templates, and especially lyceum.journal which is a different branch
and cannot be monitored by launchpad.
The number of strings in those extra templates is very small compared to
the main template, so this separation brings little benefit for much
manual work and confusion for translators.
Moreover, we already pull schooltool.
so we can do the same with lyceum.journal
| tags: |
added: i18n removed: translations |
| Gediminas Paulauskas (menesis) wrote | #1 |
| Tom Hoffman (tom-hoffman) wrote | #2 |
| Changed in schooltool: | |
| milestone: | none → karmic |
| summary: |
- Merge translation templates into one + Set up automatic translations import |
| Changed in schooltool: | |
| status: | Confirmed → Fix Released |
| milestone: | karmic → 1.1.0 |
I will move lyceum.journal into a separate launchpad project, but also split out gradebook messages, because gradebook will also become a top-level project.
Not sure what to do with commendation, maybe make it a separate example package, because that's what it is.
To make full use of Launchpad Translations there has to be a single template per project. Moreover, it has to be hosted on Launchpad Code.