AW: kde-i18n-doc Digest, Vol 235, Issue 24

Fri Oct 14 12:54:41 BST 2022

Why not simply insert the Copyright and license text in header field with sed script for all corresponding files?

Am Freitag, Oktober 14, 2022, 1:00 PM schrieb kde-i18n-doc-request at kde.org:

Send kde-i18n-doc mailing list submissions to
    kde-i18n-doc at kde.org

To subscribe or unsubscribe via the World Wide Web, visit
    https://mail.kde.org/mailman/listinfo/kde-i18n-doc
or, via email, send a message with subject or body 'help' to
    kde-i18n-doc-request at kde.org

You can reach the person managing the list at
    kde-i18n-doc-owner at kde.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of kde-i18n-doc digest..."

Today's Topics:

  1. Re: reuse compliance and imported po/ (specifically for
      kde-inotify-survey) (Sveinn í Felli)

----------------------------------------------------------------------

Message: 1
Date: Fri, 14 Oct 2022 08:16:49 +0000
From: Sveinn í Felli <sv1 at fellsnet.is>
To: kde-i18n-doc at kde.org
Subject: Re: reuse compliance and imported po/ (specifically for
    kde-inotify-survey)
Message-ID: <7bedf6a6-02e7-5ceb-7110-e50632ea4bf2 at fellsnet.is>
Content-Type: text/plain; charset=UTF-8; format=flowed

I understand this as a call for translators, or rather the coordinators 
(those with SVN or GIT-access) to fill in the respective copyright and 
licence placeholders in PO-file headers.
This has to be done in a text-editor, so if people are using dedicated 
translation software (Lokalize, POEdit, etc.) they may overlook this.

OT: I think (maybe wrongly) that Lokalize can fill in some of this 
information, but only for new PO-files based on a POT-template; is there 
a way in Lokalize to edit the header?
Otherwise one has to close the file in Lokalize, edit it in a 
text-editor, close and then re-open in Lokalize. Quite a manouver..

Best,
Sveinn í Felli

Þann 14.10.2022 07:47, skrifaði "Iñigo Salvador Azurmendi":
> And this is a call for developers who create POT files, for transalators or for both?
> 
> 
> Cheers,
> Iñigo.
> 
> 
> 
> PS: Excuse my ignorance. Asking is the way to solve it.
> 
> 
> ----- Jatorrizko mezua -----
> Nork: Johnny Jazeix <jazeix at gmail.com>
> Data: 2022(e)ko Urriak 14(a), Ostirala, 9:17
> Gaia: Re: reuse compliance and imported po/ (specifically for kde-inotify-survey)
> Nori: xalba at clientes.euskaltel.es, KDE i18n-doc <kde-i18n-doc at kde.org>, Harald Sitter <sitter at kde.org>
> 
> 
>> Hi,
> 
> 
>> https://community.kde.org/Policies/Licensing_Policy for the reuse licence.
>> If I understand correctly, the first po files of the list do not have any copyright comment and all the po files do not have the licence indicated in the "reuse" format.
>> For the copyright:
> 
>> # Copyright (C) 2022 This_file_is_part_of_KDE
> 
>> or
> 
>> # SPDX-FileCopyrightText: 2022 This_file_is_part_of_KDE
> 
> 
>> For the licence:
> 
>> # SPDX-License-Identifier: LGPL-2.1-or-later
> 
> 
>> So together, the header of each po file should contain:
> 
>> # SPDX-FileCopyrightText: 2022 This_file_is_part_of_KDE
>> # SPDX-License-Identifier: LGPL-2.1-or-later
> 
> 
>> With the appropriate licence and dates.
> 
> 
>> Cheers,
> 
> 
>> Johnny
> 
> 
> 
>> Le ven. 14 oct. 2022 à 02:36, "Iñigo Salvador Azurmendi" <xalba at clientes.euskaltel.es> a écrit :
> 
>> Hello Harald,
>> could you explain this as if I don't understand what it is about, or point somewhere it is explained?
> 
> 
>> Thank you,
>> Iñigo.
> 
> 
> 
>> 22 # MISSING COPYRIGHT AND LICENSING INFORMATION
>> 23 The following files have no copyright and licensing information:
> 
> 
> 
> 
>> 30 The following files have no licensing information:
> 
> 
>> 47 # SUMMARY
>> 48 * Bad licenses:
>> 49 * Deprecated licenses:
>> 50 * Licenses without file extension:
>> 51 * Missing licenses:
>> 52 * Unused licenses:
>> 53 * Used licenses: BSD-3-Clause, CC0-1.0, FSFAP, GPL-2.0-only, GPL-3.0-only, LicenseRef-KDE-Accepted-GPL
>> 54 * Read errors: 0
>> 55 * Files with copyright information: 43 / 49
>> 56 * Files with license information: 27 / 49
>> 57 Unfortunately, your project is not compliant with version 3.0 of the REUSE Specification :-(
> 
> 
>> 59 Running after_script 00:01
>> 60 Running after script...
>> 61 $ echo
> 
> 
> 
>> 63 Cleaning up project directory and file based variables 00:03
> 
> 
>> 65 ERROR: Job failed: exit code 1
> 
> 
> 
> 
>> 37 * po/eu/kde-inotify-survey.po
> 
> 
> 
> 
> 
> 
> 
> 
>> ----- Jatorrizko mezua -----
>> Nork: Harald Sitter <sitter at kde.org>
>> Data: 2022(e)ko Urriak 13(a), Osteguna, 12:51
>> Gaia: reuse compliance and imported po/ (specifically for kde-inotify-survey)
>> Nori: KDE i18n-doc <kde-i18n-doc at kde.org>
> 
>>> Ahoy ahoy
>>>
>>> It'd be really lovely if everyone could sort out the licensing
>>> information in translations to establish reuse compliance. I now have
>>> my pipeline failing because ever so many translations are not
>>> compliant :(
>>>
>>> https://invent.kde.org/system/kde-inotify-survey/-/jobs/528415
>>>
>>> thx
>>> HS
> 

------------------------------

Subject: Digest Footer

_______________________________________________
kde-i18n-doc mailing list
kde-i18n-doc at kde.org
https://mail.kde.org/mailman/listinfo/kde-i18n-doc

------------------------------

End of kde-i18n-doc Digest, Vol 235, Issue 24
*********************************************

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-i18n-doc/attachments/20221014/8d032b3c/attachment.htm>