#31: Translation management
Issue revisions
- new by Kore Nordmann at 2008-O-21 11:36
- new by Kore Nordmann at 2008-O-21 11:40
| Type |  enhancement |
|---|---|
| State |  new |
| Priority |  low |
| Resolution |  none |
| Assigned to | Nobody |
| Scheduled for | 1.0 |
| Affected versions | |
| Affected components | Modules |
| Last change | Tuesday 21 October 2008 11:40:45 UTC by Kore Nordmann |
Short description
Arbit itself will use QTLinguist files for interface translations. Other formats commonly used in projects are gettext, for example.
To increase the coverage of translations a module should be implemented which allows users to translate interface strings with some collaboration to find the "best" possible translation.
Kore Nordmann at Tuesday 21 October 2008 11:40:45 UTC
Scheduled for version 1.0.
Sivan Greenberg at Monday 26 April 2010 11:49:07 UTC
How do we define "best" possible translation ? Is there such a feature in another web tool we can look at to get an idea?
Sivan Greenberg at Monday 26 April 2010 11:50:40 UTC
so, this is going to be a collaborative translation tool? There are already enough out there, isn't this like re-inventing the wheel?
norro at Sunday 20 March 2011 10:27:48 UTC
http://crowdin.net/ seems to be a good way to do it, providing importers and exporters for QTLinguist translation files.