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

cvs synchro between 2.2 and head
by Paul POULAIN 06 Jan '06

06 Jan '06

Hello koha devs, i just commited all fixes/improvements that are in koha 2.2.5 in head. Don't expect this synch to be bugfree, but i made some test anyway, it should not break too many things. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Koha 2.2.5 for monday
by Paul POULAIN 06 Jan '06

06 Jan '06

Hello, unless otherwise stated (a mail from owen mail, mainly ;-) ), Koha 2.2.5 will be available on monday. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

cvs change log
by Paul POULAIN 04 Jan '06

04 Jan '06

Hello, the cvschangelog is calculated daily and available at : bureau.paulpoulain.com/cvslog/ (for both 2.2 and head versions) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Koha 3.0 and UTF-8
by Paul POULAIN 04 Jan '06

04 Jan '06

utf8 is a : go for beta test in HEAD. Some explanations of what i've made : - updater/updatedatabase => will transform all tables in innoDB (not related to utf8, just to warn you) AND collate them in utf8 / utf8_general_ci. The SQL command is : ALTER TABLE tablename DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci. - *-top.inc will show the pages in utf8 - THE HARD THING : for me, mysql-client and mysql-server were set up to communicate in iso8859-1, whatever the mysql collation ! Thus, pages were improperly shown, as datas were transmitted in iso8859-1 format ! After a full day of investigation, someone on usenet pointed "set NAMES 'utf8'" to explain that I wanted utf8. I could put this in my.cnf, but if I do that, ALL databases will "speak" in utf8, that's not what we want. Thus, I added a line in Context.pm : everytime a DB handle is opened, the communication is set to utf8. - how to deal with MARC records ? MARC records are in marc-8 encoding, stored in biblioitems.marc binary format, that is not modified by the alter table (fortunatly, as it's a binary format !). But... I created a marcxml column in this table, containing the XML output of the marc record (a duplicate of the raw marc record). I did not knew what it will be used for, but know I know : the utf8 move transform the marcxml column, and the catalogue is moved to utf8 (with MARCgetbiblio using marcxml instead of raw marc) ! The last question being : is biblioitems.marc (raw marc record) still useful ? I think no : - iso2709 is limited to 99999 char, specialised to MARC-8 encoding, binary. - XML has none of those limitations. Thus, my opinion is that we should get rid of iso2709 and use XML everywhere, except when exporting datas in iso2709 format. But internally, we should use only XML. Let me know if it works completly, correctly, poorly or not at all for you ! -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Sharing experience with utf-8
by Tumer Garip 03 Jan '06

03 Jan '06

Here is what we had to do to use koha in utf-8 hoping that it helps in some of your discussions: 1- We are using koha since 2.2.0 now at 2.2.2b 2- We use English for intranet and English-Turkish for opac 3- The platform is Windows 4- We changed the character set of the database to utf-8 with the iso-xxxx data in it. No problem for Mysql as you are moving up the ladder. No need to reload the data (10 min) 5- Changed all the charset=iso-xxxx in the templates to read utf-8 and saved the files as utf-8 (15 min.) in a simple text editor. 6- Character decode in biblio for MARC21 is very ambigious for us because it is not very clear which character encoding it is changing from. All the marc records we bulkimport are MARC-8 , iso2709 or ANSEL or whatever you want to call them. So we simply wrote a one to one character mapping of MARC-8 to utf-8 for our Turkish accented characters. Here it is: #Additional Turkish characters s/(\xf0)s/ş/gm; s/(\xf0)S/Ş/gm; s/(\xf0)c/ç/gm; s/(\xf0)C/Ç/gm; s/\xe7\x49/İ/gm; s/(\xe6)G/Ğ/gm; s/(\xe6)g/ğ/gm; s/\xB8/ı/gm; s/\xB9/£/gm; s/(\xe8|\xc8)o/ö/gm ; s/(\xe8|\xc8)O/Ö/gm ; s/(\xe8|\xc8)u/ü/gm ; s/(\xe8|\xc8)U/Ü/gm ; s/\xc2\xb8/ı/gm; All the character codes are directly from LC's website about MARC21. Since we provided the actual characters rather than their codes we saved the biblio.pm as utf8 to save time. (Half a day together with research) 7- We have a full working koha as utf8 supporting all characters and we keep doing the same thing everytime we get an update. 8- Translation of opac files through .po files do not work for us. As we see it, this po translator is simply a search and replace text engine. So it converts the string ' English English <somevariable> English.' to ' Turkish Turkish <somevariable> Turkish'. Which is useless as it should be 'Turkish <somevariable> Turkish Turkish'. 9- So we sat down and translated the opac templates to proper Turkish. It is now more easier for our people to follow the changes in cvs and implement the changes to templates rather than doing complete translations every time. 10- The whole update up till now is taking less than half a day with one person doing it. 11- We as Windows people do not have much experience with this po editor. But as far as I know it supports utf8 so whats the hassle about these translations? As far as we understand it the official language of KOHA is English and if someone is translating it to some other language it is their responsibility to find the resources to translate it in time to be implemented as an additional language. Even if this requires a complete rewrite of some templates. 12- Finally we believe that koha should start using utf8 ASAP before the move to zebra to gain experience. If zebra is implemented with all this iso stuff we will have more problems with each translation requiring a different character set and sort order set and character mapping to set etc. etc. Koha is more powerful with more features, stability and performance and I believe people will be more happy to see improvement in these even if they have to spend a little bit more resource on their own translations. With no prejudice, Tumer Garip Near East Univ. Library Director Cyprus tgarip(a)neu.edu.tr

3 2

Re: Italian translation of Koha
by paul POULAIN 30 Dec '05

30 Dec '05

Tarcisio Fedrizzi a écrit : >Hi we are an italian society (Leader.IT) and we are interested in the >italian translation of Koha. So we have taken contact with one of the >translators Giuseppe Angilella, and he says us that he cannot prosecute >with the translation. So he says to contact you in order to get the access >to the online translation platform so we can resume the italian >translation. I apologize for my bad english and I hope you understand what >I wrote. > >Thank you for the attention. >Bye and Happy New Year. =) >Fedrizzi Tarcisio > > Hello Fedrizzi, For french translation of Koha, i Use kartouche. I've hacked it a little to fit some specific needs. I've added the italian translation for guiseppe, you can work on it : it's available here : http://bureau.paulpoulain.com/kartouche/ Let me know when you have translated many strings and want to test the results, i'll open some italian Koha for you on my desktop. (if bureau.paulpoulain.com don't work, that may be possible because of some DNS problems I have, the IP is : 213.41.184.186) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

2 1

Koha 2.2.5 roadmap
by Paul POULAIN 20 Dec '05

20 Dec '05

Hi, some news about 2.2.5 roadmap. It should be released as christmas gift, at the end of next week, or maybe january, 2nd. French libraries are testing this version. It almost only fixes bugs. Merry & holy christmas to everybody. Here the Release Notes of the future version : BUGFIXES === ACQUISITION === * suggestion/acquisition bugfixes : - 200 field is no more splitted in 2 parts - author is after title in UNIMARC (dirty solution, but mySQL has a strange behaviour) - when the book is recieved, the suggestion is marked "available" and a mail is sent * printing stylesheet dropped ALL <p> (hiding too many things in order printing) === CATALOGUING === * Repeated subfield in authority were not being reported in the biblio while cataloguing * when AuthoBarcode=ON and MARC=ON the barcode was not calculated automatically. Now, the barcode will be calculated (and any manual entry discarded during save) * adding a feature to enable reordering of subfields in MARC editor (can be considered as a bug ? at least one of my libraries think that yes !) * when a note is added to items it was not stored into non MARC-DB * permission required to use a plugin was wrong. Changed to "editcatalogue", more convenient. * if the last field was an authority, the authority report generated a javascript error (going after array size) === AUTHORITIES === * fixing bug in summary (separator before subfield was in fact after) * fixing bug in authority order : authorities are not ordered alphabetically instead of no order. Requires all the dataset to be retrieved, but the benefits is important ! * no need to do a search on an authority when the authority has no MARC field (like EDITORS pseudo authority) === SERIALS === * Ordering bull-home better : by title === CIRCULATION === * minor bugfix : showing date in format from systempreferences === REPORTS === * Lot of bugfixes in borrower issues, catalogue issues, issues stats === ALL === * bugfixes in ldap auth (bugfixes from 2.2.4, 2.2.3 was not buggy) === OPAC === * adding dashes in isbn in opac-detail.pl * translation bug ISSN translated to ISBN in french , very annoying mistake ! + some other translations * ordering by acquisition date was buggy. IMPROVEMENTS === ACQUISITION === * added a menu & a screen to see late issues attached to a bookseller. === CIRCULATION=== * In overdue list, Added some filter features : - filter on borrower firstname, surname or cardnumber. **This can be discussed and changed** - filter on borrowercategory - filter on itemtype - filter on branch - show all current issues. * Added a reserve management page in circulation module. It basically displays all the reservations not cancelled. * Adding a systempreference to notice the library before departure of a borrower. when borrower leaves the library in less than 'NotifiyBorrowerDeparture', the circulation desk shows it. === CATALOGUING === * as the MARC editor begins to be really heavy, i've also added a marc_hide systempref. It hides all marc features not requested by libraries that want MARC but not too much. It hides MARC tag & subfield code, reordering buttons as well as indicators. by default, hide_marc is off === OPAC === * by default, recent acquisitions are done on 30 days. * New systempreference : OpacPasswordChange if set to Yes (default) the user can change it's password. If set to No, he can't. Useful for libraries with LDAP auth, where the password is checked in LDAP, not in Koha, thus Koha can't change it === SERIALS === * ordering lists by biblio title * when adding a subscription and searching a biblio, you can filter on itemtype (useful as libraries usually have one or few itemtypes specific for serials) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

3 3

test
by Bruffey, Mark 16 Dec '05

16 Dec '05

Test once again; others see my posts, but I do not recv in outlook . . . . L. Mark Bruffey Director Library Services Central Baptist Theological Seminary 900 Forestview Lane N Plymouth MN 55441 763 417 8264 mbruffey(a)centralseminary.edu Central Seminary www.centralseminary.edu <http://www.centralseminary.edu/> Fourth Baptist Church www.fourthbaptist.org <http://www.fourthbaptist.org/> WCTS Radio AM 1030 Online www.centralseminary.edu/wcts *************************************** Have you experienced the good news? "Every one who calls on the name of the Lord will be saved!" [Romans 10:13] ***************************************

1 0

Perl-ZOOM is a GO!
by Joshua Ferraro 15 Dec '05

15 Dec '05

Hi everyone, I'm pleased to announce that the first public release of the ZOOM-Perl software, distributed as the Net::Z3950::ZOOM module, was released and uploaded to CPAN yesterday. Thanks to Index Data, and especially Mike Taylor for their hard work on this module over the past few weeks. With this software release, we're ready for the next phase of Zebra integration, which will include using the Perl-ZOOM API to perform OPAC and Cataloging functions on a Zebra database. If you'd like to get involved in this process, you'll want to read through the ZOOM-Perl documentation here: http://search.cpan.org/~mirk/Net-Z3950-ZOOM-1.00/lib/ZOOM.pod Most of what we'll be doing is search and retrieve clients using the ZOOM class, which looks something like this: use ZOOM; eval { $conn = new ZOOM::Connection($host, $port) $conn->option(preferredRecordSyntax => "usmarc"); $rs = $conn->search_pqf('@attr 1=4 dinosaur'); $n = $rs->size(); print $rs->record(0)->render(); }; if ($@) { print "Error ", $@->code(), ": ", $@->message(), "\n"; } and updating records, using the ZOOM::Package class, which looks something like this: $p = $conn->package(); $p->option(action => "specialUpdate"); $p->option(recordIdOpaque => 145); $p->option(record => content_of("/tmp/record.xml")); $p->send("update"); $p->destroy(); 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

2 1

Savannah News
by Joshua Ferraro 15 Dec '05

15 Dec '05

Hi everyone, Just a bit of news from Savannah, our project's code repository: <snip> Savannah CVS URL changed In our effort to better structure the Savannah system and get the necessary fundations for new features, all CVS-related services are moved to cvs.savannah.gnu.org and cvs.savannah.nongnu.org. You can use 'sv' instead of 'savannah' for short. cvs -z3 -d:ext:username@cvs.sv.gnu.org:/sources/project co module_name cvs -z3 -d:ext:username@cvs.sv.gnu.org:/web/project co module_name </snip> There are some other changes related to anonymous check-out as well as how CVS/diff emails are being generated, etc. If you'd like more details, visit: http://savannah.gnu.org/forum/forum.php?forum_id=4168 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