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

[Johnny Jazeix]

Yes, if each maintainer can do a sed, it should do the work.

Another question is what licence should we use for po files? According to
the wiki page (https://community.kde.org/Policies/Licensing_Policy):
Translations of text from the files described in section 4 must be licenced
under one of the terms in sections 4.
And section 4 is:
* LGPL-2.1-only OR LGPL-3.0-only OR LicenseRef-KDE-Accepted-LGPL: LGPL
version 2.1, or version 3 or later versions approved by the membership of
KDE e.V.
* LGPL-2.1-or-later: LGPL version 2.1 or later
* BSD-2-Clause: BSD License as listed below.
* MIT: MIT license as listed below.
* X11: X11 license as listed below.

Is it up to the translation teams to decide?

Cheers,

Johnny


Le ven. 14 oct. 2022 à 13:55, Mincho Kondarev <mkondarev at yahoo.de> a écrit :

>
>
> 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
> :
>
>
>   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
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-i18n-doc/attachments/20221014/cdf7f922/attachment-0001.htm>