[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [libreoffice-documentation] Questions about Translations of the Guides


Hi :)
Sorry, only just dared to answer this one!  My opinion doesn't really count.  You probably have a far better idea of what is going on because of discussions in your team and from getting involved in the work. 

"Release early and release often" sometimes means just getting a first iteration out there that people can see and use even if you know parts of it are wrong or "not quite as perfect as you would like".  The next time you go through you have some notes or even just vague ideas of improvements you want to make and you may get a chance to do some of those changes. 
http://paulgraham.com/startuplessons.html

It means you get a result out there into the world so that people can see and use the result.  Some of that might result in criticism but a lot of that criticism can be turned around by inviting the critical people to join the team to help put things right. 

So, don't worry about re-doing things to be perfect.  Just get the first version out there.  Don't aim at perfect the first time.  That is my thought. 
Regards from
Tom :)


--- On Sun, 17/6/12, Zeki Bildirici <zeki@ozgurlukicin.com> wrote:

From: Zeki Bildirici <zeki@ozgurlukicin.com>
Subject: Re: [libreoffice-documentation] Questions about Translations of the Guides
To: documentation@global.libreoffice.org
Cc: "Tom Davies" <tomdavies04@yahoo.co.uk>
Date: Sunday, 17 June, 2012, 9:21

2012/6/17 Tom Davies <tomdavies04@yahoo.co.uk>
>
> Hi :)
> The embedded help in English is a bit old and out-of-date now.  Is your
> team checking it works and fixing it as they translate?  If so then it would
> be fantastic if we could translate it back into English!

Actually, we don’t check&report them as we considered them as "must be
recent" till now. And the localizers are not regular users of all the
applications.

We face them sometimes.
eg:https://translations.documentfoundation.org/tr/libo_help/translate.html?unit=14569917

Well, i think there might be a good feedback option for the QA of the
original strings. Pootle has a comment box, which we can add a
"unique" word to the strings which we may think:

- Outdated,
- Bad wording
- Vanished feature etc.

For example a unique word of comment as "tombalak", will work such a
tag, and it will be possible to track this strings and report them.

What's your opinion?

Regards,
Zeki

--
Unsubscribe instructions: E-mail to documentation+help@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/documentation/
All messages sent to this list will be publicly archived and cannot be deleted


--
Unsubscribe instructions: E-mail to documentation+help@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/documentation/
All messages sent to this list will be publicly archived and cannot be deleted

Follow-Ups:
Re: [libreoffice-documentation] Questions about Translations of the GuidesZeki Bildirici <zeki@ozgurlukicin.com>
References:
Re: [libreoffice-documentation] Questions about Translations of the GuidesZeki Bildirici <zeki@ozgurlukicin.com>
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 GNU Lesser General Public License (LGPLv3). "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.