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

List:       kde-i18n-doc
Subject:    akademy l10n BoF wrap up
From:       Sebastien Renard <renard () kde ! org>
Date:       2013-07-18 8:27:27
Message-ID: 1802697.5iGMBybEgE () eniokafox
[Download RAW message or body]

Hello everybody,

We had a BoF during akademy 2013 (thanks Luigi for organization !). Here is a 
wrap up of main topics we discussed.

Attendees :
    Marta (Poland)
    Shinjo (Korea)
    Luigi (Italia)
    Luciano (Italia)
    Sébastien (France)
    Lasse (Finland)
    Adrian (Galicia)
    Claus (Danish, wikis)


l10n.kde.org website changes
----------------------------------------------------
* GSoC: integration with identity.kde.org, property assignment  for 
translation files/modules

* More information here: http://community.kde.org/KDE_Localization/LTMT

* Some comments:

	- Translators will need an identity account to book a file. An option 
could be to allow  "anonymous locking" by team coordinators (with note about 
the name  of the unregistered user) for new unregistered users
	- Booking file list won't be exactly the same as statistics file list; a 
file is booked for all branch (stable and trunk or summit if used)


Proposal about 3-months releases:  is one month of string freeze enough?
----------------------------------------------------------------------------------------------------------------------
                
* Most people in Bof thought that it is not a big issue

* For teams that are using the summit workflow the change will be very small.

* Point of attention: late branch merging adding lots of translation late in 
the process (that is mostly due to git transition, not directly related to 
release length but it can be worst with short release cycle).


Integration of wiki translations in the gettext-based workflow
--------------------------------------------------------------------------------------------------
                
* Two separate issues with current situation:
	- most of wiki translators are not related to local translation 
team.wiki-only people need integration into the team. 
	- bad quality (all teams in Bof testify that)

* We all agree on the following:
	- We would like to unify wiki and legacy translation team for each 
country (consistency, quality...)
	- We would like to allow each to choose between two organization modes:
		o Option 1: Integration in current worfklow: exporting of pot + bulk 
import from scripty, merging  and translation locked in wiki. Same workflow as 
for some websites (www_www, okular, www_edu etc.)
		o Option 2: use wiki for translation, no integration with scripty. 
But unified team (mailing list, coordinator etc.)


Report a typo
----------------------
* It is not very easy for users to report a typo. Many way to do it (mail to 
translator, to mailing list, open a bug in bugzilla and guess that i18n is for 
translation etc.)

* Some team (Poland) use translation credit field to ask users to report typo 
to team mailing list.

* We agree on the following:
	- buzilla is not suitable to report typo / translation errors
	- about application => translation is too hidden
	- a simple mail to locale l10n team is the easiest way to get usefull 
feedback

* ...and we propose this:
	- add a help menu entry "Report a typo" aside "Report a bug" (or inside 
bug wizard first screen) that just open mail editor to locale translation team
	- team mailing list will be a string that each team will translate to 
locale mail point of contact (mailing list or individual email)
	- cherry on the cake: automatically add information on catalogs loaded by 
application in the report
	- from the dev point of view, this could be overloaded to use different 
point of contact for third party application that use kde framework. That the 
way it works today for the bug report part.

    =>kdelibs folks are ok to do that (at least David and Kevin are :p)


Things that could/should be handled automatically:
-----------------------------------------------------------------------------------
* Version numbers, documentation release dates, contributor names, emails, ...
* Strings used repeatedly throughout KDE
  => some work  is currently done for doc release date by Luigi


Fixing typo or missing directly in code:
-------------------------------------------------------------

* We all agree on the fact that translators should be officially allowed to fix 
English strings and add or update context directly in code without prior 
developer agreement.

* This should be done for simple things (string changes, adding or changing 
context). Any other change must involve developers collaboration.

    => this is already done but just need to be said and written ;-)


Cheers
-- 
Sébastien


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