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

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Fri Dec 11 01:59:53 CET 2020


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

--- Comment #24 from David Cook <dcook at prosentient.com.au> ---
(In reply to David Cook from comment #22)
> (In reply to Owen Leonard from comment #21)
> > If you're referring to the question of syntax, other projects I've seen do
> > something similar. For instance in Drupal:
> > 
> > <?php print t('Skip to main content'); ?></a>
> > 
> > Translatable strings are wrapped in the t() function.
> 
> Drupal is an old project as well, and that example looks worrying. Based on
> https://en.wikipedia.org/wiki/Drupal#Themes, it looks like that example must
> be one of those "hard-coded PHP" templates. I wonder what they do in Drupal
> 8+ with Twig.

Admittedly, https://metacpan.org/pod/Catalyst::Plugin::I18N uses a similar
method using l() instead of t().

I suppose I wouldn't mind t() that much (although the Java way of doing it is
still better I think) if that were the only macro we were required to use, but
Bug 26392 introduces t(), tx(), tnx(), txn(), tp(), tpx(), tnp(), tnpx(). 

In my opinion, it's a bit absurd to expect developers to use 8 different macros
which look almost exactly the same. 

I think that it'll make front-end developments take 10x* as long, as QA will
constantly need to be telling people to re-do their templates. 

But I could be wrong. Maybe we'll all get used to the 8 different macros. 

I was going to say that I'll probably just stop contributing template changes
to Koha, but I guess I'm on the QA team these days, so I should probably
memorize them. 

*arbitrary order of magnitude

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


More information about the Koha-bugs mailing list