Send Koha-devel mailing list submissions to
    koha-devel@lists.koha-community.org

To subscribe or unsubscribe via the World Wide Web, visit
    https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
or, via email, send a message with subject or body 'help' to
    koha-devel-request@lists.koha-community.org

You can reach the person managing the list at
    koha-devel-owner@lists.koha-community.org

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


Today's Topics:

1. Re: Perl syntax for strings (Fridolin SOMERS)
2. Time to translate: string freeze to prepare Koha 20.05.13 has
begun (Victor Grousset/tuxayo)


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

Message: 1
Date: Wed, 16 Jun 2021 17:17:52 +0200
From: Fridolin SOMERS <fridolin.somers@biblibre.com>
To: koha-devel@lists.koha-community.org
Subject: Re: [Koha-devel] Perl syntax for strings
Message-ID: <cdbbb37f-4042-1e62-b79f-5351931f70cf@biblibre.com>
Content-Type: text/plain; charset=utf-8; format=flowed

OK so proposing to remove this space makes sens, great ;)

Also looks like Perl::Tidy does not remove the space.

Le 15/06/2021 à 11:00, Thomas Klausner a écrit :
> Hi!
>
> On Tue, Jun 15, 2021 at 10:19:12AM +0200, Fridolin SOMERS wrote:
>
>> I see in Perl code some cases where a string in written with a space between
>> q or qq or qw and string.
>> Like : qq /foo bar/ instead of qq/foo bar/
>
> While this works, it is strongly recommended to not use this "feature".
> It's main "use" is to use ANY string as quote-like operator:
>
> perl -E 'say qq A({/";A'
> ({/";
>
> But of course this is horrible and should not be used (outside of
> obfuscations..)
>
>> Most of cases are in :
>> use CGI qw ( -utf8 );
>
> This isn't even using the "feature" to allow any string..
>
>> There are only 29 other cases :
>> git grep -E ' q[qw]? [/({]' | grep -v 'use CGI qw '
>
> Of course this regex would fail to find why the space after q/qq/qw is
> allowed, because using the space you can use ANY char for the quote-like
> op. But I'm quite sure that nobody is crazy enough to put that into
> production code. And coming up with a regex that matches this would be
> quite hard... Though maybe there is a Perl::Critic rule for it?
>
>> Should we add a coding guideline ?
>> https://wiki.koha-community.org/wiki/Coding_Guidelines
>
> ++
>
> Greetings,
> domm
>

--
Fridolin SOMERS <fridolin.somers@biblibre.com>
Software and system maintainer 🦄
BibLibre, France


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

Message: 2
Date: Thu, 17 Jun 2021 00:14:11 +0200
From: Victor Grousset/tuxayo <victor@tuxayo.net>
To: koha-translate@lists.koha-community.org, koha-devel
    <koha-devel@lists.koha-community.org>, Koha <Koha@lists.katipo.co.nz>
Subject: [Koha-devel] Time to translate: string freeze to prepare Koha
    20.05.13 has begun
Message-ID: <d06c1393-8e79-54c7-3eb5-212018937d0f@tuxayo.net>
Content-Type: text/plain; charset=utf-8; format=flowed

Hi, saluton, hola, bonjour,

String freeze is into effect as of now for the 20.05.x maintenance branch.
The minor release is scheduled for around the 22th.

This means it's the right time to head over to the translation platform:
https://translate.koha-community.org/projects/

Reminder: if you add or change a translation in version 20.05,
then you must also copy it to 20.11 and 21.05.
Otherwise your work will be lost for future versions. (We've had a
recent significant case of that!)


Happy translating,

--
Victor Grousset/tuxayo


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

Subject: Digest Footer

_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/


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

End of Koha-devel Digest, Vol 187, Issue 13
*******************************************