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

[Fwd: [Koha] Mellon Awards for Technology Collaboration]
by Andres Tarallo 07 Jun '06

07 Jun '06

Saw this in the Koha LIST.

1 0

Next stable release (roadmap + question) (kados, read carefully)
by Paul POULAIN 07 Jun '06

07 Jun '06

Hello all, I think we have almost solved the 2 main problems with rel_2_2 : * encoding problems : joshua get rid of unicode ones & I get rid of the remaining iso-8859-1 one. I made something i'm not very proud of : Joshua introduced a TemplateEncoding system preference that can be either iso8859-1 or utf8. If it is set to iso8859-1, there are a lot of encoding problems : MARC::File::XML don't like it, as MARC::Record is supposed to work in MARC8 or UNICODE. Thus, it seems that all accents are transformed in the process html => xml => marc. Thus, i've reintroduced the html => marc behaviour if the TemplateEncoding is set to iso8859-1 (i've fixed the html2marc as joshua proposed previously, fixing a remaining bug) This solution is a workaround : we will have to find a correct solution for Koha 3.0, to move every Koha to UNICODE and UNICODE only. But for instance, I tried some things but failed. Thust this solution, that works correctly for french libraries and should change nothing for unicode ones.' 'acqui.simple/addbiblio.pl' 2>&1 * MARC editor, cloneTag problem : when duplicating a tag, there was 2 problems : - the mandatory flags where no more properly affected. I solved this problem by moving color change on Check to the field itself, not to error$i container. Error$i container is now useless and removed. I also changed active color to grey, yellow being for mandatory fields. - when you duplicate a field with an authority, the value is still reported to the 1st field. When you duplicate the 1st authority, the container name is set to index+index, so you get 2 "indexindex" containers. I still have to solve this problem, but that should not bee too hard I think. Kados : I didn't modified NPL templates, I let you do this. ROADMAP : ========== I hope I'll find some more time to work on this version next week, working on translation to french, and maybe install it to one of my libraries. So, this next version should be officially released on 12th / 13th. what could be it's name ? 2.2.6 or 2.4.0 ? That will be discussed on monday (note for everybody : monday is closed in France. So you won't see us on chat. But i'll be here on monday 20:00GMT (10PM for French ppl) -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org)

3 3

Next Meeting
by Joshua Ferraro 05 Jun '06

05 Jun '06

Hi all, We had a rather light meeting today, and decided to schedule another one for Wednesday June 7th at 20:00 GMT. Hope to see you there. 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

borrowers Module
by toumi bruno 02 Jun '06

02 Jun '06

Hi everybody I'm working now on borrowers module ,and i try to fix all the bugs . Don't work on it until i've finished. ps:Use the updatedatabase because the borrowers table has changed.

1 0

[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