[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:48:58
Message-ID: AANLkTimk1OcZxX6opnxOSunHke0ob2g8KEF2CZe_x40i () mail ! gmail ! com
[Download RAW message or body]

I am sorry, my KMail didn't show the message I sent, so I thought the
message wasn't sent. Sorry if you got two same messages.

2010/8/13 Park Shinjo <kde@peremen.name>

> 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
> >
>

[Attachment #3 (text/html)]

I am sorry, my KMail didn&#39;t show the message I sent, so I thought the message \
wasn&#39;t sent. Sorry if you got two same messages.<br><br><div \
class="gmail_quote">2010/8/13 Park Shinjo <span dir="ltr">&lt;<a \
href="mailto:kde@peremen.name" target="_blank">kde@peremen.name</a>&gt;</span><br> \
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px \
solid rgb(204, 204, 204); padding-left: 1ex;"> <div>Good. I am also translating \
VirtualBox, they requires translation of Qt, since Korean isn&#39;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.<br>


<br>
Qt Linguist has different set of shortcut keys and different UI, but there&#39;s a \
way to convert ts to po and vice versa, you may use your favorite po editor for \
translating Qt.<br> <br>
Now I am registering myself in gitorious and starting translation in upstream =)<br>
<br>
On 2010³â 8¿ù 12ÀÏ ¸ñ¿äÀÏ ¿ÀÀü 7:02:58 Albert Astals Cid wrote:<br>
</div><div><div></div><div>&gt; Hi, since some time Qt allows for translations to be \
contributed to Qt<br> &gt; upstream, so i&#39;d like to suggest us stopping to \
translate Qt (kdeqt.po)<br> &gt; locally and people contributing translations to the \
correct place (Qt proper).<br> &gt;<br>
&gt; Contributing Qt translations upstream will mean:<br>
&gt; &nbsp;* Qt but non KDE programs will also use your translations too, making \
your<br> &gt; contribution more useful (good)<br>
&gt; &nbsp;* Translations will be synced with Qt releases instead with KDE releases \
as<br> &gt; they should be (good)<br>
&gt; &nbsp;* You will use a different tools and format (linguist, .ts) (bad?)<br>
&gt; &nbsp;* You will have to give Nokia the right to license the translations under \
a<br> &gt; non free license (bad?)<br>
&gt;<br>
&gt; So i&#39;d like to ask for comments about what you think if working on the<br>
&gt; technical solution to allow Qt translations to be used (isntead of kdeqt.po<br>
&gt; ones) is worth or even if there are some good sides to it you don&#39;t want \
the<br> &gt; removal of kdeqt.po to happen.<br>
&gt;<br>
&gt; Albert<br>
&gt;<br>
</div></div></blockquote></div><br>



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