Hello,

I found out that many emails can be grabbed directly from translation PO files. 
I found them in KDE applications, mainly the educational games. I copied the 
emails I found for Polish, Spanish and Swedish in a new private page:

http://www.doudoulinux.org/web/private/team/article/find-new-translators

I'll look at other languages on the flow. Please inform me if you wish to 
contact some of them.

JM.

> Hello,
> 
> What an opportunity you had, lucky woman!
> 
> All of this sounds good, 85 languages for our project is a good target
> ;). This shows that promotion campaigns is the right thing to do even
> while searching for translators, but not only. So I think we should
> try to mimic the way Mozilla is searching for contributors during the
> coming months.
> 
> 1. Contact translators of other projects → we can look at Gcompris,
> Childpslay, etc., and find emails of contributors (do not post them
> publicly please because of spam)
> 
> 2. Search for communities of translators → get in touch with our main
> upstream projects (Debian, LXDE and in a smaller extent Gnome/KDE), it
> was partially planned indeed, any other idea?
> 
> 3. Post in forums, blogs, etc. → we did this a bit but could do much
> more – 85 languages to reach…
> 
> 4. Always recall in our communication that we need contributors → we
> have to get used to doing this in all our articles/news
> 
> For the latest point I propose that all our external communications
> say at least in the end that we need contributors and that anyone can
> help translating. It can then be immediately applied. The second point
> can also start soon since I was planning to contact the Debian
> translation team to tell them about our Transifex portal.
> 
> For the remaining points I encourage you to tell me if you are
> interested in helping the project growth so that we can start to speed
> up our language panel expansion. I'd say that the first point may give
> better results if we're targeting child-oriented projects. Of course
> we'll need to take the time to help our new contributors begin their
> work.
> 
> Please tell me what's your feelings.
> 
> JM.
> 
> 
> > Hello all,
> >
> > I have meet the leader of the localisation of Mozilla, Pascal. A
> > sympathetic and interesting man which works is managing the
> > localisation in 85 languages all the product of Mozilla !
> >
> > When i discover his job, i ask him, thinking in DoudouLinux : How
> you
> > found all this contributors ?
> >
> > Of course, all the localisation (website & software & promotional
> > objects) are made by volunteers.
> >
> > He explain me that the problem is not how found but how keep them !
> >
> > He explain me different possibilities :
> > - he contact the translator of other free project and ask them
> > directly if they agree to translate in this languages for others
> > software.
> > - he search a translator community and ask them directly if they
> know
> > one people on this language.
> > - he post in many forum, use twitter, use blog a lot to found them
> > - every time he write on the web he put a line for contribution and
> > for translation
> >
> > Usually, for the first involvement he discuss a lot with this new
> > contributors. After he link him an easy and short translation for
> > giving them a good feeling. This first translation
> > is a way for him to analyse his skills. Second the level of his new
> > contributor, he put him in translation of article, of software, of
> > marketing etc etc. Offering them more
> > and more work, more and more difficult.
> >
> >
> > So, what is the better plan for DoudouLinux ;) ?
> >
> > Elisa
> >
> > _______________________________________________
> > Doudoulinux-dev mailing list
> > [email protected]
> > https://mail.gna.org/listinfo/doudoulinux-dev
> 
> _______________________________________________
> Doudoulinux-dev mailing list
> [email protected]
> https://mail.gna.org/listinfo/doudoulinux-dev

_______________________________________________
Doudoulinux-dev mailing list
[email protected]
https://mail.gna.org/listinfo/doudoulinux-dev

Reply via email to