Switch translation to use transifex.com
Over the past years the number of maintained translations for YAM are constantly decreasing. While this might be perfectly correlated with the decreasing number of Amiga users/translators left, one can also argue that the way translations have to be performed and maintained is too complicated. Having to deal with subversion and change log entries might be one reasons. It is therefore desirable to evaluate alternatives to the current approach of directly editing the catalog translation files (.ct) which could be cumbersome and error prone as well as too complicated for some people not trained with them. Last not least the quality of the actually language translations of YAM are somehow unknown as today at most there is only one translator per language without any cross-checking mechanisms between translators in any form.
In recent years a free online service appeared on the internet (www.transifex.com) which allows to not only provide a central place to deal with application translations. It also provides a nice and smooth online editor for editing all kind of translations with functionality like allowing to provide comments to potential translators, building groups of translators and even allowing to verify translations of each other. In addition, as transifex.com is meant to be a community-driven translation service it has an increasing number of translation groups so that new fresh and Amiga-independent translators might even contribute to individual translations of YAM. It is therefore very attractive to consider switching to transifex rather than having to manually editing the .ct file and submitting it either via email to the yam developers or via directly checking in changes to our subversion repository. Furthermore, transifex also provides a python-driven command-line client which allows to directly pull and push translations from the command-line so that interaction between a repository checkin and transifex translations are possible.
After analysis and testing of transifex.com the only currently existing hurdle in directly switching to it is, that it doesn't directly support the Amiga-style catalog format. In addition, there doesn't seem to be a mechanism to even train or enhance transifex to use that format. However, as it supports a wide range of different translation file formats it also supports the probably most used format, the GNU gettext-based PO-style format for translations. While this format is currently not directly supported by e.g. flexcat it seems to be quite easily possible to develop conversion tools between these formats so that the transifex services can be used. The proposed procedure for switching to transifex is therefore:
The most critical point seems to be point 6 which should assure that if a translator prefers to directly editing the .po files in the repository these changes are directly uploaded to transifex. In addition, if changes are performed on transifex also the repository should be updated in regular intervals so that it is kept in sync.
Change History (4)
Note: See TracTickets for help on using tickets.
This list contains all users that will be notified about changes made to this ticket.
These roles will be notified: Reporter, Owner, Subscriber