[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-i18n-doc
Subject: Re: [RFC][IMPORTANT] Removing kdeqt.po
From: Marek Laane <bald () smail ! ee>
Date: 2010-08-13 15:48:08
Message-ID: AANLkTin3da55_8mR86zVOJmvEqT_OqfgHfq5m_FpD4Oq () mail ! gmail ! com
[Download RAW message or body]
2010/8/12 Albert Astals Cid <aacid@kde.org>
> A Dijous, 12 d'agost de 2010, Marek Laane va escriure:
> > 2010/8/12 Albert Astals Cid <aacid@kde.org>
> >
> > > A Dijous, 12 d'agost de 2010, Marek Laane va escriure:
> > > > 2010/8/12 Albert Astals Cid <aacid@kde.org>
> > > >
> > > > > A Dijous, 12 d'agost de 2010, Marek Laane va escriure:
> > > > > > 2010/8/12 Albert Astals Cid <aacid@kde.org>
> > > > > >
> > > > > > > A Dijous, 12 d'agost de 2010, Martin Schlander va escriure:
> > > > > > > > Torsdag den 12. august 2010 00:02:58 skrev Albert Astals Cid:
> > > > > > > > > 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?)
> > > > > > > >
> > > > > > > > How difficult would it be to go the middle ground? Meaning
> keep
> > > > > > > > a
> > > > >
> > > > > qt.po
> > > > >
> > > > > > > in
> > > > > > >
> > > > > > > > kde svn - but we translate it on Qt schedule and send it
> > >
> > > upstream.
> > >
> > > > > Sort
> > > > >
> > > > > > > of
> > > > > > >
> > > > > > > > like how it's done with Amarok and other projects living
> > > > > > > > outside
> > >
> > > of
> > >
> > > > > kde
> > > > >
> > > > > > > > svn - but doing so completely transparently for the kde
> > >
> > > translator.
> > >
> > > > > > > This is not an option.
> > > > > > >
> > > > > > > Albert
> > > > > >
> > > > > > Because of the license or are there some other objections?
> > > > >
> > > > > Because of the license and because for Amarok we are the only place
> > >
> > > where
> > >
> > > > > translations happen and for Qt there would be 2, giving place to
> > > > > conflicts and
> > > > > other problems.
> > > > >
> > > > > Albert
> > > >
> > > > Well, that would be probably not so big problem as we have also 2
> > > > places, one for stable and one for trunk. I don't know exactly Qt's
> > > > tradition but
> > >
> > > I
> > >
> > > > suppose they have also at least stable and trunk...
> > >
> > > No, you don't understand me, there will be two places with translations
> > > KDE repository and Qt repository, each with stable and trunk
> > > translations.
> > >
> > > Albert
> >
> > Err, I do not really... If Qt has stable and trunk, can't they be related
> > stable and trunk, respectively, for KDE translators? Essentially so as by
> > now we have the kdeqt.po in stable and in trunk. Of course, it requires
> > that Qt side is ready to synchronize translations made by KDE
> > translators...
> >
> > Or do you mean Qt has some translators absolutely not connected to KDE?
> As
> > there is quite few Qt tranlations so far, ti would be not very big
> problem,
> > I assume?
>
> Of course, Qt has its own translations, that's where i am asking you to
> contribute to and that's why it would create conflicts.
>
> Albert
>
> Understood. One more question: if kdeqt.po will go, how can one become Qt's
translator? Is there some web formular, mailing list, something else you
have to contact etc?
> >
> > > > > > > > Using Linguist you'll surely miss your translation memory and
> > >
> > > some
> > >
> > > > > > > > other excellent Lokalize features, and I guess learning a bit
> > > > > > > > of git will be needed too, joining another mailinglist, keep
> > > > > > > > track
> > >
> > > of
> > >
> > > > > > > > the schedules and deadlines of a different project etc., so
> > > > > > > > it'd be a bit of a learning curve and extra work for sure.
> But
> > > > > > > > it
> > >
> > > might
> > >
> > > > > > > > be the
> > > > >
> > > > > right
> > > > >
> > > > > > > > thing to do do nevertheless.
> > > > > > > >
> > > > > > > > Also the Qt l10n project seems a bit crude and immature:
> > > > > > > > http://qt.gitorious.org/qt/pages/QtLocalization
> > > > > > > >
> > > > > > > > At least I don't easily find any info on status/stats of
> > >
> > > languages,
> > >
> > > > > > > > team pages or anything really.
>
[Attachment #3 (text/html)]
<br><br><div class="gmail_quote">2010/8/12 Albert Astals Cid <span dir="ltr"><<a \
href="mailto:aacid@kde.org">aacid@kde.org</a>></span><br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex;"> <div><div></div><div class="h5">A Dijous, 12 d'agost de \
2010, Marek Laane va escriure:<br> > 2010/8/12 Albert Astals Cid <<a \
href="mailto:aacid@kde.org">aacid@kde.org</a>><br> ><br>
> > A Dijous, 12 d'agost de 2010, Marek Laane va escriure:<br>
> > > 2010/8/12 Albert Astals Cid <<a \
href="mailto:aacid@kde.org">aacid@kde.org</a>><br> > > ><br>
> > > > A Dijous, 12 d'agost de 2010, Marek Laane va escriure:<br>
> > > > > 2010/8/12 Albert Astals Cid <<a \
href="mailto:aacid@kde.org">aacid@kde.org</a>><br> > > > > ><br>
> > > > > > A Dijous, 12 d'agost de 2010, Martin Schlander va \
escriure:<br> > > > > > > > Torsdag den 12. august 2010 00:02:58 \
skrev Albert Astals Cid:<br> > > > > > > > > Hi, since some \
time Qt allows for translations to be<br> > ><br>
> > contributed<br>
> ><br>
> > > > > > > > to Qt upstream, so i'd like to suggest us \
stopping to<br> > > > > > > > > translate Qt (kdeqt.po) \
locally and people contributing<br> > > > > > > > > \
translations to the correct place (Qt proper).<br> > > > > > > > \
><br> > > > > > > > > Contributing Qt translations \
upstream will mean:<br> > > > > > > > > * Qt but non KDE \
programs will also use your translations<br> > > > > > > > > \
too, making your<br> > > > > > > > ><br>
> > > > > > > > contribution more useful (good)<br>
> > > > > > > ><br>
> > > > > > > > * Translations will be synced with Qt \
releases instead with<br> > ><br>
> > KDE<br>
> ><br>
> > > > > > releases<br>
> > > > > ><br>
> > > > > > > > as they should be (good)<br>
> > > > > > > ><br>
> > > > > > > > * You will use a different tools and format \
(linguist, .ts)<br> > > > > > > > > (bad?) * You will have \
to give Nokia the right to license<br> > > > > > > > > \
the<br> > > > ><br>
> > > > translations<br>
> > > ><br>
> > > > > > > > under<br>
> > > > > > > ><br>
> > > > > > > > a non free license (bad?)<br>
> > > > > > ><br>
> > > > > > > How difficult would it be to go the middle ground? \
Meaning keep<br> > > > > > > > a<br>
> > > ><br>
> > > > qt.po<br>
> > > ><br>
> > > > > > in<br>
> > > > > ><br>
> > > > > > > kde svn - but we translate it on Qt schedule and \
send it<br> > ><br>
> > upstream.<br>
> ><br>
> > > > Sort<br>
> > > ><br>
> > > > > > of<br>
> > > > > ><br>
> > > > > > > like how it's done with Amarok and other \
projects living<br> > > > > > > > outside<br>
> ><br>
> > of<br>
> ><br>
> > > > kde<br>
> > > ><br>
> > > > > > > svn - but doing so completely transparently for \
the kde<br> > ><br>
> > translator.<br>
> ><br>
> > > > > > This is not an option.<br>
> > > > > ><br>
> > > > > > Albert<br>
> > > > ><br>
> > > > > Because of the license or are there some other \
objections?<br> > > > ><br>
> > > > Because of the license and because for Amarok we are the only \
place<br> > ><br>
> > where<br>
> ><br>
> > > > translations happen and for Qt there would be 2, giving place \
to<br> > > > > conflicts and<br>
> > > > other problems.<br>
> > > ><br>
> > > > Albert<br>
> > ><br>
> > > Well, that would be probably not so big problem as we have also 2<br>
> > > places, one for stable and one for trunk. I don't know exactly \
Qt's<br> > > > tradition but<br>
> ><br>
> > I<br>
> ><br>
> > > suppose they have also at least stable and trunk...<br>
> ><br>
> > No, you don't understand me, there will be two places with \
translations<br> > > KDE repository and Qt repository, each with stable and \
trunk<br> > > translations.<br>
> ><br>
> > Albert<br>
><br>
> Err, I do not really... If Qt has stable and trunk, can't they be \
related<br> > stable and trunk, respectively, for KDE translators? Essentially so \
as by<br> > now we have the kdeqt.po in stable and in trunk. Of course, it \
requires<br> > that Qt side is ready to synchronize translations made by KDE<br>
> translators...<br>
><br>
> Or do you mean Qt has some translators absolutely not connected to KDE? As<br>
> there is quite few Qt tranlations so far, ti would be not very big problem,<br>
> I assume?<br>
<br>
</div></div>Of course, Qt has its own translations, that's where i am asking you \
to<br> contribute to and that's why it would create conflicts.<br>
<font color="#888888"><br>
Albert<br>
</font><div><div></div><div class="h5"><br></div></div></blockquote><div>Understood. \
One more question: if kdeqt.po will go, how can one become Qt's translator? Is \
there some web formular, mailing list, something else you have to contact etc?</div> \
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex;"><div><div class="h5"> ><br>
> > > > > > > Using Linguist you'll surely miss your \
translation memory and<br> > ><br>
> > some<br>
> ><br>
> > > > > > > other excellent Lokalize features, and I guess \
learning a bit<br> > > > > > > > of git will be needed too, \
joining another mailinglist, keep<br> > > > > > > > track<br>
> ><br>
> > of<br>
> ><br>
> > > > > > > the schedules and deadlines of a different project \
etc., so<br> > > > > > > > it'd be a bit of a learning curve \
and extra work for sure. But<br> > > > > > > > it<br>
> ><br>
> > might<br>
> ><br>
> > > > > > > be the<br>
> > > ><br>
> > > > right<br>
> > > ><br>
> > > > > > > thing to do do nevertheless.<br>
> > > > > > ><br>
> > > > > > > Also the Qt l10n project seems a bit crude and \
immature:<br> > > > > > > > <a \
href="http://qt.gitorious.org/qt/pages/QtLocalization" \
target="_blank">http://qt.gitorious.org/qt/pages/QtLocalization</a><br> > > \
> > > > ><br> > > > > > > > At least I don't \
easily find any info on status/stats of<br> > ><br>
> > languages,<br>
> ><br>
> > > > > > > team pages or anything really.<br>
</div></div></blockquote></div><br>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic