You can switch the language in staff and the OPAC. We always offer English and German, and sometimes additional languages as well, in our installations. Of course, every string stored in the database can only be in one language. This is true for the frameworks, authorized values, itemtype and patron category descriptions, and so on. Katrin On 2013-07-05 08:01, Robin Sheat wrote:
A language choice option already exists, at least in the OPAC. Possibly also in the staff client, but I haven't looked.
Paul <paul.a@aandc.org> wrote:
Op 04/07/13 16:13, Paul schreef:
[version 3.8] Yes, it's hard coded in the templates (*.tt -- example opac-main.tt, opac-results.tt, etc) in /usr/share/koha/opac/htdocs/opac-tmpl/prog/en/modules between 'doc-head-open.inc' and 'doc-head-close.inc'... I once edited all of these (we also prefer English English to US English), but you lose some|many|most of them on upgrades. And there's many more uses of
At 04:57 PM 7/4/2013 +0100, Robin Sheat wrote: the US
spelling 'catalog' -- see your para 2. (below) "Library Catalog"
No, the default language is en-US which uses "catalog". In en-NZ it's catalogue, in nl it's catalogus, in fr it seems to also be catalogue. Koha handles all of this just fine, using the translation system.
Thanks Robin - I had never noticed that there were EN-GB files in 3.8 ;={ I've just read Paul P.'s comments in translator_doc.txt and <http://wiki.koha-community.org/wiki/Installation_of_additional_languages_for_OPAC_and_INTRANET_staff_client#Adding_additional_languages_after_installing_Koha_on_your_server>
and will try and find time to play with it in the sandbox.
And, btw, I was certainly not recommending changing the hard coded templates -- after hours of grep + vi, I would not be that sadistic to other users.
Thinking out loud, has anyone ever tried to set up a "language choice" option? Here in Canada we have two official languages (EN and FR), and it would be very neat to become bi-lingual in Koha.
Best - Paul
The values aren't really hardcoded: they're in the file because that's where they go, but they are changed as needed when translations are updated.
If you're editing the templates to get custom or regional vocabulary, you are doing it wrong. Instead you should run a translation or develop your own based on the most appropriate for your library's wants.
-- Robin Sheat Catalyst IT Ltd. â +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
--- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca>
The language can in fact be switched in the OPAC. There is a system preference in I18N/L10N, opaclanguagesdisplay, when set to enable will allow borrowers to change languages, if you have them installed. At the least, there isn't a language switching preference for the staff client, yet,that I could find. For adding additional searches, you can have a look at http://wiki.koha-community.org/wiki/JQuery_Library#Add_additional_searches_t... - You would pop this in your OPACUserJS field (instructions are at the top of the page). Multiple statements would be required to add multiple search types, but it is easily doable without editing the templates. I'd suggest popping into the Koha IRC channel to figure out the specific values you are wanting for each search. Liz _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha