OK, I came up with something.

We can lock up the wiki registration and the Admin will have to approve each and every translator manually (TranslateWiki works that way when you want to contribute to MediaWiki).

That way the user will have to provide his/her real name upon registration.

There's also a possibility that the registration will remain open but the main coordinator will have to approve each translator manually, just like what Siebrand does.

Well, there are plenty of possibilities... Having a distinct TranslateWiki instance is not such a bad idea... (This way the current rules won't be applied).

What else can I check for you guys?

Kind regards,
Yaron Shahrabani
<Hebrew translator>



On Tue, Feb 28, 2012 at 3:03 PM, Aric Stewart <aric@codeweavers.com> wrote:
Hi,

I have had quite a long discussion with the TranslateWiki people.  They are great and while what we need would require a bit of PHP development they expressed that they would be happy to do the work.

The main sticking block is that our requirement for Real Names and e-mail for all contributors runs contrary to their privacy policy. So we would not be able to get that information in our patches.

They are currently exploring that idea and we are in continued discussion about this. If we can get around that road block then they may be our best option.

Transifex's Dimitris Glezos has also been very communicative with me, and very helpful, however Transifex does not actually do PO management converting the POs into their own database format and requiring developers to have a client tool to be able to get and push the translations. That could be done by a translation manager who would then generate all the patches and mail them with the proper credit.  However he still has not answered my basic question of if we would be able to get that information.

So I am still actively following up on these leads and hopefully something will work out.

-aric


On 2/28/12 1:42 AM, Yaron Shahrabani wrote:
Hi guys!

If I understand correctly the wanted solution is the translation
attribution will be per string basis meaning that we can attribute a
certain author to a string.

The only system I'm aware of that is capable of such thing is
TranslateWiki, which is a little overkill because we will have to use a
full wiki system in order to implement gettext (which can be done using
a much less sophisticated system).

Since the Wine project already has a Wiki, maybe we can utilize this
wiki in order to install TranslateWiki.

There are several advantages:
1. The strings are saved just like wiki pages meaning that there's a
full history and diff of all strings including dates and authors.
2. The statistics are great (The current statistics is nice as well but
contains less info).
3. It's a full wiki system (Both advantage and disadvantage).

None of the other systems can attribute a certain translation to a
certain author AFAICT.

Kind regards,
YaronShahrabani

   <Hebrew translator>




2012/2/27 Miroslav Suchý <msuchy@redhat.com <mailto:msuchy@redhat.com>>

   Hi,
   I just read:
   http://www.winehq.org/news/__2012022001
   <http://www.winehq.org/news/2012022001>
   and then
   http://wiki.winehq.org/__Translating

   <http://wiki.winehq.org/Translating>
   especially:

       The Wine project would be very interested in making its PO files
       available on web-based community translations systems such as
       Pootle or Launchpad. Our hope is that this would make
       translating Wine even easier and engage new translators.

       The reason why it has not happened yet is that all Wine
       contributions, including for translations, must be attributable
       to a specific author and that these tools don't make that
       possible yet. For more details see the wine-devel discussion
       here and here. Any contributions that would solve this issue
       would be very welcome.


   which refer:
   http://www.winehq.org/__pipermail/wine-devel/2012-__January/093908.html

   <http://www.winehq.org/pipermail/wine-devel/2012-January/093908.html>

   I would like to point you to:
   https://www.transifex.net/
   which can do the tracking.

   Latest version is probably not what you want, because it just add at
   the top of the file:
   # Translators:
   # Martin Minar <skulliq@gmail.com <mailto:skulliq@gmail.com>>, 2011
   <tel:2011>.
   # Milan Kerslager <kerslage@linux.cz <mailto:kerslage@linux.cz>>,
   2002 <tel:2002>, 2007 <tel:2007>.
   # Miloslav Trmac <mitr@volny.cz <mailto:mitr@volny.cz>>, 2002
   <tel:2002>.
   # Miroslav Suchý <msuchy@redhat.com <mailto:msuchy@redhat.com>>,
   2011 <tel:2011>.

   msgid ""
   msgstr ""
   "Project-Id-Version: Spacewalk\n"
   "Report-Msgid-Bugs-To: \n"
   "POT-Creation-Date: 2011-12-21 13:07+0100\n"
   "PO-Revision-Date: 2011-12-14 09:21+0000\n"
   "Last-Translator: Miroslav Suchý <msuchy@redhat.com
   <mailto:msuchy@redhat.com>>\n"
   "Language-Team: Czech
   (http://www.transifex.net/__projects/p/fedora/team/cs/
   <http://www.transifex.net/projects/p/fedora/team/cs/>)\n


   So you had overview of contributors, but you could not tell which
   one contributor done which string.

   But version 0.7 (IIRC) sent each contribution immediately to git.
   Under login (and email) of that contributor. That contributor was
   "Author" and commiter was some transifex user. So this way you allow
   git commit access to those contributors directly to git, but since
   it goes via that web interface, they could commit only to /po/
   directory and even only to language, for which they had been granted.

   You can download it here:
   http://trac.transifex.org/__files/ <http://trac.transifex.org/files/>

   and setup your own instance.

   If is sufficient for you only tracking name of contributors, you can
   use that hosted solution at: https://www.transifex.net/


   --
   Miroslav Suchy
   Red Hat Satellite Engineering