From kde-i18n-doc Thu Jul 21 23:47:31 2016 From: "Wantoyo ." Date: Thu, 21 Jul 2016 23:47:31 +0000 To: kde-i18n-doc Subject: Re: kde-i18n-doc Indonesian language translations Message-Id: X-MARC-Message: https://marc.info/?l=kde-i18n-doc&m=146914488327251 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--001a113b08d206e05005382df1cc" --001a113b08d206e05005382df1cc Content-Type: text/plain; charset=UTF-8 2016-07-22 4:57 GMT+07:00 Albert Astals Cid : > 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. > > > --001a113b08d206e05005382df1cc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


2016-07-22 4:57 GMT+07:00 Albert Astals Cid <aacid@kde.org>:=
El dimecres, 20 de ju= liol 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 beca= me a
> > coordinator?
>
> You coordinate the translations into the Indonesian language. If you a= re 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. Y= ou
> collect the newly (partly) translated files and commit the files in th= e 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 f= or well
>formedness) and commit them and give you the next steps to proceed.

>Cheers,
>=C2=A0 Albert

=C2=A0Okay, I'= ll send some files to you.

>
> So you need have commit rights on that repository. For that you need t= o 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 ent= er
> the public key with your account. After that you need to ask for commi= t
> rights on svn.kde.org for the Indonesian language.
>
> Obviously you need the package subversion and related packages install= ed on
> your system.
>
> On your disk you need to setup a hierarchy of folders. I have kde4bran= ch,
> 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/k= de/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/h= ome/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.<= br> > 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 packa= ges.
> In pology you can find ./bin/posieve to check the .po files in docmess= ages
> and messages for errors.
>
> All the files you got with the above checkout are subject to changes o= n 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 ~/.subvers= ion with files
> that contains parameters needed by the above "svn up" comman= d.
> After a days work by you or your coworkers updated versions of .po fil= es 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 th= e translator. So
> something like "updated by translator_name".
>
> During an update you may get a message about a conflict. I leave it yo= u to
> figure out what to do.
>
> > Be happy if I could I was willing to be the coordinator of the In= donesian.
> >
> > Wantoyo
>
> Hope this gives you enough to start, otherwise ask.



--001a113b08d206e05005382df1cc--