<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body>A new request with request id 18521 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is : <br><br>Title : Koha-devel Digest, Vol 185, Issue 28<br>Category : <br>Description : <div>Send Koha-devel mailing list submissions to<br> koha-devel@lists.koha-community.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>or, via email, send a message with subject or body 'help' to<br> koha-devel-request@lists.koha-community.org<br><br>You can reach the person managing the list at<br> koha-devel-owner@lists.koha-community.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Koha-devel digest..."<br><br><br>Today's Topics:<br><br> 1. Re: Template::Toolkit and Translations (Julian Maurice)<br> 2. Release of Koha 20.11.05 (Fridolin SOMERS)<br> 3. Issue with bugzilla (Jonathan Druart)<br> 4. Re: Issue with bugzilla (Jonathan Druart)<br> 5. Release of Koha 20.05.11 (Andrew Fuerste-Henry)<br> 6. Koha 19.11.17 released (Victor Grousset/tuxayo)<br> 7. Re: Template::Toolkit and Translations (dcook@prosentient.com.au)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Mon, 26 Apr 2021 12:16:33 +0200<br>From: Julian Maurice <julian.maurice@biblibre.com><br>To: koha-devel@lists.koha-community.org<br>Subject: Re: [Koha-devel] Template::Toolkit and Translations<br>Message-ID: <971d191a-1353-e531-6366-f66ec1e817d6@biblibre.com><br>Content-Type: text/plain; charset=windows-1252; format=flowed<br><br>Hi David,<br><br>I think that language descriptions would be best in a Perl module, so <br>that they can be used everywhere (perl and templates).<br><br>For instance:<br><br>package Koha::Languages;<br>use Koha::I18N;<br>sub getLanguages {<br> return {<br> en => __('English'),<br> fr => __('French'),<br> }<br>}<br><br>And if the original description is needed, we can do the same but <br>without the __() translation.<br><br>sub getLanguagesDescriptionsInTheirOwnLanguage {<br> return {<br> en => 'English',<br> fr => 'Français',<br> }<br>}<br><br>Le 26/04/2021 à 02:44, dcook@prosentient.com.au a écrit :<br>> Hi all,<br>> <br>> While I mostly work in English, I occasionally do support libraries in <br>> other languages like French, Arabic, and Chinese. And more recently I’ve <br>> been looking at the Languages dropdown in the OPAC advanced search.<br>> <br>> In the templates, I notice that we often translate HTML, but what if we <br>> translated strings for a Template::Toolkit data structure instead?<br>> <br>> Consider the following:<br>> <br>> [% BLOCK en %]Anglais[% END %]<br>> <br>> [% BLOCK fr %]Français[% END %]<br>> <br>> [% langs.en = INCLUDE en %]<br>> <br>> [% langs.fr = INCLUDE fr %]<br>> <br>> I suppose it’s not very beautiful, but the translation process should be <br>> simple and in the end we have a re-usable hash map rather than static HTML.<br>> <br>> As I commented on Bug 12017 <br>> (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12017 <br>> <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12017>), we <br>> could have a database table of language codes with native language <br>> names, and then iterate through that and use the hash map of <br>> translations to provide the translations. Since we’re not producing <br>> HTML, we could flexibly reuse this language data in various different <br>> contexts. Whether it’s the Languages dropdown in the OPAC advanced <br>> search, the language selector, or whatever.<br>> <br>> We could probably use this concept in other places as well where we need <br>> translations but we don’t want to be bound to HTML.<br>> <br>> What do people think? I’m not wedded to the idea, but it’s something <br>> that crossed my mind this morning, when I looked at the large switch <br>> statements at <br>> https://bugs.koha-community.org/bugzilla3/page.cgi?id=splinter.html&bug=12017&attachment=40285 <br>> <https://bugs.koha-community.org/bugzilla3/page.cgi?id=splinter.html&bug=12017&attachment=40285>. <br>> <br>> <br>> (To that end, I would also suggest a theme-independent Template::Toolkit <br>> include directory, but that’s another story…)<br>> <br>> David Cook<br>> <br>> Software Engineer<br>> <br>> Prosentient Systems<br>> <br>> Suite 7.03<br>> <br>> 6a Glen St<br>> <br>> Milsons Point NSW 2061<br>> <br>> Australia<br>> <br>> Office: 02 9212 0899<br>> <br>> Online: 02 8005 0595<br>> <br>> <br>> _______________________________________________<br>> Koha-devel mailing list<br>> Koha-devel@lists.koha-community.org<br>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>> website : https://www.koha-community.org/<br>> git : https://git.koha-community.org/<br>> bugs : https://bugs.koha-community.org/<br>> <br><br>-- <br>Julian Maurice<br>BibLibre<br><br><br>------------------------------<br><br>Message: 2<br>Date: Mon, 26 Apr 2021 15:17:02 +0200<br>From: Fridolin SOMERS <fridolin.somers@biblibre.com><br>To: koha-devel <koha-devel@lists.koha-community.org>,<br> "koha@lists.katipo.co.nz" <koha@lists.katipo.co.nz><br>Subject: [Koha-devel] Release of Koha 20.11.05<br>Message-ID: <20b59c30-ee22-5e47-e64e-a7fc12b2bcb7@biblibre.com><br>Content-Type: text/plain; charset=utf-8; format=flowed<br><br>Hello everyone 🤗<br><br>The Koha community is proud to announce the release of Koha 20.11.05.<br><br>It is a maintenance release.<br><br>The full release notes are available here:<br>https://koha-community.org/koha-20-11-05-released/<br><br>Debian packages should be available in a few days.<br><br>Best regards 🤓<br><br>-- <br>Fridolin SOMERS <fridolin.somers@biblibre.com><br>Software and system maintainer 🦄<br>BibLibre, France<br><br><br>------------------------------<br><br>Message: 3<br>Date: Mon, 26 Apr 2021 15:35:46 +0200<br>From: Jonathan Druart <jonathan.druart@bugs.koha-community.org><br>To: koha-devel <koha-devel@lists.koha-community.org><br>Subject: [Koha-devel] Issue with bugzilla<br>Message-ID:<br> <CAJzKNY763eQ5vPuU3P_VP+YSh7G8i4m0AYjLUWcXwR4vPeVEuw@mail.gmail.com><br>Content-Type: text/plain; charset="UTF-8"<br><br>Hi all,<br><br>We are experiencing issues on bugzilla.<br>It seems that it is not possible to comment and search.<br>However you can search if you are logged out, and apply patches using git-bz.<br><br>The issue will certainly not be fixed until tomorrow.<br><br>Cheers,<br>Jonathan<br><br><br>------------------------------<br><br>Message: 4<br>Date: Mon, 26 Apr 2021 16:13:54 +0200<br>From: Jonathan Druart <jonathan.druart@bugs.koha-community.org><br>To: koha-devel <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] Issue with bugzilla<br>Message-ID:<br> <CAJzKNY5enK9xsJeV8Gs+XbkAyGSYS9_8dcDLFaGUtkeerA=r_A@mail.gmail.com><br>Content-Type: text/plain; charset="UTF-8"<br><br>The problem is fixed now, thanks Galen!<br><br>Le lun. 26 avr. 2021 à 15:35, Jonathan Druart<br><jonathan.druart@bugs.koha-community.org> a écrit :<br>><br>> Hi all,<br>><br>> We are experiencing issues on bugzilla.<br>> It seems that it is not possible to comment and search.<br>> However you can search if you are logged out, and apply patches using git-bz.<br>><br>> The issue will certainly not be fixed until tomorrow.<br>><br>> Cheers,<br>> Jonathan<br><br><br>------------------------------<br><br>Message: 5<br>Date: Mon, 26 Apr 2021 15:19:21 -0500<br>From: Andrew Fuerste-Henry <andrew@bywatersolutions.com><br>To: koha-devel <koha-devel@lists.koha-community.org><br>Subject: [Koha-devel] Release of Koha 20.05.11<br>Message-ID:<br> <CANGX5DwsqOt7vYVxdvJtgxH_1MA9Q9SWgk1qLj36nGjgs2Njbg@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>Hi all!<br>We're proud to announce the release of Koha 20.05.11. This is a maintenance<br>release.<br><br>Full release notes can be found here:<br>https://koha-community.org/koha-20-05-11-released/<br><br>Debian packages should be available in a few days.<br>Thank you!<br>-- <br>Andrew Fuerste-Henry<br>Educator<br>(he/him/his)<br>ByWater Solutions<br>bywatersolutions.com<br>Phone:(888)900-8944 <(888)%20900-8944><br><br>What is Koha? <http://bywatersolutions.com/what-is-koha/><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20210426/6ade74e6/attachment-0001.htm><br><br>------------------------------<br><br>Message: 6<br>Date: Mon, 26 Apr 2021 23:46:04 +0200<br>From: Victor Grousset/tuxayo <victor@tuxayo.net><br>To: Koha@lists.katipo.co.nz, koha-devel<br> <koha-devel@lists.koha-community.org><br>Subject: [Koha-devel] Koha 19.11.17 released<br>Message-ID: <60abd1be-731d-d5ca-2762-7556ed7a9984@tuxayo.net><br>Content-Type: text/plain; charset=utf-8; format=flowed<br><br>Hello!<br><br>The Koha Community is happy to announce the release of Koha 19.11.17<br><br>The full release notes can be found at:<br>https://koha-community.org/koha-19-11-17-released/<br><br>Debian packages should be available shortly.<br><br>Thanks to everyone involved :)<br><br><br>Cheers,<br><br>-- <br>Victor Grousset/tuxayo<br><br><br>------------------------------<br><br>Message: 7<br>Date: Tue, 27 Apr 2021 09:44:47 +1000<br>From: <dcook@prosentient.com.au><br>To: "'Julian Maurice'" <julian.maurice@biblibre.com>,<br> <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] Template::Toolkit and Translations<br>Message-ID: <032601d73af6$24a6b570$6df42050$@prosentient.com.au><br>Content-Type: text/plain; charset="utf-8"<br><br>Hi Julian,<br><br>I like part of what you've suggested here. I still think that putting languages (with codes and name in native text) in the database is a good idea, as it allows the ability to add languages to Koha without a code change. Unless Koha is going to be perfectly comprehensive with languages, I think that libraries need to be able to add their own languages to the database.<br><br>But I'd be fine with putting the translations of languages into Perl rather than Template::Toolkit. <br><br>I've found the barrier to entry for Koha translations to be too high, so I can't keep track of all the different _(), __(), _t(), etc functions across the different file types, but if your suggestion for Koha::Languages works using that __() syntax, then I'm fine with it. <br><br>David Cook<br>Software Engineer<br>Prosentient Systems<br>Suite 7.03<br>6a Glen St<br>Milsons Point NSW 2061<br>Australia<br><br>Office: 02 9212 0899<br>Online: 02 8005 0595<br><br>-----Original Message-----<br>From: Koha-devel <koha-devel-bounces@lists.koha-community.org> On Behalf Of Julian Maurice<br>Sent: Monday, 26 April 2021 8:17 PM<br>To: koha-devel@lists.koha-community.org<br>Subject: Re: [Koha-devel] Template::Toolkit and Translations<br><br>Hi David,<br><br>I think that language descriptions would be best in a Perl module, so that they can be used everywhere (perl and templates).<br><br>For instance:<br><br>package Koha::Languages;<br>use Koha::I18N;<br>sub getLanguages {<br> return {<br> en => __('English'),<br> fr => __('French'),<br> }<br>}<br><br>And if the original description is needed, we can do the same but without the __() translation.<br><br>sub getLanguagesDescriptionsInTheirOwnLanguage {<br> return {<br> en => 'English',<br> fr => 'Français',<br> }<br>}<br><br>Le 26/04/2021 à 02:44, dcook@prosentient.com.au a écrit :<br>> Hi all,<br>> <br>> While I mostly work in English, I occasionally do support libraries in <br>> other languages like French, Arabic, and Chinese. And more recently <br>> I’ve been looking at the Languages dropdown in the OPAC advanced search.<br>> <br>> In the templates, I notice that we often translate HTML, but what if <br>> we translated strings for a Template::Toolkit data structure instead?<br>> <br>> Consider the following:<br>> <br>> [% BLOCK en %]Anglais[% END %]<br>> <br>> [% BLOCK fr %]Français[% END %]<br>> <br>> [% langs.en = INCLUDE en %]<br>> <br>> [% langs.fr = INCLUDE fr %]<br>> <br>> I suppose it’s not very beautiful, but the translation process should <br>> be simple and in the end we have a re-usable hash map rather than static HTML.<br>> <br>> As I commented on Bug 12017<br>> (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12017<br>> <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12017>), we <br>> could have a database table of language codes with native language <br>> names, and then iterate through that and use the hash map of <br>> translations to provide the translations. Since we’re not producing <br>> HTML, we could flexibly reuse this language data in various different <br>> contexts. Whether it’s the Languages dropdown in the OPAC advanced <br>> search, the language selector, or whatever.<br>> <br>> We could probably use this concept in other places as well where we <br>> need translations but we don’t want to be bound to HTML.<br>> <br>> What do people think? I’m not wedded to the idea, but it’s something <br>> that crossed my mind this morning, when I looked at the large switch <br>> statements at<br>> https://bugs.koha-community.org/bugzilla3/page.cgi?id=splinter.html&bu<br>> g=12017&attachment=40285 <br>> <https://bugs.koha-community.org/bugzilla3/page.cgi?id=splinter.html&bug=12017&attachment=40285>.<br>> <br>> <br>> (To that end, I would also suggest a theme-independent <br>> Template::Toolkit include directory, but that’s another story…)<br>> <br>> David Cook<br>> <br>> Software Engineer<br>> <br>> Prosentient Systems<br>> <br>> Suite 7.03<br>> <br>> 6a Glen St<br>> <br>> Milsons Point NSW 2061<br>> <br>> Australia<br>> <br>> Office: 02 9212 0899<br>> <br>> Online: 02 8005 0595<br>> <br>> <br>> _______________________________________________<br>> Koha-devel mailing list<br>> Koha-devel@lists.koha-community.org<br>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>> website : https://www.koha-community.org/ git : <br>> https://git.koha-community.org/ bugs : <br>> https://bugs.koha-community.org/<br>> <br><br>--<br>Julian Maurice<br>BibLibre<br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org<br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/ git : https://git.koha-community.org/ bugs : https://bugs.koha-community.org/<br><br><br><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org<br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/<br>git : https://git.koha-community.org/<br>bugs : https://bugs.koha-community.org/<br><br><br>------------------------------<br><br>End of Koha-devel Digest, Vol 185, Issue 28<br>*******************************************<br></div><br><br>NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.<br></body></html>