A new request with request id 18521 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is :

Title : Koha-devel Digest, Vol 185, Issue 28
Category :
Description :
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: Template::Toolkit and Translations (Julian Maurice)
2. Release of Koha 20.11.05 (Fridolin SOMERS)
3. Issue with bugzilla (Jonathan Druart)
4. Re: Issue with bugzilla (Jonathan Druart)
5. Release of Koha 20.05.11 (Andrew Fuerste-Henry)
6. Koha 19.11.17 released (Victor Grousset/tuxayo)
7. Re: Template::Toolkit and Translations (dcook@prosentient.com.au)


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

Message: 1
Date: Mon, 26 Apr 2021 12:16:33 +0200
From: Julian Maurice <julian.maurice@biblibre.com>
To: koha-devel@lists.koha-community.org
Subject: Re: [Koha-devel] Template::Toolkit and Translations
Message-ID: <971d191a-1353-e531-6366-f66ec1e817d6@biblibre.com>
Content-Type: text/plain; charset=windows-1252; format=flowed

Hi David,

I think that language descriptions would be best in a Perl module, so
that they can be used everywhere (perl and templates).

For instance:

package Koha::Languages;
use Koha::I18N;
sub getLanguages {
return {
en => __('English'),
fr => __('French'),
}
}

And if the original description is needed, we can do the same but
without the __() translation.

sub getLanguagesDescriptionsInTheirOwnLanguage {
return {
en => 'English',
fr => 'Français',
}
}

Le 26/04/2021 à 02:44, dcook@prosentient.com.au a écrit :
> Hi all,
>
> While I mostly work in English, I occasionally do support libraries in
> other languages like French, Arabic, and Chinese. And more recently I’ve
> been looking at the Languages dropdown in the OPAC advanced search.
>
> In the templates, I notice that we often translate HTML, but what if we
> translated strings for a Template::Toolkit data structure instead?
>
> Consider the following:
>
> [% BLOCK en %]Anglais[% END %]
>
> [% BLOCK fr %]Français[% END %]
>
> [% langs.en = INCLUDE en %]
>
> [% langs.fr = INCLUDE fr %]
>
> I suppose it’s not very beautiful, but the translation process should be
> simple and in the end we have a re-usable hash map rather than static HTML.
>
> As I commented on Bug 12017
> (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12017
> <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12017>), we
> could have a database table of language codes with native language
> names, and then iterate through that and use the hash map of
> translations to provide the translations. Since we’re not producing
> HTML, we could flexibly reuse this language data in various different
> contexts. Whether it’s the Languages dropdown in the OPAC advanced
> search, the language selector, or whatever.
>
> We could probably use this concept in other places as well where we need
> translations but we don’t want to be bound to HTML.
>
> What do people think? I’m not wedded to the idea, but it’s something
> that crossed my mind this morning, when I looked at the large switch
> statements at
> https://bugs.koha-community.org/bugzilla3/page.cgi?id=splinter.html&bug=12017&attachment=40285
> <https://bugs.koha-community.org/bugzilla3/page.cgi?id=splinter.html&bug=12017&attachment=40285>.
>
>
> (To that end, I would also suggest a theme-independent Template::Toolkit
> include directory, but that’s another story…)
>
> David Cook
>
> Software Engineer
>
> Prosentient Systems
>
> Suite 7.03
>
> 6a Glen St
>
> Milsons Point NSW 2061
>
> Australia
>
> Office: 02 9212 0899
>
> Online: 02 8005 0595
>
>
> _______________________________________________
> 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/
>

--
Julian Maurice
BibLibre


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

Message: 2
Date: Mon, 26 Apr 2021 15:17:02 +0200
From: Fridolin SOMERS <fridolin.somers@biblibre.com>
To: koha-devel <koha-devel@lists.koha-community.org>,
    "koha@lists.katipo.co.nz" <koha@lists.katipo.co.nz>
Subject: [Koha-devel] Release of Koha 20.11.05
Message-ID: <20b59c30-ee22-5e47-e64e-a7fc12b2bcb7@biblibre.com>
Content-Type: text/plain; charset=utf-8; format=flowed

Hello everyone 🤗

The Koha community is proud to announce the release of Koha 20.11.05.

It is a maintenance release.

The full release notes are available here:
https://koha-community.org/koha-20-11-05-released/

Debian packages should be available in a few days.

Best regards 🤓

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


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

Message: 3
Date: Mon, 26 Apr 2021 15:35:46 +0200
From: Jonathan Druart <jonathan.druart@bugs.koha-community.org>
To: koha-devel <koha-devel@lists.koha-community.org>
Subject: [Koha-devel] Issue with bugzilla
Message-ID:
    <CAJzKNY763eQ5vPuU3P_VP+YSh7G8i4m0AYjLUWcXwR4vPeVEuw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

Hi all,

We are experiencing issues on bugzilla.
It seems that it is not possible to comment and search.
However you can search if you are logged out, and apply patches using git-bz.

The issue will certainly not be fixed until tomorrow.

Cheers,
Jonathan


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

Message: 4
Date: Mon, 26 Apr 2021 16:13:54 +0200
From: Jonathan Druart <jonathan.druart@bugs.koha-community.org>
To: koha-devel <koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] Issue with bugzilla
Message-ID:
    <CAJzKNY5enK9xsJeV8Gs+XbkAyGSYS9_8dcDLFaGUtkeerA=r_A@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

The problem is fixed now, thanks Galen!

Le lun. 26 avr. 2021 à 15:35, Jonathan Druart
<jonathan.druart@bugs.koha-community.org> a écrit :
>
> Hi all,
>
> We are experiencing issues on bugzilla.
> It seems that it is not possible to comment and search.
> However you can search if you are logged out, and apply patches using git-bz.
>
> The issue will certainly not be fixed until tomorrow.
>
> Cheers,
> Jonathan


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

Message: 5
Date: Mon, 26 Apr 2021 15:19:21 -0500
From: Andrew Fuerste-Henry <andrew@bywatersolutions.com>
To: koha-devel <koha-devel@lists.koha-community.org>
Subject: [Koha-devel] Release of Koha 20.05.11
Message-ID:
    <CANGX5DwsqOt7vYVxdvJtgxH_1MA9Q9SWgk1qLj36nGjgs2Njbg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi all!
We're proud to announce the release of Koha 20.05.11. This is a maintenance
release.

Full release notes can be found here:
https://koha-community.org/koha-20-05-11-released/

Debian packages should be available in a few days.
Thank you!
--
Andrew Fuerste-Henry
Educator
(he/him/his)
ByWater Solutions
bywatersolutions.com
Phone:(888)900-8944 <(888)%20900-8944>

What is Koha? <http://bywatersolutions.com/what-is-koha/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20210426/6ade74e6/attachment-0001.htm>

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

Message: 6
Date: Mon, 26 Apr 2021 23:46:04 +0200
From: Victor Grousset/tuxayo <victor@tuxayo.net>
To: Koha@lists.katipo.co.nz, koha-devel
    <koha-devel@lists.koha-community.org>
Subject: [Koha-devel] Koha 19.11.17 released
Message-ID: <60abd1be-731d-d5ca-2762-7556ed7a9984@tuxayo.net>
Content-Type: text/plain; charset=utf-8; format=flowed

Hello!

The Koha Community is happy to announce the release of Koha 19.11.17

The full release notes can be found at:
https://koha-community.org/koha-19-11-17-released/

Debian packages should be available shortly.

Thanks to everyone involved :)


Cheers,

--
Victor Grousset/tuxayo


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

Message: 7
Date: Tue, 27 Apr 2021 09:44:47 +1000
From: <dcook@prosentient.com.au>
To: "'Julian Maurice'" <julian.maurice@biblibre.com>,
    <koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] Template::Toolkit and Translations
Message-ID: <032601d73af6$24a6b570$6df42050$@prosentient.com.au>
Content-Type: text/plain;    charset="utf-8"

Hi Julian,

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.

But I'd be fine with putting the translations of languages into Perl rather than Template::Toolkit.

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.

David Cook
Software Engineer
Prosentient Systems
Suite 7.03
6a Glen St
Milsons Point NSW 2061
Australia

Office: 02 9212 0899
Online: 02 8005 0595

-----Original Message-----
From: Koha-devel <koha-devel-bounces@lists.koha-community.org> On Behalf Of Julian Maurice
Sent: Monday, 26 April 2021 8:17 PM
To: koha-devel@lists.koha-community.org
Subject: Re: [Koha-devel] Template::Toolkit and Translations

Hi David,

I think that language descriptions would be best in a Perl module, so that they can be used everywhere (perl and templates).

For instance:

package Koha::Languages;
use Koha::I18N;
sub getLanguages {
return {
en => __('English'),
fr => __('French'),
}
}

And if the original description is needed, we can do the same but without the __() translation.

sub getLanguagesDescriptionsInTheirOwnLanguage {
return {
en => 'English',
fr => 'Français',
}
}

Le 26/04/2021 à 02:44, dcook@prosentient.com.au a écrit :
> Hi all,
>
> While I mostly work in English, I occasionally do support libraries in
> other languages like French, Arabic, and Chinese. And more recently
> I’ve been looking at the Languages dropdown in the OPAC advanced search.
>
> In the templates, I notice that we often translate HTML, but what if
> we translated strings for a Template::Toolkit data structure instead?
>
> Consider the following:
>
> [% BLOCK en %]Anglais[% END %]
>
> [% BLOCK fr %]Français[% END %]
>
> [% langs.en = INCLUDE en %]
>
> [% langs.fr = INCLUDE fr %]
>
> I suppose it’s not very beautiful, but the translation process should
> be simple and in the end we have a re-usable hash map rather than static HTML.
>
> As I commented on Bug 12017
> (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12017
> <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12017>), we
> could have a database table of language codes with native language
> names, and then iterate through that and use the hash map of
> translations to provide the translations. Since we’re not producing
> HTML, we could flexibly reuse this language data in various different
> contexts. Whether it’s the Languages dropdown in the OPAC advanced
> search, the language selector, or whatever.
>
> We could probably use this concept in other places as well where we
> need translations but we don’t want to be bound to HTML.
>
> What do people think? I’m not wedded to the idea, but it’s something
> that crossed my mind this morning, when I looked at the large switch
> statements at
> https://bugs.koha-community.org/bugzilla3/page.cgi?id=splinter.html&bu
> g=12017&attachment=40285
> <https://bugs.koha-community.org/bugzilla3/page.cgi?id=splinter.html&bug=12017&attachment=40285>.
>
>
> (To that end, I would also suggest a theme-independent
> Template::Toolkit include directory, but that’s another story…)
>
> David Cook
>
> Software Engineer
>
> Prosentient Systems
>
> Suite 7.03
>
> 6a Glen St
>
> Milsons Point NSW 2061
>
> Australia
>
> Office: 02 9212 0899
>
> Online: 02 8005 0595
>
>
> _______________________________________________
> 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/
>

--
Julian Maurice
BibLibre
_______________________________________________
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/




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

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 185, Issue 28
*******************************************


NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.