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

List:       kde-i18n-doc
Subject:    Re: [RFC][IMPORTANT] Removing kdeqt.po
From:       Park Shinjo <kde () peremen ! name>
Date:       2010-08-13 9:45:30
Message-ID: 201008131845.31261.peremen () gmail ! com
[Download RAW message or body]

Good. I am also translating VirtualBox, they requires translation of Qt, since Korean \
isn't translated in Qt upstream. Fortunately I know the existence and translated \
kdeqt.po, there was no hassle for translating for them. Maybe another Qt-based \
project outside of KDE might require that, it will help them too.

Qt Linguist has different set of shortcut keys and different UI, but there's a way to \
convert ts to po and vice versa, you may use your favorite po editor for translating \
Qt.

Now I am registering myself in gitorious and starting translation in upstream =)

On 2010년 8월 12일 목요일 오� � 7:02:58 Albert Astals Cid wrote:
> Hi, since some time Qt allows for translations to be contributed to Qt 
> upstream, so i'd like to suggest us stopping to translate Qt (kdeqt.po) 
> locally and people contributing translations to the correct place (Qt proper).
> 
> Contributing Qt translations upstream will mean:
> * Qt but non KDE programs will also use your translations too, making your 
> contribution more useful (good)
> * Translations will be synced with Qt releases instead with KDE releases as 
> they should be (good)
> * You will use a different tools and format (linguist, .ts) (bad?)
> * You will have to give Nokia the right to license the translations under a 
> non free license (bad?)
> 
> So i'd like to ask for comments about what you think if working on the 
> technical solution to allow Qt translations to be used (isntead of kdeqt.po 
> ones) is worth or even if there are some good sides to it you don't want the 
> removal of kdeqt.po to happen.
> 
> Albert
> 


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