From karl at huftis.org  Sun Jul  7 06:52:49 2024
From: karl at huftis.org (Karl Ove Hufthammer)
Date: Sun, 7 Jul 2024 15:52:49 +0200
Subject: [pology] Support for SPDX-FileCopyrightText in Pology
Message-ID: <0b7088ed-29a2-49cf-a813-a8bbfc5044e0@huftis.org>

Here?s the TLDR version:
Pology doesn?t support ?SPDX-FileCopyrightText? headers, which Lokalize 
uses. It would be nice if it did.

Long version:

For some time, Lokalize has been writing author contribution information 
using ?SPDX-FileCopyrightText? comments in the PO header, e.g.

 ??? # SPDX-FileCopyrightText: 2023, 2024 Nomen Nescio <nomen at example.com>

instead of the old-style

 ??? # Nomen Nescio <nomen at example.com>, 2023, 2024.

However, Pology currently doesn?t support this. That is, it treats the 
?SPDX-FileCopyrightText? line as a normal ?comment? field instead of
as an ?author? field.

One result is that the ?normalize-header? sieve doesn?t normalize the 
author information, i.e., it completeley ignores the 
?SPDX-FileCopyrightText? lines.

I discovered the problem by noticing that posummit had for some time 
automatically been *removing* my author information (but not that of 
others, using the old-style format) from files I have been updating. I 
was really to blame, because I had set up to my posummit scripts to 
automatically clear any ?comment? fields (but not ?title? or ?author? 
fields), as they generally don?t contain any useful information for 
*our* translations, only ?noise?. This was working well before, but not 
after Lokalize started writing ?SPDX-FileCopyrightText? headers and 
converting old-style author information to the new format. (Note that it 
only does this for the *current* translator, not for the others.)

So this is a request for supporting the new ?SPDX-FileCopyrightText? 
format. This is what I think should happen:

 1. ?SPDX-FileCopyrightText? lines should be treated as ?author? fields
    instead of ?comment? fields.
 2. The ?normalize-header? sieve should (by default or as an option)
    output the author list using the new format.


-- 
Karl Ove Hufthammer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nedohodnik.net/pipermail/pology-nedohodnik.net/attachments/20240707/a8187339/attachment.htm>

From pere at hungry.com  Tue Jul 23 23:44:24 2024
From: pere at hungry.com (Petter Reinholdtsen)
Date: Wed, 24 Jul 2024 08:44:24 +0200
Subject: [pology] Current latest upstream edition of pology?
Message-ID: <sa6zfq7gugn.fsf@hjemme.reinholdtsen.name>


Hi.

I was looking for the latest edition of pology, and discovered both
<URL: https://invent.kde.org/sdk/pology > and
<URL: https://github.com/KDE/pology >.  Are these the same code base?
Which one is the preferred upstream source for pology?

I was planning to use pomtrans to convert a nb PO file a nn PO file
draft, and ran into problems, so I thought it would be best to test the
latest edition.


Is there any interest in having pology included in Debian?  If someone
is willing to maintain it, I would be happy to sponsor the uploads.
<URL: https://bugs.debian.org/831441 > is the request for a Debian
package, and <URL: http://www.hungry.com/~pere/debian-sponsoring.html >
is my references for signing other peoples packages into Debian.

-- 
Happy hacking
Petter Reinholdtsen

From karl at huftis.org  Sun Jul 28 08:00:25 2024
From: karl at huftis.org (Karl Ove Hufthammer)
Date: Sun, 28 Jul 2024 17:00:25 +0200
Subject: [pology] Current latest upstream edition of pology?
In-Reply-To: <sa6zfq7gugn.fsf@hjemme.reinholdtsen.name>
References: <sa6zfq7gugn.fsf@hjemme.reinholdtsen.name>
Message-ID: <abbba582-c656-4182-99b9-91b9b6b0d0fd@huftis.org>

Petter Reinholdtsen skreiv 24.07.2024 08:44:
> I was looking for the latest edition of pology, and discovered both
> <URL:https://invent.kde.org/sdk/pology  > and
> <URL:https://github.com/KDE/pology  >.  Are these the same code base?
> Which one is the preferred upstream source for pology?

https://github.com/KDE is an official read-only mirror. The repository 
at invent.kde.org is the preferred upstream source. See 
https://community.kde.org/Infrastructure/Git/GitHub_Mirror for mor 
information.


-- 
Karl Ove Hufthammer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nedohodnik.net/pipermail/pology-nedohodnik.net/attachments/20240728/7db320cd/attachment.htm>