From kde-i18n-doc  Tue Dec 30 22:04:26 2014
From: Albert Astals Cid <aacid () kde ! org>
Date: Tue, 30 Dec 2014 22:04:26 +0000
To: kde-i18n-doc
Subject: Re: kbibtex, po/ directory in sources
Message-Id: <1853375.MmgS1iaBTG () xps>
X-MARC-Message: https://marc.info/?l=kde-i18n-doc&m=141997708024099
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart1713203.WpCH4A3Bsd"


--nextPart1713203.WpCH4A3Bsd
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"

El Dimarts, 30 de desembre de 2014, a les 23:02:20, Thomas Fischer va 
escriure:
> Hello Albert,
> 
> On Tue, Dec 30, 2014 at 10:48:59PM +0100, Albert Astals Cid wrote:
> > El Dimarts, 30 de desembre de 2014, a les 22:44:23, Thomas Fischer va
> > 
> > escriure:
> > > On Sat, Dec 27, 2014 at 04:05:19PM +0100, Luigi Toscano wrote:
> > > > Thomas Fischer ha scritto:
> > > > > I checked with techbase.kde.org. The most fitting text I could
> > > > > find on extragear modules that want to integrate .po files is
> > > > > this one:
> > > > > https://techbase.kde.org/Development/Tutorials/Localization/i18n_Cha
> > > > > llen
> > > > > ges#KDE_Extra_Gear_Releases It talks about 'branches', which means
> > > > > it
> > > > > was written for
> > > > > Subversion. Do you have any more current information or can
> > > > > point me into the right direction?
> > > > 
> > > > I remember at least two scripts, release-tools and releaseme, see this
> > > > answer from Burkhard to the almost same issue on kde-i18n-doc@, and
> > > > the
> > > > follow-up messages:
> > > > http://lists.kde.org/?l=kde-i18n-doc&m=141607083027117&w=2
> > > > I'm replying on kde-i18n-doc@, where other people can help as well
> > > > more
> > > > than me :)
> > > 
> > > I checked with other extragear projects and found a number of
> > > scripts (written in Bash, Ruby, Python, ...) used to download
> > > .po files from WebSVN.
> > 
> > So you wrote another one instead of using an existing one? Why?
> 
> (a) I fell victim to NIH
> (b) The other projects' scripts were all specific for their
>     project, e.g. hardcoding names
> 
> True, there should be a generic solution applicable to all
> extragear projects, maybe centrally located such as in
> sysadmin/release-tools.
> 
> Maybe I'll find some time during the next days to contact some
> other extragear project maintainers to see if we can merge our
> approaches (same problem exists for tarball generation).

http://quickgit.kde.org/?p=releaseme.git

Cheers,
  Albert

> 
> Bye,
> Thomas

--nextPart1713203.WpCH4A3Bsd
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEABECAAYFAlSjIWoACgkQ/lREvmcCFhvl/QCgr+B/zkc2NC61VcMxh7Y9I75F
PK0AoJ8Dg/TFwgWA3Ra9A8iRyU9+TAXK
=ZRQ4
-----END PGP SIGNATURE-----

--nextPart1713203.WpCH4A3Bsd--