i think the best idea is that the various Koha installation guides get
consolidated into a new project, following the workflow of the 'Koha manual'
project
https://gitlab.com/koha-community/koha-manual
it's critical that the installation doco is correct and up to date, and an
elected group of
> this looks good to me - why do you think it might not be worth pursuing?
No particular reason, I just wanted to get some opinions in case there
was a downside I wasn't seeing.
Also: Julian is right, the t() macro works perfectly, I was just
looking at the wrong po file!
Thanks,
Owen
--
Hi all-
At the last developers meeting I volunteered to draft a proposal on
Inclusive Language to the Koha community coding guidelines. The proposal is
below along with some reasons why we would want to do this as well as a
couple of resources for those wanting to do a deeper dive into the topic.
Hi Owen,
this looks good to me - why do you think it might not be worth pursuing?
Katrin
On 13.07.20 16:36, Owen Leonard wrote:
I've posted a work in progress here:
https://gitlab.com/koha-dev/koha-dev/-/tree/wip-2020-07-08-combine-header-searches
Katrin I liked your idea about defining the
I'm collecting news for the July newsletter. Send anything noteworthy to:
k o h a news AT gmail dot com
News criteria:
---
** For events **:
- Please include dates for past events. If I can't find dates I may not add
it.
- Announcements for future events with dates
Le 13/07/2020 à 16:36, Owen Leonard a écrit :
Even with the t() macro the
labels are still not picked up for translation correctly.
What do you mean ? Translation works for me on your branch :
https://pic.infini.fr/nqc3mEkM/mvaUg6k2.png
--
Julian Maurice
BibLibre
I've posted a work in progress here:
https://gitlab.com/koha-dev/koha-dev/-/tree/wip-2020-07-08-combine-header-searches
Katrin I liked your idea about defining the labels, but I'm not sure I
did exactly what you were suggesting. Even with the t() macro the
labels are still not picked up for
