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

List:       kde-i18n-doc
Subject:    Re: Migration to Launchpad
From:       Albert Astals Cid <aacid () kde ! org>
Date:       2013-01-21 19:10:34
Message-ID: 1536189.rq40VD4JRA () xps
[Download RAW message or body]

El Dilluns, 21 de gener de 2013, a les 14:37:15, Tomáš Chvátal va escriure:
> 2013/1/21 Kevin Krammer <krammer@kde.org>:
> > On Monday, 2013-01-21, Vít Pelčák wrote:
> >> 2013/1/21 Yuri Chornoivan <yurchor@ukr.net>:
> >> > Mon, 21 Jan 2013 03:11:58 +0200 було написано Volkan Gezer
> >> > 
> >> > <vlkngzr@gmail.com>:
> >> >> Is it planned to use Launchpad for translations? Using po files are so
> >> >> hard
> >> >> to do synchronized translations working with many translators for each
> >> >> file.
> >> >> 
> >> >> -Volkan Gezer
> >> > 
> >> > Hi,
> >> > 
> >> > There are no such plans.
> >> > 
> >> > KDE translations were removed from Ubuntu language packs since 12.10
> >> > due
> >> > to lack of synchronization with upstream and the low quality of Ubuntu
> >> > teams crowd translations.
> >> > 
> >> > Rosetta does not show fuzzy suggestions and easy to use filters for
> >> > translations so it is not obvious to me how it can improve consistency.
> >> > Rosetta is very slow and unconfigurable compared to its analogues,
> >> > Transifex and Weblate. It is almost unmaintained, no improvements at
> >> > least for several years, just constant regressions (just imho).
> >> > 
> >> > Best regards,
> >> > Yuri
> 
> Actually as we are going to move to git 

Translations are not going to move to git.

Cheers,
  Albert

> it might be worth considering
> showeling summit into each teams throat and make the summit updates
> (scatter/merge automatic).
> Also putting weblate over such summit would be sweet so if some team
> desires web translations they can.
> 
> But moving the translations to different infrastructure is really not good
> idea.
> 
> Also if I manage to make the pology/weblate work for the opensuse
> translations (see my few last mails to this list) we can take look how
> poorly/great is it performing.
> 
> Tom
[prev in list] [next in list] [prev in thread] [next in thread]