[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-i18n-doc
Subject: Re: kde-i18n-doc Indonesian language translations
From: "Wantoyo ." <wantoyek () gmail ! com>
Date: 2016-07-21 23:47:31
Message-ID: CAHSFn7D7CyhE+HWArgLR=rqu3m819G-A0Kc0XAWE=0m4wV8DnQ () mail ! gmail ! com
[Download RAW message or body]
2016-07-22 4:57 GMT+07:00 Albert Astals Cid <aacid@kde.org>:
> El dimecres, 20 de juliol de 2016, a les 16:40:20 CEST, Freek de Kruijf va
> escriure:
> > Op woensdag 20 juli 2016 20:02:29 CEST schreef Wantoyo .:
> > > I must be a coordinator ?!
> > > What should I do and what my responsibilities for later if I became a
> > > coordinator?
> >
> > You coordinate the translations into the Indonesian language. If you are
> the
> > only one it is easy. If there are more translators you divide the work
> > among yourself and the others, so nobody works on the same .po file. You
> > collect the newly (partly) translated files and commit the files in the
> svn
> > repository.
>
> >This is a quite good explanation.
>
> >There's one missing bit and it is how you get commit access.
>
> >For that please first send me *in private* the files you have already
> >translated, i'll give them some formal review (not indonesian but for well
> >formedness) and commit them and give you the next steps to proceed.
>
> >Cheers,
> > Albert
>
> Okay, I'll send some files to you.
>
> > So you need have commit rights on that repository. For that you need to
> have
> > a key pair in .ssh without a passphrase. You need an account on kde.org.
> > Same that you use to enter a bug report. Because access to
> techbase.kde.org
> > is currently not possible I cant find the website on which you can enter
> > the public key with your account. After that you need to ask for commit
> > rights on svn.kde.org for the Indonesian language.
> >
> > Obviously you need the package subversion and related packages installed
> on
> > your system.
> >
> > On your disk you need to setup a hierarchy of folders. I have kde4branch,
> > kde4trunk, kf5branch and kf5trunk.
> > In each of these folders you need to give commands like:
> > cd ..../kde4trunk
> > svn checkout svn+ssh://svn@svn.kde.org/home/kde/trunk/l10n-kde4/id
> > svn checkout svn+ssh://
> svn@svn.kde.org/home/kde/trunk/l10n-kde4/templates
> > svn checkout svn+ssh://svn@svn.kde.org/home/kde/trunk/l10n-kde4/scripts
> > svn checkout svn+ssh://
> svn@svn.kde.org/home/kde/trunk/l10n-support/pology
> >
> > These commands create subfolders: id, templates, scripts, and pology.
> > In id, in a lower folder, you will find your .po files.
> > In templates you will find the .pot files.
> > In scripts the most important script is update_xml which generates the
> > docbooks in id/docs/....
> > This script needs the package git to be installed and some other
> packages.
> > In pology you can find ./bin/posieve to check the .po files in
> docmessages
> > and messages for errors.
> >
> > All the files you got with the above checkout are subject to changes on a
> > daily basis.
> >
> > You need to update all these files using the command:
> > cd ....kde4trunk
> > svn update id templates scripts pology
> > The above "svn checkout" commands create a folder ~/.subversion with
> files
> > that contains parameters needed by the above "svn up" command.
> > After a days work by you or your coworkers updated versions of .po files
> are
> > in your id folder.
> > You commit these updates in the folder id using the command:
> > svn -m "some comment" commit id
> > "some commend" can be anything, I use it to give honor to the
> translator. So
> > something like "updated by translator_name".
> >
> > During an update you may get a message about a conflict. I leave it you
> to
> > figure out what to do.
> >
> > > Be happy if I could I was willing to be the coordinator of the
> Indonesian.
> > >
> > > Wantoyo
> >
> > Hope this gives you enough to start, otherwise ask.
>
>
>
[Attachment #3 (text/html)]
<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">2016-07-22 \
4:57 GMT+07:00 Albert Astals Cid <span dir="ltr"><<a href="mailto:aacid@kde.org" \
target="_blank">aacid@kde.org</a>></span>:<br><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">El dimecres, 20 de juliol de 2016, a les 16:40:20 \
CEST, Freek de Kruijf va<br> escriure:<br>
> Op woensdag 20 juli 2016 20:02:29 CEST schreef Wantoyo .:<br>
> > I must be a coordinator ?!<br>
> > What should I do and what my responsibilities for later if I became a<br>
> > coordinator?<br>
><br>
> You coordinate the translations into the Indonesian language. If you are the<br>
> only one it is easy. If there are more translators you divide the work<br>
> among yourself and the others, so nobody works on the same .po file. You<br>
> collect the newly (partly) translated files and commit the files in the svn<br>
> repository.<br>
<br>
>This is a quite good explanation.<br>
<br>
>There's one missing bit and it is how you get commit access.<br>
<br>
>For that please first send me *in private* the files you have already<br>
>translated, i'll give them some formal review (not indonesian but for \
well<br> >formedness) and commit them and give you the next steps to proceed.<br>
<br>
>Cheers,<br>
> Albert<br>
<br></blockquote><div> <span tabindex="-1" id="result_box" class="" \
lang="en"><span>Okay</span><span>,</span> <span>I</span><span>'ll</span> \
<span>send some</span> <span>files to</span> \
<span>you</span><span>.<br><br></span></span></div><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"> ><br>
> So you need have commit rights on that repository. For that you need to have<br>
> a key pair in .ssh without a passphrase. You need an account on <a \
href="http://kde.org" rel="noreferrer" target="_blank">kde.org</a>.<br> > Same \
that you use to enter a bug report. Because access to <a \
href="http://techbase.kde.org" rel="noreferrer" \
target="_blank">techbase.kde.org</a><br> > is currently not possible I cant find \
the website on which you can enter<br> > the public key with your account. After \
that you need to ask for commit<br> > rights on <a href="http://svn.kde.org" \
rel="noreferrer" target="_blank">svn.kde.org</a> for the Indonesian language.<br> \
><br> > Obviously you need the package subversion and related packages \
installed on<br> > your system.<br>
><br>
> On your disk you need to setup a hierarchy of folders. I have kde4branch,<br>
> kde4trunk, kf5branch and kf5trunk.<br>
> In each of these folders you need to give commands like:<br>
> cd ..../kde4trunk<br>
> svn checkout svn+ssh://<a \
href="http://svn@svn.kde.org/home/kde/trunk/l10n-kde4/id" rel="noreferrer" \
target="_blank">svn@svn.kde.org/home/kde/trunk/l10n-kde4/id</a><br> > svn checkout \
svn+ssh://<a href="http://svn@svn.kde.org/home/kde/trunk/l10n-kde4/templates" \
rel="noreferrer" target="_blank">svn@svn.kde.org/home/kde/trunk/l10n-kde4/templates</a><br>
> svn checkout svn+ssh://<a \
href="http://svn@svn.kde.org/home/kde/trunk/l10n-kde4/scripts" rel="noreferrer" \
target="_blank">svn@svn.kde.org/home/kde/trunk/l10n-kde4/scripts</a><br> > svn \
checkout svn+ssh://<a \
href="http://svn@svn.kde.org/home/kde/trunk/l10n-support/pology" rel="noreferrer" \
target="_blank">svn@svn.kde.org/home/kde/trunk/l10n-support/pology</a><br> ><br>
> These commands create subfolders: id, templates, scripts, and pology.<br>
> In id, in a lower folder, you will find your .po files.<br>
> In templates you will find the .pot files.<br>
> In scripts the most important script is update_xml which generates the<br>
> docbooks in id/docs/....<br>
> This script needs the package git to be installed and some other packages.<br>
> In pology you can find ./bin/posieve to check the .po files in docmessages<br>
> and messages for errors.<br>
><br>
> All the files you got with the above checkout are subject to changes on a<br>
> daily basis.<br>
><br>
> You need to update all these files using the command:<br>
> cd ....kde4trunk<br>
> svn update id templates scripts pology<br>
> The above "svn checkout" commands create a folder ~/.subversion with \
files<br> > that contains parameters needed by the above "svn up" \
command.<br> > After a days work by you or your coworkers updated versions of .po \
files are<br> > in your id folder.<br>
> You commit these updates in the folder id using the command:<br>
> svn -m "some comment" commit id<br>
> "some commend" can be anything, I use it to give honor to the \
translator. So<br> > something like "updated by translator_name".<br>
><br>
> During an update you may get a message about a conflict. I leave it you to<br>
> figure out what to do.<br>
><br>
> > Be happy if I could I was willing to be the coordinator of the \
Indonesian.<br> > ><br>
> > Wantoyo<br>
><br>
> Hope this gives you enough to start, otherwise ask.<br>
<br>
<br>
</blockquote></div><br></div></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic