[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: State of en_GB (was Re: Clean up of Kooka translations)
From:       Burkhard =?ISO-8859-1?Q?L=FCck?= <lueck () hube-lueck ! de>
Date:       2013-11-14 20:41:04
Message-ID: 31469701.p0kRVMBLpP () parodia
[Download RAW message or body]

Am Donnerstag, 14. November 2013, 20:04:44 schrieb Jonathan Marten:
> I hadn't considered the proofreading aspect of the en_GB work, but it is 
> definitely a good idea - there are some strings that I've noticed that
> don't  look right even in worldwide English.  How does the process work? -
> do we have carte blanche to jump in and change these wherever they may
> appear, or via the normal bug/review process?

In the past afair several members from en_GB team did a lot of proofreading + 
fixing of gui + docbook strings (Malcom Hunter, Andrew Coles etc.) and this was 
always much appreciated.

Please keep in mind:

* development language is en_US, but more than 50 % of the kde developers have 
a different native language

* developers are really "bad" in writing GUI strings, because they know too 
much about their application and have a technical pov.

* our GUI should be understandable for Joe User, not only for geeks often 
using much "slang" wording

* with a kde developer account you have write access to all source repos

* please respect string freeze according to the release schedules 
(http://techbase.kde.org/Schedules)

-- 
Burkhard Lück

[prev in list] [next in list] [prev in thread] [next in thread]