[Koha-bugs] [Bug 26392] Wrap all translatable strings in opac-main.tt

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26392

--- Comment #38 from David Cook <dcook at prosentient.com.au> ---
(In reply to Katrin Fischer from comment #35)
> 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. 

I think that we'll just have to agree to disagree on that one. The variables
would be formulaic so they shouldn't be difficult to create. It would also make
templates easier to wrangle, as you wouldn't have as much line wrapping and
thick blocks of text adding bulk to the templates.

> Koha is a very string heavy application. Look at the numbers in our po
> files on Pootle - I am an active translator.

I agree that the PO files are huge, but looking through them that are also lots
of junk lines, duplicate translations, unnecessary translations, etc. Using
tokens would cut down on a lot of that. 

I'm looking at ./misc/translator/po/fr-FR-staff-prog.po right now, and lots of
these lines would be eliminated or reduced by using tokens. 

I think that we could work smarter rather than harder.

> > 
> > > 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?

Absolutely. I work with this style in DSpace and Keycloak and it's so easy.

Also, it also makes it much easier to customize strings for existing
installations, since you can update "string files" rather than updating
templates which have been hard-coded with English strings.

-- 
You are receiving this mail because:
You are watching all bug changes.