<html xmlns="http://www.w3.org/1999/xhtml" xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office"><head><!--[if gte mso 9]><xml><o:OfficeDocumentSettings><o:AllowPNG/><o:PixelsPerInch>96</o:PixelsPerInch></o:OfficeDocumentSettings></xml><![endif]--></head><body>
<br><br>Why not simply insert the Copyright and license text in header field with sed script for all corresponding files?<br><br><p class="yahoo-quoted-begin" style="font-size: 15px; color: #715FFA; padding-top: 15px; margin-top: 0">Am Freitag, Oktober 14, 2022, 1:00 PM schrieb kde-i18n-doc-request@kde.org:</p><blockquote class="iosymail"><div dir="ltr">Send kde-i18n-doc mailing list submissions to<br></div><div dir="ltr"> <a ymailto="mailto:kde-i18n-doc@kde.org" href="mailto:kde-i18n-doc@kde.org">kde-i18n-doc@kde.org</a><br></div><div dir="ltr"><br></div><div dir="ltr">To subscribe or unsubscribe via the World Wide Web, visit<br></div><div dir="ltr"> <a href="https://mail.kde.org/mailman/listinfo/kde-i18n-doc" target="_blank">https://mail.kde.org/mailman/listinfo/kde-i18n-doc</a><br></div><div dir="ltr">or, via email, send a message with subject or body 'help' to<br></div><div dir="ltr"> <a ymailto="mailto:kde-i18n-doc-request@kde.org" href="mailto:kde-i18n-doc-request@kde.org">kde-i18n-doc-request@kde.org</a><br></div><div dir="ltr"><br></div><div dir="ltr">You can reach the person managing the list at<br></div><div dir="ltr"> <a ymailto="mailto:kde-i18n-doc-owner@kde.org" href="mailto:kde-i18n-doc-owner@kde.org">kde-i18n-doc-owner@kde.org</a><br></div><div dir="ltr"><br></div><div dir="ltr">When replying, please edit your Subject line so it is more specific<br></div><div dir="ltr">than "Re: Contents of kde-i18n-doc digest..."<br></div><div dir="ltr"><br></div><div dir="ltr"><br></div><div dir="ltr">Today's Topics:<br></div><div dir="ltr"><br></div><div dir="ltr"> 1. Re: reuse compliance and imported po/ (specifically for<br></div><div dir="ltr"> kde-inotify-survey) (Sveinn í Felli)<br></div><div dir="ltr"><br></div><div dir="ltr"><br></div><div dir="ltr">----------------------------------------------------------------------<br></div><div dir="ltr"><br></div><div dir="ltr">Message: 1<br></div><div dir="ltr">Date: Fri, 14 Oct 2022 08:16:49 +0000<br></div><div dir="ltr">From: Sveinn í Felli <<a ymailto="mailto:sv1@fellsnet.is" href="mailto:sv1@fellsnet.is">sv1@fellsnet.is</a>><br></div><div dir="ltr">To: <a ymailto="mailto:kde-i18n-doc@kde.org" href="mailto:kde-i18n-doc@kde.org">kde-i18n-doc@kde.org</a><br></div><div dir="ltr">Subject: Re: reuse compliance and imported po/ (specifically for<br></div><div dir="ltr"> kde-inotify-survey)<br></div><div dir="ltr">Message-ID: <<a ymailto="mailto:7bedf6a6-02e7-5ceb-7110-e50632ea4bf2@fellsnet.is" href="mailto:7bedf6a6-02e7-5ceb-7110-e50632ea4bf2@fellsnet.is">7bedf6a6-02e7-5ceb-7110-e50632ea4bf2@fellsnet.is</a>><br></div><div dir="ltr">Content-Type: text/plain; charset=UTF-8; format=flowed<br></div><div dir="ltr"><br></div><div dir="ltr">I understand this as a call for translators, or rather the coordinators <br></div><div dir="ltr">(those with SVN or GIT-access) to fill in the respective copyright and <br></div><div dir="ltr">licence placeholders in PO-file headers.<br></div><div dir="ltr">This has to be done in a text-editor, so if people are using dedicated <br></div><div dir="ltr">translation software (Lokalize, POEdit, etc.) they may overlook this.<br></div><div dir="ltr"><br></div><div dir="ltr">OT: I think (maybe wrongly) that Lokalize can fill in some of this <br></div><div dir="ltr">information, but only for new PO-files based on a POT-template; is there <br></div><div dir="ltr">a way in Lokalize to edit the header?<br></div><div dir="ltr">Otherwise one has to close the file in Lokalize, edit it in a <br></div><div dir="ltr">text-editor, close and then re-open in Lokalize. Quite a manouver..<br></div><div dir="ltr"><br></div><div dir="ltr">Best,<br></div><div dir="ltr">Sveinn í Felli<br></div><div dir="ltr"><br></div><div dir="ltr">Þann 14.10.2022 07:47, skrifaði "Iñigo Salvador Azurmendi":<br></div><div dir="ltr">> And this is a call for developers who create POT files, for transalators or for both?<br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">> Cheers,<br></div><div dir="ltr">> Iñigo.<br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">> PS: Excuse my ignorance. Asking is the way to solve it.<br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">> ----- Jatorrizko mezua -----<br></div><div dir="ltr">> Nork: Johnny Jazeix <<a ymailto="mailto:jazeix@gmail.com" href="mailto:jazeix@gmail.com">jazeix@gmail.com</a>><br></div><div dir="ltr">> Data: 2022(e)ko Urriak 14(a), Ostirala, 9:17<br></div><div dir="ltr">> Gaia: Re: reuse compliance and imported po/ (specifically for kde-inotify-survey)<br></div><div dir="ltr">> Nori: <a ymailto="mailto:xalba@clientes.euskaltel.es" href="mailto:xalba@clientes.euskaltel.es">xalba@clientes.euskaltel.es</a>, KDE i18n-doc <<a ymailto="mailto:kde-i18n-doc@kde.org" href="mailto:kde-i18n-doc@kde.org">kde-i18n-doc@kde.org</a>>, Harald Sitter <<a ymailto="mailto:sitter@kde.org" href="mailto:sitter@kde.org">sitter@kde.org</a>><br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">>> Hi,<br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">>> <a href="https://community.kde.org/Policies/Licensing_Policy " target="_blank">https://community.kde.org/Policies/Licensing_Policy </a>for the reuse licence.<br></div><div dir="ltr">>> 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.<br></div><div dir="ltr">>> For the copyright:<br></div><div dir="ltr">> <br></div><div dir="ltr">>> # Copyright (C) 2022 This_file_is_part_of_KDE<br></div><div dir="ltr">> <br></div><div dir="ltr">>> or<br></div><div dir="ltr">> <br></div><div dir="ltr">>> # SPDX-FileCopyrightText: 2022 This_file_is_part_of_KDE<br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">>> For the licence:<br></div><div dir="ltr">> <br></div><div dir="ltr">>> # SPDX-License-Identifier: LGPL-2.1-or-later<br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">>> So together, the header of each po file should contain:<br></div><div dir="ltr">> <br></div><div dir="ltr">>> # SPDX-FileCopyrightText: 2022 This_file_is_part_of_KDE<br></div><div dir="ltr">>> # SPDX-License-Identifier: LGPL-2.1-or-later<br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">>> With the appropriate licence and dates.<br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">>> Cheers,<br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">>> Johnny<br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">>> Le ven. 14 oct. 2022 à 02:36, "Iñigo Salvador Azurmendi" <<a ymailto="mailto:xalba@clientes.euskaltel.es" href="mailto:xalba@clientes.euskaltel.es">xalba@clientes.euskaltel.es</a>> a écrit :<br></div><div dir="ltr">> <br></div><div dir="ltr">>> Hello Harald,<br></div><div dir="ltr">>> could you explain this as if I don't understand what it is about, or point somewhere it is explained?<br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">>> Thank you,<br></div><div dir="ltr">>> Iñigo.<br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">>> 22 # MISSING COPYRIGHT AND LICENSING INFORMATION<br></div><div dir="ltr">>> 23 The following files have no copyright and licensing information:<br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">>> 30 The following files have no licensing information:<br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">>> 47 # SUMMARY<br></div><div dir="ltr">>> 48 * Bad licenses:<br></div><div dir="ltr">>> 49 * Deprecated licenses:<br></div><div dir="ltr">>> 50 * Licenses without file extension:<br></div><div dir="ltr">>> 51 * Missing licenses:<br></div><div dir="ltr">>> 52 * Unused licenses:<br></div><div dir="ltr">>> 53 * Used licenses: BSD-3-Clause, CC0-1.0, FSFAP, GPL-2.0-only, GPL-3.0-only, LicenseRef-KDE-Accepted-GPL<br></div><div dir="ltr">>> 54 * Read errors: 0<br></div><div dir="ltr">>> 55 * Files with copyright information: 43 / 49<br></div><div dir="ltr">>> 56 * Files with license information: 27 / 49<br></div><div dir="ltr">>> 57 Unfortunately, your project is not compliant with version 3.0 of the REUSE Specification :-(<br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">>> 59 Running after_script 00:01<br></div><div dir="ltr">>> 60 Running after script...<br></div><div dir="ltr">>> 61 $ echo<br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">>> 63 Cleaning up project directory and file based variables 00:03<br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">>> 65 ERROR: Job failed: exit code 1<br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">>> 37 * po/eu/kde-inotify-survey.po<br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">>> ----- Jatorrizko mezua -----<br></div><div dir="ltr">>> Nork: Harald Sitter <<a ymailto="mailto:sitter@kde.org" href="mailto:sitter@kde.org">sitter@kde.org</a>><br></div><div dir="ltr">>> Data: 2022(e)ko Urriak 13(a), Osteguna, 12:51<br></div><div dir="ltr">>> Gaia: reuse compliance and imported po/ (specifically for kde-inotify-survey)<br></div><div dir="ltr">>> Nori: KDE i18n-doc <<a ymailto="mailto:kde-i18n-doc@kde.org" href="mailto:kde-i18n-doc@kde.org">kde-i18n-doc@kde.org</a>><br></div><div dir="ltr">> <br></div><div dir="ltr">>>> Ahoy ahoy<br></div><div dir="ltr">>>><br></div><div dir="ltr">>>> It'd be really lovely if everyone could sort out the licensing<br></div><div dir="ltr">>>> information in translations to establish reuse compliance. I now have<br></div><div dir="ltr">>>> my pipeline failing because ever so many translations are not<br></div><div dir="ltr">>>> compliant :(<br></div><div dir="ltr">>>><br></div><div dir="ltr">>>> <a href="https://invent.kde.org/system/kde-inotify-survey/-/jobs/528415" target="_blank">https://invent.kde.org/system/kde-inotify-survey/-/jobs/528415</a><br></div><div dir="ltr">>>><br></div><div dir="ltr">>>> thx<br></div><div dir="ltr">>>> HS<br></div><div dir="ltr">> <br></div><div dir="ltr"><br></div><div dir="ltr"><br></div><div dir="ltr"><br></div><div dir="ltr">------------------------------<br></div><div dir="ltr"><br></div><div dir="ltr">Subject: Digest Footer<br></div><div dir="ltr"><br></div><div dir="ltr">_______________________________________________<br></div><div dir="ltr">kde-i18n-doc mailing list<br></div><div dir="ltr"><a ymailto="mailto:kde-i18n-doc@kde.org" href="mailto:kde-i18n-doc@kde.org">kde-i18n-doc@kde.org</a><br></div><div dir="ltr"><a href="https://mail.kde.org/mailman/listinfo/kde-i18n-doc" target="_blank">https://mail.kde.org/mailman/listinfo/kde-i18n-doc</a><br></div><div dir="ltr"><br></div><div dir="ltr"><br></div><div dir="ltr">------------------------------<br></div><div dir="ltr"><br></div><div dir="ltr">End of kde-i18n-doc Digest, Vol 235, Issue 24<br></div><div dir="ltr">*********************************************<br></div><blockquote></blockquote></blockquote>
</body></html>