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

Re: [Koha-devel] are month names translatable in opac?
by Owen Leonard 26 Feb '04

26 Feb '04

> I wonder whether the names for months (in > reserves) are translatable, If I understand you correctly, then YES, they are translatable. The months are listed like this in opac-reserve.tmpl: <option value="2">Feb</option> The translatable string is 'Feb' (February), and the value="2" indicates the 2nd month of the year. Changing 'Feb' won't affect how the date gets stored. -- Owen

1 0

a bug in reserves.pl?
by Benedykt P. Barszcz 26 Feb '04

26 Feb '04

Hi All, Whenever I press the reserve button from within the default intranet theme, the options>> line plus other characters on page currently displayed loose their charset definition and browser defaults to iso-8859-1 ! Please help, it is causing lot's of trouble. Page source from within browser, however, is showing <title>KOHA: INTRANET: Catalogue</title> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> Benedict

1 0

what's (wk) and (hm)?
by Benedykt P. Barszcz 26 Feb '04

26 Feb '04

As in the subject... Benedict

1 0

What's Current Loan
by Benedykt P. Barszcz 26 Feb '04

26 Feb '04

Hi, Sorry, but I do not understand what it is. Could anyone enlighten me? If it says YES, does it mean an item is unavailable? If No, an item is in stock? Benedict

1 0

are month names translatable in opac?
by Benedykt P. Barszcz 26 Feb '04

26 Feb '04

Hi, I wonder whether the names for months (in reserves) are translatable, i.e. whether they take part in mysql transaction. If so, Polish equivalents would spoil the output, am I correct? Benedict

1 0

Koha 2.0.0 release date
by paul POULAIN 26 Feb '04

26 Feb '04

Hi dev, The next release will be called "2.0.0", without anything after. "Why" may you ask ? For at least 2 reasons : * The 2.0.0RCx is used in at least 10 libraries around the world. * Here in France, ppl speak of Koha 2.0.0 as "it will provide full MARC support", "it will do...", "it will be...". This future has to be removed : "Koha 2.0.0RCx provide MARC support". So, i'll call the next release 2.0.0 The date ? When polish & chinese translations are ready. I also plan to change a little my release notes. The "bug fixed" will have only bugs fixed. The "improvement" will include a warning. I wrote release_notes_200.txt. It's something like this : /BUGS FIXED: major : * #662 : missed prepare(?) in supplier.pl * french only : fixed total cost calculation bug in order line (due to translation error) * #436 : circulation.pl partially templated * #606 : ***** PORT FROM HEAD BEFORE RELEASE * #679 : OPAC doesn't allow linking of subject headings minor : * isbnsearch now shows correctly the total number of books in DB * value_builder textarea dropped to 5 lines instead of 10 * 20 values in authorised_value admin screen instead of only 5 * opac, css template : inputs now in light blue, to see them better. Added 5px bottom margin & fixed a bug in IE * fixed bad management of ' in supplier title * request link not shown if item is notforloan * branchcode field max size set to 4 in editor , as in the DB (was 3) * #719 : input box too short for Library name in syspreferences IMPROVEMENTS : FEATURES HERE ARE CONSIDERED AS "NEW". They seem to work, but are for the 1st time in a public release. * printing the biblio is now possible from the item screen * POLISH translation * CHINESE translation/ -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

the meaning of a "biblio" in Koha
by Benedykt P. Barszcz 26 Feb '04

26 Feb '04

Hi Group, In opac-moredetail.tmpl there's a GROUP - section where it says: "Biblionumber", and in a BARCODE section "Biblio number:" Are the two different? Also is the meaning for it like in bibliogrphic record (MARC for example)? Benedict

2 1

npl intranet
by Benedykt P. Barszcz 25 Feb '04

25 Feb '04

I am pasting this for Owen to have a look at it in his spare time. Perhaps there are some thing to be changed in the npl intranet template? Benedict xgettext.pl: Warning (negligible): acqui-home.tmpl: line 46: Suggest ESCAPE=URL for TMPL_VAR in attribute "for": "" xgettext.pl: Warning: acquire.tmpl: line 82: Strange attribute syntax: ="" xgettext.pl: Warning: modbibitem.tmpl: line 88: Probably missing whitespace before or missing quotation mark near: amp;bib="TMPL_VAR Name="biblionumber">"amp;bi="TMPL_VAR Name="biblioitemnumber">" xgettext.pl: Warning (negligible): opac-main.tmpl: line 54: Unquoted attribute contains character(s) that should be quoted: +2 xgettext.pl: Warning (negligible): opac-main.tmpl: Further similar negligible warnings will not be reported, use --pedantic for details xgettext.pl: Warning: additem-nomarc.tmpl: line 174: SGML "closed start tag" notation: <input name="lccn" size="40"< xgettext.pl: Warning: detail-opac.tmpl: line 63: Probably missing whitespace before or missing quotation mark near: itemnumber xgettext.pl: Warning: AcceptMarcUpload.tmpl: line 25: Possible SGML "closed start tag" notation: <input type="hidden" name=menu value=< xgettext.pl: Warning: AcceptMarcUpload.tmpl: line 27: SGML "closed start tag" notation: <input type="hidden" name=menu value= Name this set of MARC records: < xgettext.pl: Warning: aqbookfund.tmpl: line 49: Probably missing whitespace before or missing quotation mark near: value="Add bookfund" class="submit" xgettext.pl: Warning: categoryitem.tmpl: line 258: Probably missing whitespace before or missing quotation mark near: script_name">" method="post" xgettext.pl: Warning: categoryitem.tmpl: line 293: SGML "closed start tag" notation: </t$ < xgettext.pl: Warning: marc_subfields_structure.tmpl: line 65: Possible SGML "closed start tag" notation: <form action=" method="post"><input type="hidden" name="tagfield" value="< xgettext.pl: Warning: marc_subfields_structure.tmpl: line 65: Unrecognizable token found: (too confused to show details) The create seems to be successful.

1 0

More... stuff (fwd)
by Pat Eyler 24 Feb '04

24 Feb '04

This looks like it would be an awesome bit for koha using libraries, if it could work with MySQL (even more so if we ever do get PostgreSQL capable). Anyone interested in taking a look and maybe lending David a hand? -pate Pat Eyler Kaitiaki/manager migrant Linux sys admin the Koha project ruby, shell, and perl geek http://www.koha.org http://pate.eylerfamily.org ---------- Forwarded message ---------- Date: Tue, 24 Feb 2004 14:49:06 -0600 From: David Christensen <DChristensen(a)westman.wave.ca> To: perl4lib(a)perl.org Subject: More... stuff Hi all, I've been working on building a cataloguing utility, currently under the working name "ALEX", but I'll be changing that so as not to conflict with Eric Lease Morgan's "Alex Catalogue of Electronic Texts" . There's a few parts to it: ALEX-DB: a database abstraction layer. Currently works with PostgreSQL. (there is an example of using Tk::MARC in the pl/ directory) ALEX-Import: a Perl/Tk widget for slurping MARC files into ALEX-DB ALEX-Search: a Perl/Tk widget for searching ALEX-DB This isn't actually a full-blown application, yet. But the tools are coming along nicely :-) If anyone is interested in playing with it, you can grab the modules from: http://home.westman.wave.ca/~dchristensen/index.html I would certainly appreciate any comments or questions :-) -David

1 0

z3950 search problems
by Sullivan,Deric [CMC] 24 Feb '04

24 Feb '04

Hi, I've had a problem with the z3950 search client and I've noticed that others have had a similar problem. It's the problem where the database connection is lost and reported in one of the log files. Here's what I did to get rid of the symptoms. I'm not a Koha expert, nor a Perl expert, and I usually use PostgreSQL instead of MySQL so I make no guaranties that this fix is correct, but it does stop processz3950queue from complaining the way it did and it seems to make sense that a forked process that terminates should not be using, in the default fashion, any handles that the parent process is relying on. The forked process used a new name ($dbi) for the handle, but it was the same handle. Although even using "my $dbi = C4::Context->new_dbh" instead of "my $dbi = C4::Context->dbh" would not have worked since the child still keeps the reference to the parents handle (because it was created before the fork) and this handle would be destroyed when the child terminated. At least that's how I see it. There are probably other problems because even after these modifications, the search client still did not seem to work. Replace: my $dbi = C4::Context->dbh; with: $dbh->{"InactiveDestroy"} = "true"; Replace all references to dbi with dbh. Deric The views expressed here are mine and do not reflect the official position of my employer or the organization through which the Internet was accessed.

1 0