- Koha-devel - lists.koha-community.org

Re: [Koha-devel] Public IP for Koha
by Tim O'brien 21 May '12

21 May '12

Hi, I manage to intall koha 3.6. My institution has four branch libraries and i wanted to use public IP so that the other three branches can access the system. I am thinking of using public IP for these purpose. Kindly advice me: the risks and if there are better options. Regards, O'brien

3 2

Koha Calendar
by Elliott Davis 16 May '12

16 May '12

As I'm sure everybody running master has realized, bug 5549 introduced a new module Koha::Calendar. After digging around in the module I realized that the table special_holidays had separate columns for year, month, and date. I am wondering what the rationale is behind this decision. If it was simply I preference I would like to propose that we move it to replace the 3 current columns with a timestamp so that the calendar can take advantage of setting open and closed hours and fining for hourly based items accordingly. Elliott Davis Library Systems Analyst Robert R. Muntz Library [Description: Telephone]903.565.5542<tel:903.565.5542> [Description: Envelope]tdavis(a)uttyler.edu [Description: Chrome]http://library.uttyler.edu<http://library.uttyler.edu/>

2 1

Re: [Koha-devel] Multi-Lingual SQL & User Defined Parameters
by Karam Qubsi 16 May '12

16 May '12

Hi Dear Mr Massoud , Dear all, I think this will be very helpful for the people who don't want to use the English interface in Koha , and as you say when we finish translating koha 3.8 to Arabic ( very soon inshaallah) , we will have problems with the people who want to use koha in Arabic and english in the same time e.g: May be some Arab librarian prefer to use koha English interface for the staff client , and in the case that we've used the translated sql files (that your company provided it to us) for the marc21 the Arab librarian who want to use the English interface will have a problem because all the staff client will be in english except for the marc records and if we use the English version of the marc21 sql files the problem will be that the Arab librarian who will use the Arabic interface will see the marc fields in english so if we want to use arabic interface we have to use arabic sql files for marc is it possible to make something like armarc as we have normarc in the SQL structure ?! it's not a standard we don't really have 'armarc' and it is not a solution so the library chose its Marc flavor and all the librarian in that library will be forced to use this armarc , but will help to make the installation of the translated Arabic marc more easier and for the preferences description is included in the po files but the preferences still in English (the main term ) maybe the best solution is to make all the strings in koha included in the po files I don't have deep technical background but this will be more flexible for koha users all over the world for other languages not only for the Arabic language wish you will be able to do that for all the koha community :) thanks a lot for you Mr Massoud and thanks you all in Koha community for helping us :D Karam Qubsi Koha Arab Translating Team http://koha.wikibrary.org/ Wikibrary for Arab Librarians http://wikibrary.org > Date: Wed, 16 May 2012 09:00:57 +0300 > From: Massoud Alshareef <massoud(a)kwareict.com> > Subject: [Koha-translate] Multi-Lingual SQL & User Defined Parameters > To: koha-devel(a)lists.katipo.co.nz, koha(a)lists.katipo.co.nz, > koha-translate(a)lists.koha-community.org > Message-ID: > <CAMp2hxbU3fzajsQjgd-hou-RiPLmJ7y8Wf3XU=k2=5W15pPzmQ(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hello, > > I have asked a question about two years ago about when we can have Koha > support of Multi-Lingual SQL files (used for marc21/Auth fields description > in the Staff client) and Multi-Lingual users defined parameters (used for > describing items/ libraries & groups/ locations/ patrons categories/ etc), > and the answer from Koha development then was that it is > under consideration but not in the development pipelines yet, as it will > require some re-structuring in Koha system databases and controls. That > means, Koha will remain a single language in these areas. > > With Koha 3.6 release, I noticed the inclusion of "Spanish translation for > SQL files" in the INTERNATIONALIZATION enhancement section. Does this mean > that Spanish Koha, or any non-English Koha, now has both Spanish and > English SQL files, where Koha users can switch between more than one > language when, for instance, editing marc records in the staff client ? > > Koha Preferences description used to be in SQL files, which means a single > language prefers, and then moved into PO files format with 3.2 release (I > think) and thus Preferences became multi-lingual since then. > > Thank you Koha development for elaborating on the issue of having a fully > bilingual Koha. > > BTW, Arabic Koha 3.8 is now on the fast-lanes translation speed to be > completed within 3-4 weeks. > See Arabic Koha 3.8 OPAC demo site on > http://176.34.184.60/cgi-bin/koha/opac-search.pl?q=%D8%B9%D9%84%D9%85 > > Thanks > Massoud M. AlShareef, > > The world of achievement has always belonged to the optimist! > > KnowledgeWare Technologies > (P.O. Box 230-312) > Riyadh 11321, Saudi Arabia > Cel: +966 505 307 267 > massoud(a)kwareict.com >

2 1

sandbox system
by Paul Poulain 16 May '12

16 May '12

Hello koha-devel, I just pushed a few minuts ago the 1st version of the sandbox scripts I've developped and that is available to facilitate testing of Koha patches. You'll find everything, including some installation notes at http://git.koha-community.org/gitweb/?p=contrib/global.git;a=summary (git clone git://git.koha-community.org/contrib/global.git contrib, in the sandbox directory) PS: if you want to improve my scripts, you're welcomed ! -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

1 0

Multi-Lingual SQL & User Defined Parameters
by Massoud Alshareef 16 May '12

16 May '12

Hello, I have asked a question about two years ago about when we can have Koha support of Multi-Lingual SQL files (used for marc21/Auth fields description in the Staff client) and Multi-Lingual users defined parameters (used for describing items/ libraries & groups/ locations/ patrons categories/ etc), and the answer from Koha development then was that it is under consideration but not in the development pipelines yet, as it will require some re-structuring in Koha system databases and controls. That means, Koha will remain a single language in these areas. With Koha 3.6 release, I noticed the inclusion of "Spanish translation for SQL files" in the INTERNATIONALIZATION enhancement section. Does this mean that Spanish Koha, or any non-English Koha, now has both Spanish and English SQL files, where Koha users can switch between more than one language when, for instance, editing marc records in the staff client ? Koha Preferences description used to be in SQL files, which means a single language prefers, and then moved into PO files format with 3.2 release (I think) and thus Preferences became multi-lingual since then. Thank you Koha development for elaborating on the issue of having a fully bilingual Koha. BTW, Arabic Koha 3.8 is now on the fast-lanes translation speed to be completed within 3-4 weeks. See Arabic Koha 3.8 OPAC demo site on http://176.34.184.60/cgi-bin/koha/opac-search.pl?q=%D8%B9%D9%84%D9%85 Thanks Massoud M. AlShareef, The world of achievement has always belonged to the optimist! KnowledgeWare Technologies (P.O. Box 230-312) Riyadh 11321, Saudi Arabia Cel: +966 505 307 267 massoud(a)kwareict.com

1 0

Call for News for the May Newsletter
by Daniel Grobani 15 May '12

15 May '12

Dear Koha Kommunitarians, I'm harvesting news for the May newsletter. Please send me by the 25th anything you think your fellow community members might like to know about. "News" can be as short as a sentence or as long as a paper. I especially encourage you to send me a line or two for the gossip/society column about what you're currently working on. And if you know of a go-live not announced on the list, please be sure to let me know about it. Thanks, Daniel Grobani

1 0

Koha 3.8.1 entering string freeze
by Chris Cormack 14 May '12

14 May '12

Hi All As promised, the 3.8.x branch has entered string freeze in preparation for the 3.8.1 release next week. "So?" you ask, "What does this mean for me?" Are you a developer? - If so just be aware I will only be pushing patches that do not contain changes to any of the translatable strings from now until the release. Are you a translator? - Once the translation manager emails to say the po files are updated, you are clear to translate your hearts out. Are you a Koha user? - If you have the skills or know someone who does, check out the 3.8.x and do some testing on it, that would be awesome. Are you a brewer? - I quite like a nice IPA Chris

1 0

Guided report in Koha 3.8.0
by Partha Mukhopadhyay 14 May '12

14 May '12

3 3

Branch Specific System Preferences
by Chris Nighswonger 11 May '12

11 May '12

Recently the need has arisen locally to run the self-checkout (sco) under multiple user accounts to accommodate multiple branches using the sco module. To the best of my understanding this is not currently possible due to the way in which the user for the sco module is defined using a system preference. While there may be a number of ways to accomplish this, it seems that it may be desirable to have a category of "branch specific" system preferences. This would be an attempt to group system preferences into one of two general categories of "global" or "branch." Before launching out into writing such a feature, I thought I'd run it by both lists to see if a) I'm way off base, b) if such a feature is desirable, and c) if I'm off on an insanely hard project. Kind Regards, Chris

8 17

Localization of Perl strings in Koha
by Julian Maurice 11 May '12

11 May '12

Hi, a discussion has started in bug 8044 (http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8044) about localization in Koha. But I want to include in this discussion the maximum number of people. Summary of the discussion: I proposed a patch that uses Locale::Maketext. You can see an example of use in the 2nd patch attached to the bug, but here is a code sample: use Koha::I18N; use CGI; my $cgi = new CGI; my $lh = Koha::I18N->get_handle_from_context($cgi, 'intranet'); $lh->maketext("A localized string with parameter: [_1]", $some_scalar); Then, Frédéric Démians suggested to use Locale::TextDomain instead of Locale::Maketext (some advantages are listed in bug comments) There is also a discussion about how we can handle templates translation with a translation framework like Locale::Maketext or Locale::TextDomain. This is not the topic of bug 8044, but a global discussion now is certainly better than choosing a direction now and then taking the opposite direction in a few months. First, we have to make a decision about the module to use. If you know well the two modules, please join the discussion! Next, the patch is only a 'first draft': PO files are in a new directory locale/<LANG>, and the script that updates PO files is in locale directory too. I don't know where is the best place to put them in order to integrate well with Koha. So any suggestions are welcomed. If you have any other suggestion, please feel free to contribute :) -- Julian Maurice <julian.maurice(a)biblibre.com> BibLibre

1 0