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

[news] Full time developper for Koha 3.0
by Paul POULAIN 01 Jun '06

01 Jun '06

Hi, I'm pleased to announce that Henri-Damien and me have decided to hire Antoine for 6 months. We have so many contracts that we can't work on HEAD / Koha 3.0 So, we have decided to dedicate Antoine to this, and to this only. He work on OpenCataloger for 1 more week. Then 1 week off. Then, from June, 19th to Dec, 19th, he will be available for : - code cleaning on head - zebra & unimarc - test & bugfixing. So, don't hesitate to suggest directions he should follow first. I think it's roadmap could be : 1 - install a working copy of head 2 - play with it to find Internal Server Errors & dead-end pages (pages with no useful links to continue working : i think there are some/many on HEAD, with the new PROG templates) 3 - clean code : - find & remove unused code - standardize things (coding guidelines) 4 - work on Zebra things, to test & fix what has to be (except encoding problems) 5 - work on zebra things, specifically for UNIMARC & encoding questions ... -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org)

2 1

coding guidelines, SQL queries
by Pierrick LE GALL 01 Jun '06

01 Jun '06

Hello koha-devel, I've put online the first of the coding guidelines [1]. I've started with SQL queries. I want your feedback about what I've written. Concerning inserts and updates, I propose two new functions mass_inserts and mass_updates (that I have already written in PHP, easy to port in Perl). [1] http://wiki.koha.org/doku.php?id=en:development:codingguidelines Bye -- Pierrick LE GALL INEO media system

2 3

Introducing Myself
by Mike Hafen 01 Jun '06

01 Jun '06

A little about myself: I am working for a school district in southern Utah, USA. We are implementing Koha to replace a propriatery system for budget reasons. I am the one doing customization / migration. I have also posted most of my changes to bugs.koha.org. Thank you for a great project. From: Chris Cormack Subject: Koha Bugs Date: Wed, 31 May 2006 07:39:26 +1200 To: mhafen(a)i.washk12.org Cc: jmf(a)liblime.com [Full Headers] [Undecoded Letter] Hi there Im one of the Koha developers and I want to say a big thank you for submitting bugs and an even bigger thank you for committing patches :) I was wondering if you would like to join the koha-devel list (if you havent already) and drop an email to the list with a quick introduction. Or if you like jump on irc .. irc.katipo.co.nz:6667 #koha and say gidday there. Once again thanks Chris -- Chris Cormack Programmer 027 4500 789 Katipo Communications Ltd chris(a)katipo.co.nz www.katipo.co.nz

2 1

about tranlsating value_builder
by long_sam.tw 31 May '06

31 May '06

Hi,all if you wanted to translate value_builder to utf-8 (abut CJK language),you would modify /cgi-bin/value_builder/*.pl. You should setup CGI header's charset => utf-8. ex if you wanted to translate unimar_leader.tmpl, you should modify intranet/cgi-bin/value_builder/ unimarc_leader.pl line 102 print $input->header(-charset =>'utf-8', -cookie => $cookie),$template->output; } setup -charset =>'utf-8',then you can translate unimarc_leader.tmpl. but i use original unimarc_leader.tmpl,then tested more times.it's not ok. finally,i open new unimarc_leader.tmpl files,then copy and paste. it is ok. Note:if you would not set header charset,default vaules were iso-8859-1. snapshot http://www.flickr.com/photo_zoom.gne?id=155172742&size=o laxendion ___________________________________________________ 最新版 Yahoo!奇摩即時通訊 7.0，免費網路電話任你打！ http://messenger.yahoo.com.tw/

1 0

bug reports
by long_sam.tw 31 May '06

31 May '06

hi,koha develop team i found 3 bugs in koha 2.2.5 version. ========================== 1. modify moremember.tmpl ========================== original line 128 form class="inline" action="renewscript.pl" modify form class="inline" action="../renewscript.pl" original line 171 form class="inline" action="renewscript.pl" modify form class="inline" action="../renewscript.pl" ======================== 2.modify readingrec.tmpl ======================== original line 38 form action="moremember.pl" modify form action="./members/moremember.pl" =================================================== 3.modify intranet-tmpl/npl/en/catalogue/detail.tmpl =================================================== if you could not setup amazon's module, you should delete line 10~12. <div style="float: right;"> <img src="http://images.amazon.com/images/P/.01.MZZZZZZZ.jpg" alt="Book Cover Image" /> </div> //Display for NPL --> Because they will break your layout,i suggest it. laxendion ___________________________________________________ 最新版 Yahoo!奇摩即時通訊 7.0，免費網路電話任你打！ http://messenger.yahoo.com.tw/

1 0

Improvements on issues page
by arnaud laurin 31 May '06

31 May '06

Hi, I'm working with the reserves infos on the issues page . Today, the system show only the reserves waiting, in the borrower informations cell ....... is that ok for everyone, if I remove "reserves waiting" of the "borrower informations" cell, and create a new cell called "Borrower current reserves" but this function will display more informations of reserves like .... - Reserves in wait - Localisation of the document if it's on transfer (ex . : transfered by the labrary X the 2006-05-05) or not transfered yet .... - Waiting Position of borrower for this document ..... If you think it's ok, I can commit it earlier ........ N.B : sorry for my english ........

1 0

npl zh_TW language files
by long_sam.tw 31 May '06

31 May '06

Hi,Koha core develop team attached files are npl zh_TW language files。please commite them into koha。 thank you laxendion ___________________________________________________ 最新版 Yahoo!奇摩即時通訊 7.0，免費網路電話任你打！ http://messenger.yahoo.com.tw/

1 0

Koha Developer's IRC Meeting
by Joshua Ferraro 30 May '06

30 May '06

Hi folks, Now that the dust has settled, and we're (hopefully) all caught up from being away, it's probably a good time to schedule another Koha developers's meeting on IRC. Do Mondays around 20:00 GMT still work for everyone? Unless I hear otherwise, lets schedule our next meeting for Monday May 29 at 20:00 GMT. Here's the time in your area: http://tinyurl.com/jdbk7 Cheers, -- Joshua Ferraro VENDOR SERVICES FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS

7 6

Re: New to KOHA
by Deniz Köllhofer 29 May '06

29 May '06

G'day. I was just curious when the 2.2.6 version, including the amazon features and bugfixes, is going to be available. I found a posting by Paul in the archives that said something about end of march... > koha-2.2.5.tar.gz 09-Jan-2006 15:43 2.4M Thanks for you help, Deniz From: Paul POULAIN <paul.poulain@...> Subject: Re: New to KOHA Newsgroups: gmane.comp.misc.koha Date: 2006-02-27 20:43:07 GMT (12 weeks, 6 days, 16 hours and 34 minutes ago) [...] Hello Marie, in fact, henri Damien already developped such a script, it's in CVS, it will be available in *2.2.6* (end of march) -- *Paul* *POULAIN* Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Re: More Fun With MARC::File::XML: Solutions
by Joshua Ferraro 28 May '06

28 May '06

Hi everyone, Just providing an update on this issue. As you may recall, I've been putting the MARC::Record suite, specifically MARC::File::XML and MARC::Charset, through some fairly rigourous tests, including a 'roundtrip' test, which converts the binary MARC-8 records to MARCXML / UTF-8 and then back to binary MARC but encoded as UTF-8. This test is available here: http://liblime.com/public/roundtrip.pl I discovered a number of bugs or issues, not in the MARC::* stuff, but in the back-end SAX parsers. I'll just summarize my discoveries here for posterity: 1. MARC::File::XML, if it encounteres unmapped encoding in a MARC-8 encoded binary MARC file (in as_xml()) will drop the entire subfield where the improper encoding exists. The simple solution is to always use: MARC::Charset->ignore_errors(1); if you expect your data will have improper encoding. 2. the XML::SAX::PurePerl parser cannot properly handle combining characters. I've reported this bug here: http://rt.cpan.org/Public/Bug/Display.html?id=19543 At the suggestion of several, I tried replacing my default system parser with expat, which cause another problem: 3. handing valid UTF-8 encoded XML to new_from_xml() sometimes causes the entire record to be destroyed when using XML::SAX::Expat as the parser (with PurePerl these seem to work). It fails with the error: not well-formed (invalid token) at line 23, column 43, byte 937 at /usr/lib/perl5/XML/Parser.pm line 187 I haven't been able to track the cause of this bug, I eventually found a workaround that didn't result in the above error, but instead, silently mangled the resulting binary MARC record on the way out: 4. Using incompatible version of XML::SAX::LibXML and libxml2 will cause binary MARC records to be mangled when passed through new_from_xml() in some cases. The solution here is to make sure you're running compatible versions of XML::SAX::LibXML and libxml2. I run Debian Sarge and when I just used the package maintainer's versions it fixed the bug. It's unclear to me why the binary MARC would be mangled, this may indicate a problem with MARC::* but I haven't had time to track it down and since installing compatible versions of the parser back-end solves the problem I can only assume it's the fault of the incompatible parsers. Issues #3 and #4 above can be replicated following batch of records through the roundtrip.pl script above: http://liblime.com/public/several.mrc If you want to test #2, try running this record through roundtrip.pl: http://liblime.com/public/combiningchar.mrc BTW: you can change your default SAX parser by editing the .ini file ... mine is located in /usr/local/share/perl/5.8.4/XML/SAX/ParserDetails.ini So the bottom line is, if you want to use MARC::File::XML in any serious application, you've got to use compatible versions of the libxml2 parser and XML::SAX::LibXML. Check the README in the perl package for documentation on which are compatible... Maybe a note somewhere in the MARC::File::XML documentation to point these issues out would be useful. Also, it wouldn't be too bad to have a few tests to make sure that the system's default SAX parser is capable of handling these cases. Just my two cents. Cheers, -- Joshua Ferraro VENDOR SERVICES FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS

1 0