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

List:       kde-i18n-doc
Subject:    Re: GCompris translation in belarusian
From:       Antos Vaclauski <vaclau () zkodam ! info>
Date:       2016-05-28 6:03:16
Message-ID: 20160528060316.GA24463 () 7398
[Download RAW message or body]

Hi all, thank you for your replies. I've realised that the matter was just in \
commiting a new folder to a new branch :) Done it, hope the commit message is fine - \
I used SVN_SILENT keyword. Sorry for raising such a kind of a "non-problem" issue

On Wed, May 25, 2016 at 10:49:21PM +0200, JAZEIX Johnny wrote:
> Hi,
> 
> disclaimer: I'm not a translator ;)
> 
> So as I understand, there are 2 branches:
> https://websvn.kde.org/branches/stable/l10n-kf5/be/ for the latest
> "release" and https://websvn.kde.org/trunk/l10n-kf5/be/ for the
> current source code.
> 
> Basically, when you push in the repository you pushed \
> (svn+ssh://svn@svn.kde.org/home/kde/trunk/l10n-kf5/be/messages/extragear-edu), it \
> will affect the trunk version (you can see the result in \
> http://l10n.kde.org/stats/gui/trunk-kf5/po/gcompris_qt.po/ where belarusian is \
> 100%). 
> You also need to push in the branches/stable repository \
> (svn+ssh://svn@svn.kde.org/home/kde/branches/stable/l10n-kf5/be/messages/extragear-edu/gcompris_qt.po)
>  for the "release" (it will be visible in
> http://l10n.kde.org/stats/gui/stable-kf5/po/gcompris_qt.po/).
> 
> For now, both version have the same strings (we just freezed it and
> didn't add/update any string) so you can just create the folder,
> copy/paste the translation file and add them to the svn repository.
> 
> Tosky, in irc, suggested that you can use Summit:
> https://techbase.kde.org/Localization/Workflows/PO_Summit which
> consolidates the various version in different branches in a single
> file. This way, you will only have one po file (containing the
> sentences to translate of both branches).
> 
> I don't know if it asks more work than handling the two different
> branches so I let you decide what you prefer.
> 
> I'm cc-ing the i18n teams as they may help better than me.
> 
> I hope I was clear enough (and didn't say wrong things) else don't
> hesitate to ask.
> 
> Thanks,
> 
> Johnny
> 
> On 05/25/16 21:25, Antos Vaclauski wrote:
> > Hi,
> > 
> > I'm afraid I don't fully realize this process in the svn world. Could you guide \
> > me a little ? What does it mean to report - should I commit somehow into the \
> > stable branch ? Thank you in advance 
> > On Tue, May 24, 2016 at 08:37:34PM +0200, JAZEIX Johnny wrote:
> > > Hi,
> > > 
> > > I'm a GCompris developer. We saw that you did translation for
> > > GCompris in belarusian. Thanks a lot!
> > > 
> > > We have it in trunk \
> > > (https://websvn.kde.org/trunk/l10n-kf5/be/messages/extragear-edu/gcompris_qt.po?view=log)
> > >  but not in the stable version (which should be in \
> > > https://websvn.kde.org/branches/stable/l10n-kf5/be/messages/extragear-edu/gcompris_qt.po?view=log).
> > >  
> > > Can you report it or do you want me to do it?
> > > 
> > > Thanks again for the translation.
> > > 
> > > Johnny
> 


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