Στις 12-09-2007, ημέρα Τετ, και ώρα 15:43 +0200, ο/η nicolas.mailhot@laposte.net έγραψε:
De : "Jeremy Katz" katzj@redhat.com
Actually, nothing says that additional repos can't have their own specspo-type package as well.
This is considerably upping the bar to creation of a new repository, and making impossible the common "collect rpms, launch createrepo" workflow
Is it that bad really? It's a step that could be done by a script and have the POs hosted at the repo's own VCS, reached by transifex.
All of the above said, specspo probably _isn't_ the right answer...
Yes, it was hyped as necessary to make translator work easy, and now you have translators complaining of it.
Is there a way to have these PO files cut into more "logical" pieces? Translators for example would like to work incrementally from the most to the less important ones. Or, have a PO with packages that will (most likely) show up in the main screens of pirut, etc.
Maybe specspo is a good opportunity to start thinking about installing a pootle server. If the strings don't change very often, the maintenance cost (merging, etc) could be bearable.
-d