One of Pootle shortcomings in my experience is lack of changes tracking.
I don't see Pootle as techi tool. If you know how to log into facebook
and post comment, you know how to translate on Pootle.
But problem is, new people don't know what they did good and what wasn't
For example, when you get new team member, you don't give him write
permission, only permission to suggest.
He makes 50 string suggestions, and I go trough all of them accepting,
refusing and editing mistakes.
But when I'm done, he can't possibly know what I accepted or corrected.
My first translation was Mozilla Thunderbird, and my mentor was long
time Firefox translator.
HG was terrible, terrible tool for translating, but one of it strong
points was change tracking.
I learned what I did wrong and how to improve my translations from that
same change tracking system.
Sometime I even corrected mentor, everyone makes mistakes. :)
I miss something like that in Pootle, to provide new people way to see
their mistakes and improve their skills with that.
2.9.2014 u 10:26, Tom Davies je napisao/la:
2 separate issues;
Wrt recruiting new people there is a constant source of potential new
people on the various Users Support mailing lists.
Most have arrived there to get answers to 1 or 2 questions and were
toooo focused and/or confused to notice any of "the other stuff" that
goes on, such as different mailing-lists for different teams. Often
people on those mailing lists have no idea how to get involved. They
are often surprised to learn that they can join other teams just as
'easily' as they joined the Users Support mailing list and that the
instructions on how to do so were right at the beginning of their trek
to join the Users Support mailing lists.
I think mentioning, about once per month (or maybe fortnightly but not
too often)) the L10n mailing list and maybe your specific language
mailing lists on your User Support mailing-lists might attract some
As far as native English speakers go, the people in their current
Documentation Team's mailing list are not very technically minded and
had a big struggle trying to understand how to edit wiki's. Anything
more complex, even Pootle, would be a major blocker for them. They
all use ODFAuthors. So, anyone new only gets help as long as they are
trying to use ODFAuthors too.
I try to help people understand how to do wiki-editing but i am a
hugely unpopular maverick there. People generally don't join these
teams to instantly find themselves embroiled in a fight = they just
want to get on with doing something useful. So new people joining
their team either also avoid me and wiki-editing or drop-out. The
English Faq has been mostly done by Sophie and Alex (who seem to be in
all teams and have tons of energy) or by people who are nothing to do
with the English Docs Team. The English-speakers Documentation Team
can only cope with doing the Published Guides.
1. I think you might be able to recruit more people from the User
Support mailing lists but don't spam them with adverts and requests
too much or too often! There are other places such as social media
and all the usual good places to market stuff but the User Support
mailing lists are an extra place that might be fruitful.
2. If you want native English speakers then you might have to think
how to attract people who are not already in the English-speakers
To unsubscribe e-mail to: email@example.com
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted
- Re: [libreoffice-l10n] Transfering HELP from AOO to LO (continued)
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy