https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36947 --- Comment #85 from David Cook <dcook@prosentient.com.au> --- Another reason why you'd use Unicode::Collate::Locale and not "use locale" is so that 1 Koha server can provide Koha instances with different locales. Technically, you could use both "use locale" and "setlocale()" together I suppose, but again Unicode::Collate::Locale is a nice core library designed for this exact purpose that we're using it for. (In reply to David Cook from comment #57)
I just finished writing and polishing this...
And I realize the LC_COLLATE thing is controversial, since it's a system-level thing and not an instance-level thing.
A system preference or a koha-conf.xml config is probably the way to go. We'd look it up in Koha/SearchEngine/Elasticsearch/Search.pm and pass it into the _sort_facets() function using the "locale" parameter.
--
I was going to say that since it's a system level thing and something that shouldn't be changed by librarians, I thought koha-conf.xml would be better.
But... if we used the system preference, then people could override it using VirtualHost directives in Apache, so that different front-ends use different locales.
I'm really not too fussed... the main reason I did this patch was out of the goodness of my heart (or perhaps intellectual vanity or perhaps both), so I'm happy to be led by others here on the configuration side of things.
-- You are receiving this mail because: You are watching all bug changes.