From kde-i18n-doc  Sun Jan 06 12:23:30 2019
From: Pino Toscano <pino () kde ! org>
Date: Sun, 06 Jan 2019 12:23:30 +0000
To: kde-i18n-doc
Subject: Re: Translation files for QtCurve not being packaged
Message-Id: <2823158.XJf3zVuKBN () pendragon>
X-MARC-Message: https://marc.info/?l=kde-i18n-doc&m=154677743510039
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart7036519.3r2IXNpygR"

--nextPart7036519.3r2IXNpygR
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"

In data domenica 6 gennaio 2019 13:03:48 CET, Karl Ove Hufthammer ha scritt=
o:
> I noticed that the widget style QtCurve doesn=E2=80=99t include any trans=
lations=20
> in my distro (openSUSE Tumbleweed), even though there is a (large, 788=20
> strings) translation file in SVN (extragear-base in both stable-kf5 and=20
> trunk-kf5).

They are shipped in the release tarballs:
https://download.kde.org/stable/qtcurve/

> It turns  out that the QtCurve release files=20
> (https://github.com/KDE/qtcurve/releases) don=E2=80=99t actually contain =
any of=20
> the translation files people have been creating.

They are not releases, they are just autogenerated tarballs from the
git tags. Do not use them as the primary source of releases, just like
happens with Applications, Plasma, extragear, etc.

> So the distros don=E2=80=99t have any translations to package.

The Debian packaging of qtcurve now uses the release tarballs, so it
has translations.

> Can someone please fix this?

Report a bug to openSUSE, asking them to use only release tarballs
instead of tracking git tags.

=2D-=20
Pino Toscano
--nextPart7036519.3r2IXNpygR
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQQ1ubO/s+l2X9kOMCJM0famIH8vegUCXDHzQgAKCRBM0famIH8v
eqmAAKCgu9E0od5IcVVCtM+/VfKVyTjQbQCfXfPuej7u+dTBr1KwAF1n5adfdDI=
=/6hO
-----END PGP SIGNATURE-----

--nextPart7036519.3r2IXNpygR--