On 25.08.2014 19:09, Robinson Tryon wrote:
What can we do to recruit more people to help with translations?
For me (an occasional translator) the biggest hurdle is the technical
overhead needed for some of the translations. Somebody like me, who just
wants to translate a page or correct some errors - being forced to learn
pootle (or similar tools) prevents me from "just starting".
Therefore in my eyes, a simpler workflow could substantially improve
crowd-sourcing of help file translations / corrections. Example:
- present an "edit" or "translate" button on every page or even paragraph
(could / should? be restricted to registered users)
- transmit the diff of such a user-made change to a group of reviewers with
"publish" rights
- make it easy to integrate the changes back into the original page (e.g.
by buttons "accept" / "edit" / "dismiss" (if spam etc)
- make history visible (e.g. like in Wikis) so that everybody can see, who
has contributed what
... well, that's just a proposal that came into my mind while reading your
question. Easy to request but heavy to implement, I suppose ;-)
Nino
--
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
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
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: 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.