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

Z39.50 daemon launcher incompatible with FreeBSD
by Thomas D 20 Jun '05

20 Jun '05

20 June 2005 Communicating with the original poster confirmed that this issue was never resoved. Will this be fixed in time for 2.2.3RC? Koha should not require a switch not supported by the Free BSD su command. Programmers should not use switches that are not universally supported if that can be avoided The original thread is quoted below Thomas D ------------------------------------------- Date: Sat Apr 2 15:20:23 NZST 2005 From: "Karl Agee" <kdagee2(a)yahoo.com> Subject: [Koha] question launching z3950 daemon To : koha(a)lists.katipo.co.nz ------------------------------------------- Well, I found out what is going on. The script is calling a shell for the z3950 daemon: su -s /bin/sh -c $KohaZ3950Shell - $RunAsUser & and my version of su in freebsd doesnt support that option (-s). How would I modify the script so that it does??? Does the program need it???? --karl --- Karl Agee <kdagee2 at yahoo.com> wrote: > > --- Stephen Hedges <shedges at skemotah.com> wrote: > > Karl Agee said: > > > 1) when lauching like this: > > > > > > -su-2.05b# > > > > > > /usr/home/kdagee/koha-2.2.1/scripts/z3950daemon/z3950-daemon-launch.sh > > > > Nope, that won't work. That's the location of > your > > unzipped download, not > > the location of your Koha install. > > 8-D silly me. > > > > > > > 2) when launching like this: > > > > > > # > > > > > > /usr/local/koha/intranet/scripts200503291957/z3950daemon/z3950-daemon-launch.sh > > > > > > I get: > > > > > > b# > > > > > > /usr/local/koha/intranet/scripts200503291957/z3950daemon/z3950-daemon-launch.sh > > > -su-2.05b# su: illegal option -- s > > > usage: su [-] [-flm] [-c class] [login [args]] > > > > Looks like your shell thinks you typed in "su -s" > -- > > for some reason. > > But don't you have a > > /usr/local/koha/intranet/scripts directory? The > > date > > after the "scripts" (scripts200503291957) > indicates > > that it's a backup > > from a previous install and not your current > > install. > > -su-2.05b# locate z3950-daemon-launch.sh > /usr/home/kdagee/koha-2.2.0/scripts/z3950daemon/z3950-daemon-launch.sh > /usr/home/kdagee/koha-2.2.1/scripts/z3950daemon/z3950-daemon-launch.sh > /usr/local/etc/rc.d/z3950-daemon-launch.sh > /usr/local/koha/intranet/scripts/z3950daemon/z3950-daemon-launch.sh > /usr/local/koha/intranet/scripts200503291957/z3950daemon/z3950-daemon-launch.sh > > # cd /usr/local/koha/intranet/scripts/z3950daemon > > -su-2.05b# ls > processz3950queue z3950-daemon-options > z3950-daemon-launch.sh z3950-daemon-shell.sh > > -su-2.05b# ./z3950-daemon-launch.sh > -su-2.05b# su: illegal option -- s > usage: su [-] [-flm] [-c class] [login [args]] > > -su-2.05b# sh z3950-daemon-launch.sh > -su-2.05b# su: illegal option -- s > usage: su [-] [-flm] [-c class] [login [args]] > > > -su-2.05b# cd ~ > > -su-2.05b# > /usr/local/koha/intranet/scripts/z3950daemon/z3950-daemon-launch.sh > -su-2.05b# su: illegal option -- s > usage: su [-] [-flm] [-c class] [login [args]] > > > ok, so, why would bash give me this error? I've > never > seen it before. I get this if I put the startup > scripts folder (via a soft link) as well. > > only thing I can think of: > > -su-2.05b# ls -la > /usr/local/koha/intranet/scripts/z3950daemon/z3950-daemon-launch.sh > -rwxr-xr-x 1 www www 2750 Mar 29 19:57 > /usr/local/koha/intranet/scripts/z3950daemon/z3950-daemon-launch.sh > > user/group www is the apache user......is this > correct? > > The only thing I see in the page source is a > reference > to a javascript thing for z3950. Does this launch > the > daemon? > > --karl > > > > __________________________________ > Do you Yahoo!? > Yahoo! Personals - Better first dates. More second > dates. > http://personals.yahoo.com > > _______________________________________________ > Koha mailing list > Koha at lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha > __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/ --------------------------------------------- Protect your mails from viruses thanks to Alinto Premium services http://www.alinto.com

2 1

MARC import fails when no ISBN present 2.2.2b
by Thomas D 20 Jun '05

20 Jun '05

20 June 2005 I cannot import MARC recorrds for books without ISBNs using the current stable release, 2.2.2b. Most of the books that ever were have no ISBNs and never will. Attempting to import a MARC communications format one record file without ISBNs fails returning the following message whether or not overwrite duplicates is selected in the import form. "MARC acquisition system Import into the reservoir Import results : * 0 imported records * 1 not imported because already in catalog * 0 not imported because already in the reservoir * 0 not imported because they seem not to be in MARC format (or ISBN/ISSN missing) ! * 1 records parsed" The same function works correctly using the LibLime Koha 2.2.1 demonstration version for importing the identical file. No related messages appear in the error log. How can I correct and/or work around this problem? Thomas D --------------------------------------------- Protect your mails from viruses thanks to Alinto Premium services http://www.alinto.com

1 0

head probably broken...
by Paul POULAIN 20 Jun '05

20 Jun '05

Hello, i'm synch'ing head with 2.2.3 fixes & improvements. don't be surprised to see problems and/or lot of commits... -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Searching Meeting and CQL!!
by Joshua Ferraro 20 Jun '05

20 Jun '05

Hi everyone, Just a friendly reminder that our Searching Group Meeting is to be held tomorrow (Tuesday, June 21) at 19:00GMT. For the time in your area please see: http://tinyurl.com/79lgf I've added a couple of things to the Wiki meeting agenda: http://www.saas.nsw.edu.au/koha_wiki/index.php?page=AgendAndNotes05jun21 Among them is mention of CQL, Common Query Language: http://www.loc.gov/z3950/agency/zing/cql/ I'll be pushing CQL for Koha as it looks to be the most innovative searching method happening for libraries. If you get a chance to read anything before the meeting I'd recommend taking a look at the link above. Cheers, -- Joshua Ferraro VENDOR SERVICES FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Koha ILS, Mambo Intranet, DiscrimiNet Filter jmf(a)liblime.com | Full Demos at http://liblime.com | 1(888)KohaILS

2 2

order of koha versions on sourceforge
by Rachel Hamilton-Williams 20 Jun '05

20 Jun '05

Hi I went to see someone who'd accidentally downloaded the older version of Koha, I think because it's first in the list on the sourceforge site... http://sourceforge.net/project/showfiles.php?group_id=16466 Do we need both "koha' and "koha2.2" as what looks like seperate products? Could we not just have the 2.2 series under "koha" then it would go to the top? Cheers R -- ----------------------------- Rachel Hamilton-Williams General Manager Katipo Communications Ltd Phone: +64-4-934 1285 Mobile: 021 389 128 E-mail: rachel(a)katipo.co.nz Web: www.katipo.co.nz

3 2

koha 2.2.3 ?
by Rachel Hamilton-Williams 20 Jun '05

20 Jun '05

Hi guys, I've just been to visit a local school who'd managed to install koha 2.0 rather than 2.2.2 - and I was recommending she upgrade - but wondered if 2.2.3 was out/going to be out this week in which case she could hold off for a few more days cheers rachel -- ----------------------------- Rachel Hamilton-Williams General Manager Katipo Communications Ltd Phone: +64-4-934 1285 Mobile: 021 389 128 E-mail: rachel(a)katipo.co.nz Web: www.katipo.co.nz

2 1

Dependency versions and special patches
by Jared Camins-Esakov 19 Jun '05

19 Jun '05

Hello all. I have begun working on a FreeBSD port of Koha, and I had a couple of questions that I thought I would submit to your combined wisdom. 1) Are there any patches for the latest Koha release (2.2.2b) that might need to be applied depending on the version of any of Koha's dependencies? As an example, I seem to recall seeing in the mailing list archives that there was some discussion about improvements to the OPAC search that required MySQL 4.1; in that case, a patch might be required to make Koha work with MySQL<4.1. 2) Are there any patches for Koha that can be applied to the latest release (2.2.2b) for features that are often required, but not a part of the main Koha distribution? 3) Are there any security issues currently outstanding on the latest release, and are there any patches for them? Thanks in advance. -- Jared Camins-Esakov -- Jared Camins-Esakov E-mail: camins2(a)tcnj.edu

1 0

Koha 2.4 Searching Group Meeting
by Joshua Ferraro 17 Jun '05

17 Jun '05

Hi all, Francois-Laurent, Paul, slef, and chris and I have settled on a time for the Koha 2.4 Searching Group Meeting. Tuesday June 21 at 19:00GMT. To see the time in your area visit: http://tinyurl.com/79lgf If you'd like something to be included on the agenda please add it to the wiki under the meeting agenda section: http://www.saas.nsw.edu.au/koha_wiki/index.php?page=AgendAndNotes05jun21 Hope to read you at the meeting. -- Joshua Ferraro VENDOR SERVICES FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Koha ILS, Mambo Intranet, DiscrimiNet Filter jmf(a)liblime.com | Full Demos at http://liblime.com | 1(888)KohaILS

2 1

Re: Re[2]: [Koha-devel] Charsets: Moving to utf-8
by Mathew 16 Jun '05

16 Jun '05

> - all translations are stored within a database table, then have > the template lookup any static text (text generated from within > Perl, can be translated before being sent to the templates. I think this is not a good idea. Read why: > > - since templates lookup their own translations, you dont need a template-per-language. > > I'd prefer a template per language. Often the syntax is different in > different languages. With one template per language you can build > phrases, which mix static text with database generated text correctly > for every language. you could mix static text and database text, but why have seperate places for the text storage? > > - since translations are stored within a database, you can update > > the translations at run-time, without needing to restart / reload > > your updated translations > > We don't have to restart/reload right now. Most language translations are based on using .po files, such that when the file modification stamp is modified, the file gets reloaded. The problem with that is that each Apache instance will load a seperate copy of the translations, unless there is a mechanism to use a global map. > > - web access to the database translations allow multiple people > > to localise the translations, at the same time. > > What do you mean with "localise the translations"? When you give a template in one language, to the person do the translation, they are said to "localise the template to their langauge" which includes variations due to region, ie en_AU, en_US, en_GB, vs. jsut creating translations in the en language. > I think CVS does this job too. I'm suggesting that you can get a translator to translate the text strings, a) without them needing to understand how to use html, b) so that they use the same tool - the web browser - to update the text strings. > > - right-to-left text is also easily supported > > This is primary a point of coding. Not only. If you use an arabic website, the menu's are on the RHS side of the page - no primary within unicode, allows you to format you menus on the RHS of the browser. > The correct formatting of such text can be controlled better by one > template per language. Having done it both ways (we origonally had seperate templates per language), and now with a single template, we have seen exactly zero cases where a language specific template was needed. That said, we have need some variations with CSS styles. > > To do some of these, we modified HTML::Template to suport custom > > TMPL_xxx tags, so that we could implement a tag for the static text > > lookup. ie: our templates look like: > > You modified the original module? yes > What about upgrades? We merge the changes, then we put the new release on the website. I have email Sam Tregar a few times - most of the changes that we have developed, he is simply not interested in. For example, we enabled support for TMPL_ELSIF simply because we often use: <TMPL_IF ...> ... <TMPL_ELSE> <TMPL_IF ... ... <TMPL_ELSE> <TMPL_IF ... .... <TMPL_ELSE> ... </TMPL_IF> </TMPL_IF> </TMPL_IF> we can now do: <TMPL_IF ...> ... <TMPL_ELSIF ...> ... <TMPL_ELSIF ...> ... <TMPL_ELSE> </TMPL_IF> which is just so much cleaner - and the ELSIF's can be EXPR's too. > > We combine H::T with the Locale::MakePhrase module so that the > > output can handle singular / plural / etc based on the > > string/numeric value of some_var. > > This could be interesting for some words or phrases, but it can't > provide the flexibility of a template. Can I ask, did you have read through the Locale::MakePhrase documentation, and the documentation that it references? Sure, a template gives you ultimate flexibility. It also gives you the ability for templates to get out of sync, which is what our biggest problem was -> each time we made an enhancement, the templates needed to re-synced with the master, thus everly language other then english (our master languge) always lagged. cheers, Mathew

1 0

Re: [Koha-devel] Charsets: Moving to utf-8
by Mathew 16 Jun '05

16 Jun '05

Hi, I dont respond often on this list, but I thought the following information may be useful... > OK ... during the bugsquash session the issue of charsets came up. > (in response to 885:; Non-ISO8859-1 charset support broken in CSS > theme in 2.2). Our goal for 2.4 would be to move everything--db > storage, and templates -- to utf-8. The question is, how? [snip] > So we're looking for suggestions on how to make the switch. What do > we need to consider: > > HTML::Template limitations (should we be looking at Template::Toolkit) > Database Issues > Translation Issues > Other stuff At my work we provide a browser-based application which is translated into a number of languages. Some of the interesting points: - we only support UTF8 as the charset, as any other charset in simply insufficient (Google does this too). - all translations are stored within a database table, then have the template lookup any static text (text generated from within Perl, can be translated before being sent to the templates. - since templates lookup their own translations, you dont need a template-per-language. - since translations are stored within a database, you can update the translations at run-time, without needing to restart / reload your updated translations - web access to the database translations allow multiple people to localise the translations, at the same time. - right-to-left text is also easily supported To do some of these, we modified HTML::Template to suport custom TMPL_xxx tags, so that we could implement a tag for the static text lookup. ie: our templates look like: ... <TMPL_CATGETS "A phrase containing a template variable [_1], that gets inserted here",some_var> ... where some_var is a Perl generated TMPL_VAR value. We combine H::T with the Locale::MakePhrase module so that the output can handle singular / plural / etc based on the string/numeric value of some_var. For some extra information, go here: http://members.optusnet.com.au/mathew Hope this helps, Mathew PS. Some languages, particularily Asian languages, contain many pen-strokes within a glyph. Often these languages need the text point-size to be slightly larger than European languages... this is just a tidbit that I have found through experience, particularily if a single template is to be used for every language.

2 1