Re: kwatchgnupg usage of U+2029 when saving the log

Ingo Klöcker <[email protected]> Fri, 14 Jun 2024 12:40:02 +0200
Newsgroups gmane.comp.kde.devel.pim
Message-ID <2614274.Lt9SDvczpP@daneel>
--nextPart4357028.ejJDZkT8p0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"; protected-headers="v1"
From: Ingo =?ISO-8859-1?Q?Kl=F6cker?= <[email protected]>
To: [email protected]
Subject: Re: kwatchgnupg usage of U+2029 when saving the log
Date: Fri, 14 Jun 2024 12:40:02 +0200
Message-ID: <2614274.Lt9SDvczpP@daneel>
In-Reply-To: <[email protected]>
References: <[email protected]>
MIME-Version: 1.0

On Freitag, 14. Juni 2024 11:58:44 CEST Marco Moock wrote:
> I use kleopatra 4:22.12.3-2+b2
> on Debian sid.
> 
> I noticed that when I export the log in kwatchgnupg, it doesn't use
> normal line break (LF or CRLF), it uses U+2029.
> 
> vim, less and other tools don't recognize it, so it will be one very
> long line.
> 
> Is that intended?

No, it's not. I have fixed this for the next 24.05 patch release.

Regards,
Ingo

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

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

iHUEABYKAB0WIQTbjgIOMowwlCBgvyGxb1mVFkdKugUCZmweAgAKCRCxb1mVFkdK
ug9QAQD4YLH2tc4QzbN84XFajyf267HqHMytkuaA0j2/CFUYIgEA7Oli7YP4CAAX
cGqqjFMJZHiXJXBp7tahPln+J20i1gQ=
=CkH3
-----END PGP SIGNATURE-----

--nextPart4357028.ejJDZkT8p0--