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

French sysprefs file encoding
by Jesse Weaver 16 Dec '08

16 Dec '08

Hello, I noticed that various patches to the systempreferences creation SQL script for French have been in the Latin-1 encoding. The base encoding for the file is UTF-8. I'm not sure how tolerant MySQL is of this, but it's very visibly broken in a Vim editing session. Not out to chop off heads, just thought everyone would want to know. -- Jesse Weaver Software Developer, LibLime

3 3

Koha 3 on Ubuntu Gutsy (7.10)
by Partha Mukhopadhyay 14 Dec '08

14 Dec '08

Dear all Let me share with you a success story. Today we are able to run Koha 3 on Ubuntu 7.10 Gutsy Gibbon with Zebra server on. It's working nicely and all modules are functional. The extent of improvements in Koha 3 is simply amazing. Hats off to you genius developers of team Koha. The installation guide (although quite helpful) available at Koha wiki (http://wiki.koha.org/doku.php?id=ubuntu_gutsy) needs to be modified slightly. I wrote down the modifications we did during the installation time. The document will be submitted to wiki within a week. Thanks and regards again to developers. Dr. Parthasarathi Mukhopadhyay Department of Library and Information Science University of Burdwan, Burdwan, West Bengal, India -- _______________________________________________ Search for products and services at: http://search.mail.com

2 1

More encoding issues
by Chadwick, John, DCA 13 Dec '08

13 Dec '08

Quick question concerning the following wiki page on encoding: http://wiki.koha.org/doku.php?id=encodingscratchpad. Some of the information in the wiki seems to be more applicable to MySQL 4.1 instead of 5.x Also, some of the suggested changes to modify tables seem to refer to tables that are not in Koha 3.0.1. Specifically, there is no table called marc_subfield_table. There is a marc_subfield_structure. There is no abstract in the table biblioitems. -- Convert the database default encoding to UTF-8 and default collate to utf8 ALTER DATABASE kohawipofinal DEFAULT CHARACTER SET utf8 DEFAULT COLLATE utf8_general_ci; -- change the table encoding type (varchar -> binary -> varchar ) for MARC Data alter table marc_subfield_table modify subfieldvalue BINARY(255); alter table marc_subfield_table modify subfieldvalue VARCHAR(255) CHARACTER SET utf8; -- change the table encoding type (text -> blob -> text ) for Koha Tables alter table biblio modify title BLOB; alter table biblio modify title TEXT CHARACTER SET utf8; alter table biblio modify author BLOB; alter table biblio modify author TEXT CHARACTER SET utf8; alter table biblio modify unititle BLOB; alter table biblio modify unititle TEXT CHARACTER SET utf8; alter table biblio modify notes BLOB; alter table biblio modify notes TEXT CHARACTER SET utf8; alter table biblio modify seriestitle BLOB; alter table biblio modify seriestitle TEXT CHARACTER SET utf8; alter table biblio modify abstract BLOB; alter table biblio modify abstract TEXT CHARACTER SET utf8; alter table biblioitems modify abstract BLOB; alter table biblioitems modify abstract TEXT CHARACTER SET utf8; That should do it for now. John +----------------------------------------------------------------------- -----+ John Chadwick, Ed.D. Information Technology Manager New Mexico State Library 1209 Camino Carlos Rey Santa Fe, NM 87507 Phone: 505-476-9740 Cell: 505-629-8116 Fax: 505-476-9761 john.chadwick(a)state.nm.us http://www.nmstatelibrary.org Confidentiality Notice: This e-mail, including all attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited unless specifically provided under the New Mexico Inspection of Public Records Act. If you are not the intended recipient, please contact the sender and destroy all copies of this message. -- This email has been scanned by the Sybari - Antigen Email System.

1 0

TMPL_VAR default
by Joe Atzberger 11 Dec '08

11 Dec '08

Nahuel's recent patch for "no title" reminded me of something. I don't think there is any problem with the patch, but I wanted to bring up the use of TMPL_VAR DEFAULT attribute, like:  I like the way that looks. But am I remembering correctly that there is some flaw in the translation system that impedes our use of this rather useful feature? If so, can anyone say more specifically what the problem is? That should be regarded as a bug worth fixing, and not some natural limitation that we just have to work around. I'm willing to attempt it if anybody can narrow the problem down. --Joe Atzberger

3 2

Koha 3.00.00 on Debian Sid - Install Report.
by Mahesh T. Pai 11 Dec '08

11 Dec '08

First, I am not subscribed, So any questions should be cc'ed to me. And apologies for cross posting - I cannot figure out which list this should be sent to. I got the system at around 6 PM last Saturday, and finished the job today (11th) morning - around 11 AM. OS install + Koha configuration took a mere 5 days. The OS installation was a battle, which ended only on Tuesday morning. I will not bother the list with details. Suffice it to say that the fault certainly was not Debian's. My ISP was corrupting the .iso files I was downloading. :-( The OS was Debian Sid/Unstable amd64 on a Intel D processor. That is all I needed to know about the hardware. Pristine install using debootstrap, and other packages added after rebooting from that install. Koha debian packages came from git.debian.org, (see the comments on http://blog.bigballofwax.co.nz/2008/08/05/koha-3-packaging/) "deb http://apt.workbuffer.org/ intrepid all" Is the line I had to add to /etc/apt/sources.lst. The packaging was buggy, but they got the dependencies right. Every dependency was fixed properly. The .debs failed to create sub directories under /etc/koha/ - a serious problem. I had to create the directories manually, and then do a "dpkg -i /var/cache/apt/archive/koha-<whatever>.deb" manually. Easy, eh?? It took me 3 days to sort out problems reaching the koha web-install page. I had the following lines in /etc/hosts 127.0.0.1 localhost library 127.0.0.2 librarian.koha 127.0.0.3 catalog.koha. "Catalog" is easier to remember than "OPAC", right? Since it was intended to be a stand alone system, I was tempted to leave out port 8080 part in apache2 configuration, but decided that the people who use it (there is a strong community of librarians here who are well aware of koha) may get confused with absence of 8080 in the URL. All the problems have been already reported on this (or -devel) lists, and googling was quick to give answers. But that it took 3 days means there were several problems. First was failure of the install scripts to put the table's names, user name, and password into the /etc/koha/koha-config.xml file. And there is some directive in koha-config.xml which put the "method to access the database as "sql". It ought to have been "mysql". Once this was sorted out, the catalog page would load, saying that the server is down for maintenance. But the web install refused to come up, complaining of some fatal error. This meant I had to manually install CGI::session from the tarball on cpan, as already mentioned in one of the lists. CGI::session I manually installed was same as the version in Debian. Guess this should go int INSTALL.debian file. Except the database configuration, I guess everything else in that file could be handled by debian installer, IMHO. Rounded off the install with a simple index page in /var/www/ with links to http://librarian.koha:8080 and http://catalog.koha. Further problems with the debian packages (snd some with koha itself). 1. Cid not create the cron jobs. (I did not realise it, till after I handed over the system. What are the consequences?) 2. I guess Debian packages does not create the appropriate files in /etc/init.d/ for the idzebra daemon. The koha-zebraqueue--ctl.sh is invoking the "daemon" binary, but debian uses start-stop-daemon binary. Hope things will run. I installed koha-idzebra-server package; not the koha-basic one. The work around was to NOT specify to use zebra for indexing. 3. What is the difference between marc21 and unimarc? Librarians would know it; but not poor souls like me, who would be doing the software installation. A description of both in the web installer would help; I chose marc21. 4. What happens if I abort the webinstaller? Some clues on the web installer pages would be nice. BTW, I did this free as in "free beer" for a friend of mine, at a law school with a mere 5K volumes. ;-) And I will write about the OS install elsewhere. -- Mahesh T. Pai || http://paivakil.blogspot.com REVOLUTION, n. An abrupt change in the form of misgovernment.

1 0

Re: [Koha-devel] [Koha-translate] String freeze for 3.0.1
by Henri-Damien LAURENT 11 Dec '08

11 Dec '08

Zeno Tajoli a écrit : > Hi to all, > > At 22.55 24/11/2008, Henri-Damien LAURENT wrote: >> Hi, >> I am glad to announce String Freeze for 3.0.1. > > we are starting to update our transaltion with the present > version of 3.0.x > The git web repository is > http://git.koha.org/cgi-bin/gitweb.cgi?p=Koha;a=shortlog;h=3.0.x ? > The last update was at 2008-10-28 ? > > Bye > > Zeno Tajoli > CILEA - Segrate (MI) > tajoliAT_SPAM_no_prendiATcilea.it > (Indirizzo mascherato anti-spam; sostituisci quanto tra AT con @) > > Hi I had no time to answer back before and wanted to check things with Chris. It seems that it was my job to update po files, and send them on to git. I had rather not do it and leave it up to you to update your translation files, since I happened to have some tricks with UTF8, as you might have. Any way, I just pushed all the po files as base for translation, hopefully you have not waited solution from git all that time and went to Kohadocs to see how to update translations ;) But, anyway, git po files are now up to date. git fetch will get you translation base for 3.0.1 I will try and be more reactive next time. But if such a thing should reproduce one day, tmpl_process3.pl (in misc/translator) is the script to begin a translation, to update, and to install a translation on your Koha box : tmpl_process3.pl create -r -s po/mypofilestaff.po -i ../../koha-tmpl/intranet-tmpl/prog/en tmpl_process3.pl create -r -s po/mypofileopac.po -i ../../koha-tmpl/opac-tmpl/prog/en To update : tmpl_process3.pl update -r -s po/mypofilestaff.po -i ../../koha-tmpl/intranet-tmpl/prog/en tmpl_process3.pl update -r -s po/mypofileopac.po -i ../../koha-tmpl/opac-tmpl/prog/en To create the translated strings from your po tmpl_process3.pl install -r -s po/mypofilestaff.po -i ../../koha-tmpl/intranet-tmpl/prog/en -o ../../koha-tmpl/intranet-tmpl/prog/mylanguage Make sure you have Locale::PO installed on your box. Sorry for delay. -- Henri-Damien LAURENT

2 1

Re: [Koha-devel] State of the debian packaging
by Vincent Danjean 08 Dec '08

08 Dec '08

I forgot the CC -------- Original Message -------- Subject: Re: [Koha-devel] [Koha] Wrong SAX Parser - does it matter? -> impact on Debian packaging Date: Sun, 07 Dec 2008 09:31:03 +0100 From: Vincent Danjean <vdanjean.ml(a)free.fr> To: Chris Cormack <chris(a)bigballofwax.co.nz> References: <003401c94446$b2fb8f80$18f2ae80$@edu> <23FC99CE-5792-4BD2-BBBC-09EFD0FE6790(a)biblio.org> <DD1D2ACF-3F3D-49EA-A9DB-988574B11329(a)gmail.com> <491DDBD2.3090202(a)free.fr> <606aab810812062322p2738f2eat8eda17dc0640c99c(a)mail.gmail.com> Chris Cormack wrote: > Hi Vincent > > Is the below issue still a problem? This issue is still problematic (ie I do not know the answer and a good packaging cannot modify a (not owned) global configuration file) Other problem I got are config files in general. The same config file is used by several packages so I must design config and postconf script to deal with this. You can see my current state here : http://git.debian.org/?p=collab-maint/koha.git;a=shortlog;h=refs/heads/wip (not in a usable state as I just started to rewrite the management of conffig file....) If you have some remarks about the packaging splitting, I would be glad to get some feedback. http://git.debian.org/?p=collab-maint/koha.git;a=blob;f=debian/control;hb=w… > I was wondering what I could do to > help you finish the packaging. > I work with a couple of Debian Developers and Francois was telling me > on friday that if we get the packaging finished soon, that although we > have missed lenny, if its done before january we might get it into the > next ubuntu release. > > If you havent had an answer on the below question let me know and I'll > go find the answer for you Ok, if you can test if koha works with current expat parser, it will help. I you kwow koha, telling me which config file is needed by which program would also be a good thing. The idea is to be able to answer to the question: Which config file (and which values will be read in it) do I need on each machine A, B and C if I want to setup: - koha opac and intranet on machine A - zebra server on machine B - pazpar2 server on machine C And which crontab/script do I need to run on each of these machines. I CC koha-devel in case someone else can answer these questions. Best regards and thanks for for help Vincent > CHris > > On Sat, Nov 15, 2008 at 9:13 AM, Vincent Danjean <vdanjean.ml(a)free.fr> wrote: >> [moving from koha to koha-devel due to my questions] >> >> Mason James wrote: >>> On 2008/11/12, at 11:56 AM, Brendan Gallagher wrote: >>>> Did you try editing ParserDetails.ini >> What I do not understand is why koha is requiring to modify such >> a global configuration file. >> >> Is this setup really still required ? Were not the bugs from the >> expat filter fixed ? I do not know at all why this parser is/was needed, >> but Expact seems to work for the test case in koha scripts : >> vdanjean koha/misc$ ./sax_parser_print.pl >> XML::SAX::Expat=HASH(0x115c4f0) >> vdanjean koha/misc$ ./sax_parser_test.pl >> é >> vdanjean koha/misc >> ) >> >> By the way, this kind of requirement is really a bad thing (with my >> hat of trying to make a official Debian package) => it will be NOT >> possible at all that the koha package modifies the global configuration >> file. >> However, I really do not understand why, if the SAX parser is really >> needed, it is not required in the koha code itself. >> >> For example, I tried to add as the first line in sax_parser_print.pl >> and sax_parser_test.pl the line: >> $XML::SAX::ParserPackage = "XML::LibXML::SAX"; >> (tip found in the doc of XML::SAX::ParserFactory) >> Without changing my global configuration file, sax_parser_print.pl >> now report XML::LibXML::SAX. >> >> I failed to see where koha really instantiate a sax parser. >> 'rgrep "use XML::SAX" koha/' does not return anything (but >> sax_parser_print.pl and sax_parser_test.pl). >> >> Perhaps, koha gurus can know where SAX parser are used and add >> the line requesting the particular parser if it is still needed ? >> >> Regards, >> Vincent >> >> -- >> Vincent Danjean GPG key ID 0x9D025E87 vdanjean(a)debian.org >> GPG key fingerprint: FC95 08A6 854D DB48 4B9A 8A94 0BF7 7867 9D02 5E87 >> Unofficial pacakges: http://www-id.imag.fr/~danjean/deb.html#package >> APT repo: deb http://perso.debian.org/~vdanjean/debian unstable main >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel(a)lists.koha.org >> http://lists.koha.org/mailman/listinfo/koha-devel >> > -- Vincent Danjean Adresse: Laboratoire d'Informatique de Grenoble Téléphone: +33 4 76 61 20 11 ENSIMAG - antenne de Montbonnot Fax: +33 4 76 61 20 99 ZIRST 51, avenue Jean Kuntzmann Email: Vincent.Danjean(a)imag.fr 38330 Montbonnot Saint Martin

6 10

Fw: Koha Hindi translation
by Krishnan Mani 08 Dec '08

08 Dec '08

Sorry to intrude, but i am sending this out to the dev list to check if anyone knows who's running the translate list. i sent the e-mail below to the translate list on 1st December, then wrote to the list admin on the 4th, but haven't received a response yet. BTW, i can volunteer to run the translate list. Thanks and regards, krishnan mani Pune, India --- On Mon, 1/12/08, Krishnan Mani <krishnanm75(a)yahoo.com> wrote: From: Krishnan Mani <krishnanm75(a)yahoo.com> Subject: Koha Hindi translation To: koha-translate(a)nongnu.org Date: Monday, 1 December, 2008, 11:58 PM Hello, i'd like to contribute a Hindi translation for Koha, and i don't think this is already listed at the Koha translation manager site. i request the admin to kindly add the same (as indicated on the home page) Thanks and regards, krishnan mani Pune, India Add more friends to your messenger and enjoy! Invite them now. Add more friends to your messenger and enjoy! Go to http://messenger.yahoo.com/invite/

2 2

String freeze for 3.0.1
by Henri-Damien LAURENT 07 Dec '08

07 Dec '08

Hi, I am glad to announce String Freeze for 3.0.1. Translators, you have 3 week time for translations. It should be only differences from 3.0.0 But strings Normalization sometimes did many tiny changes. Sorry about that. Chris will tell you more about Pootle site that will allow good translations. Let me know if you encounter any problem. Hopefully, christmas will bring us 3.0.1 release. ;) -- Henri-Damien LAURENT

6 7

Why contribute to Koha?
by Baytiyeh, Hoda 05 Dec '08

05 Dec '08

Hello, I am a Ph.D. candidate in Instructional Technology at the University of Tennessee. My dissertation focuses on what motivates people to contribute to F/OSS projects. Though it may seem obvious to you, many non-programmers are still suspicious of OSS and think there must be a catch. Can you help me to demonstrate why talented programmers are willing to work for free? My survey should take no more than 15 minutes and asks for no identifying information. Please click on the following link to take the survey. If you are interested in the results of the survey, please send me a message. This is my second request for participation; if you responded already, please ignore this request. http://ubiquity.utk.edu/limesurvey/index.php?sid=45871&lang=en <BLOCKED::http://ubiquity.utk.edu/limesurvey/index.php?sid=45871&lang=en > Your help is highly appreciated. Thanks, Hoda Baytiyeh. hodabn(a)utk.edu <BLOCKED::mailto:hodabn@utk.edu>

3 2