https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26392 --- Comment #37 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- (In reply to Tomás Cohen Arazi from comment #36)
(In reply to Katrin Fischer from comment #35)
(In reply to David Cook from comment #32)
(In reply to Katrin Fischer from comment #29)
Have to still read discussion, but I also am in favor of keeping stuff readable in templates to some extent. Using only variables in templates and having to look them up in a Perl script adds an extra step and will make it harder again for people to contribute simple changes.
Easier doesn't always mean better.
Not always, but I think in this case it applies. Forcing people to invent tons of variables will not make things more readable, but much likely less so. Koha is a very string heavy application. Look at the numbers in our po files on Pootle - I am an active translator.
Also I foresee use of a lot of silly variable names with the amount of strings we have.
With DSpace, you see keys like this: "jsp.dspace-admin.eperson-edit.emailexists".
And you say that's easier?
Yes!
intranet.admin.libraries.list_title
I really don't see the advantage of this. To me it adds an extra step with no visible win. -- You are receiving this mail because: You are watching all bug changes.