Tomasz Kłoczko wrote: > This how it IMO should be done: > > 1) every release of the package to git repos should automatically > pass them over filters extracting strings which needs to be > translated. > > 2) all phrases which needs to be translated should be hold in i18n .po > files as reference allowing to figure out that some of the already > translated phrases needs to be updated. All those strings should be > available probably over web frontend forming lists strings which > needs to be updated or still are without initial translations. > Changes in .po could be kept in VCS repo to tracka all changes > > 3) on build time packages all %descriptions and Summary fields needs > to be extracted and queried against reference .po files and on just > assembly binary packages all possible other languages should be added. That looks like a good plan for how large numbers of translators can contribute translations to many different languages. Writing the translations directly in the spec doesn't scale well when there are many languages and many translators, but it's very convenient in the special case where the translator is also the package maintainer. For the maintainer it would be much more trouble to edit the English description, commit and push, wait for the translation system to get updated, edit the translation in a different tool, and finally commit and push again. So to anyone who decides to implement Tomasz' proposal, please make it work together with translations in the spec, not replace them. Björn Persson
Attachment:
pgpvEYNbArQnq.pgp
Description: OpenPGP digital signatur
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
