What I have in mind is a mechanism which would allow Koha users to go in
Administration, and request a specific language for their installed Koha
version. For example, I run Koha 3.22.1. I go in Admin > WUI Language. I
select a language. I see a list of .po versions for this combinaison (Koha
versi
Hi,
On Mon, Feb 1, 2016 at 7:27 AM, Frédéric Demians wrote:
> Do we really need a Git repo for translation files since the authoring
> of translated strings is managed outside Git in Pootle?
I think there's some value in continuing to have one:
- in the (of course unlikely) event that the Pootl
> The idea was to manage po files using git subtree:
> http://lists.koha-community.org/pipermail/koha-devel/2015-March/041293.html
See that also:
https://wiki.koha-community.org/wiki/Git_Splitting_and_Shrinking
Do we really need a Git repo for translation files since the authoring
of translated
The idea was to manage po files using git subtree:
http://lists.koha-community.org/pipermail/koha-devel/2015-March/041293.html
2016-02-01 11:35 GMT+00:00 Frédéric Demians :
> The various Koha translations could also be placed under the umbrella
> of this "Data Sharing" project. Rather than embeddi
The various Koha translations could also be placed under the umbrella
of this "Data Sharing" project. Rather than embedding translation
files (.po files) into Koha base code, they could be available online
and retrieved from Koha "Data Sharing" server (KDSS), and then
installed on the fly when requ
Hi Paul,
I have this idea (share reports) in mind for a while.
The main point was to keep up-to-date the reports listed on the wiki
page (https://wiki.koha-community.org/wiki/SQL_Reports_Library).
IMO one important thing is to cover each report with tests, to confirm
they still pass from one versi
About sharing data, it may be an Koha-independent project, but a
linked-one also, there is the issue of the books cover images. There
are now coming from various providers (Google, Amazon, etc.). It would
be great to have an images storage server which could replace the one
integrated in Koha (loca
"Multi-tenant" is certainly a vague term. Koha via Debian packages is already
multi-tenant at the code level. Personally I don't know why someone would
promote "multi-tenant" as something desirable in a lot of contexts, but I see
that you're referring to it in the sense of sharing data. That's c
