Hi all, please keep in mind that 'translated' doesn't mean into one language, but should allow for supporting different languages at the same time, especially if those descriptions were to be used for APIs as well.
Katrin On 26.02.19 00:11, David Cook wrote:
I was pondering this yesterday as well. I figure a lookup table in the database that contains the code and a description (for reporting and administration purposes), but use translatable strings in templates using the code as hooks. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 *From:*koha-devel-boun...@lists.koha-community.org [mailto:koha-devel-boun...@lists.koha-community.org] *On Behalf Of *Barton Chittenden *Sent:* Tuesday, 26 February 2019 12:58 AM *To:* Chris Cormack <chr...@catalyst.net.nz> *Cc:* Koha-devel <koha-devel@lists.koha-community.org> *Subject:* Re: [Koha-devel] Discussion of account types / labels On Mon, Feb 25, 2019 at 6:51 AM Chris Cormack <chr...@catalyst.net.nz <mailto:chr...@catalyst.net.nz>> wrote: Whatever they are changed to needs to be translatable. Agreed. I suspect that the trade-offs between 'We would like this to be translatable' and 'we need these values to be un-editable' (I.e. not authorized values) are probably what's kept things as they are. _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
