Allow to choose another than main branch for translation imports
Bug #880064 reported by
Dirk Stöcker
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
For JOSM I still try to setup an automatic translation data handling. I now did setup a bazaar branch for po file export which works fine. I would like to use the same branch for ."pot" file import, but the translation engine requests the main branch for this purpose. The main branch is a SVN-Importer, which cannot contain the data.
Please allow the possibility to define another than main branch for translation data file import.
Revision history for this message
| Jeroen T. Vermeulen (jtv) wrote | #1 |
| Changed in launchpad: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
| tags: | added: lp-translations translations-branch |
To post a comment you must log in.
This would be a good thing to have, but it requires UI changes that we probably won't have time to make anytime soon.
It's not ideal, but you could work around this by having a separate “release series” for translation, and import the branch into there.