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

[Bug 120] subject search with apostrophe in it (ie NISGA'A) does not work.
by bugzilla-daemon＠wilbur.katipo.co.nz 08 Nov '02

08 Nov '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=120 ------- Additional Comments From tonnesen(a)cmsd.bc.ca 2002-11-09 06:01 ------- Author searches with apostrophes also are not working. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 120] New: subject search with apostrophe in it (ie NISGA'A) does not work.
by bugzilla-daemon＠wilbur.katipo.co.nz 08 Nov '02

08 Nov '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=120 Summary: subject search with apostrophe in it (ie NISGA'A) does not work. Product: Koha Version: 1.2.3 Platform: PC OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Catalogue AssignedTo: chris(a)katipo.co.nz ReportedBy: tonnesen(a)cmsd.bc.ca QAContact: koha-devel(a)lists.sourceforge.net ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

Re: [Koha-devel] Koha's i18n & l10n (fwd)
by Pat Eyler 06 Nov '02

06 Nov '02

oops, i should have sent this to the list, not just dorian -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: Wed, 6 Nov 2002 15:42:55 -0500 (EST) From: Pat Eyler <pate(a)eylerfamily.org> To: dnmeid(a)gmx.de Subject: Re: [Koha-devel] Koha's i18n & l10n On Wed, 6 Nov 2002, Dorian Meid wrote: > > > paul POULAIN schrieb: > > hdl already did one (newbasket2.pl, commited by me yesterday, after some > > testing) too. > > > > If 1.2 manager wants to backport them from main branch to 1.2, it should > > be easy and without pain. > > BTW: > Can someone tell me which pieces of code should go in which branch? > Sometimes I have the impression that two snippets relying on each other > are spread over two branches. > How do we work with the branches in koha? Right now, we're not doing terribly well at keeping the branches separate. The initial vision was that the 1.2 branch would be for bug fixing only, with new work being done on the main line. Then as features were ready to be included in the 1.2 releases, they could be backported. In practice, I think people just worked on the 1.2 line while Paul worked on 1.3 in the main line. As we get ready to branch 1.3/1.4 and start a new development line on the main trunk, we should think hard about what model we want to follow, and how to enforce it. -pate > > dorian > > > ------------------------------------------------------- > This sf.net email is sponsored by: See the NEW Palm > Tungsten T handheld. Power & Color in a compact size! > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en > _______________________________________________ > Koha-devel mailing list > Koha-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/koha-devel >

1 0

Koha's i18n & l10n
by Francisco M. Marzoa Alonso 06 Nov '02

06 Nov '02

Greetins everybody, My name's Francisco Marzoa and I'm from Spain. I work as software developer and system administrator in a little company that's mainly focused on RFID technologies. We're interesting in adding RFID capabilities to koha, but somework must be done before. I've superficially seen koha's code a few minutes ago and I've seen that there's no internazionalization (i18n) and/or localization (l10n) support, (maybe I'm wrong?). Of course, we're interesting in translate Koha mainly to spanish, but I think that we can do it better than only getting the sources and translating strings. Among other things, without (translatable) resource isolation, if we change some koha's code functionality, we'll have to repeat that changes in every language, even if that changes doesn't imply strings. I've seen that in contribute's page TODO there is a "Translate things" entry, but I think the better could be if we prior to code translation, we do prepare that code for internazionalization and localization. I can contribute doing the whole string isolation (prepare code for i18n and l10n) and, later, with an spanish koha translation. Please, let me know what do you thing about this and... excuse my english! Cheers,

4 4

Re: cataloging on the koha ils
by Rosalie Blake 06 Nov '02

06 Nov '02

Hello Michelle, I can only answer part of your question, but I'm sending both your question and my reply to the kohalist, where people with eperience in MARC will pick it up, and offer some more answers, I'm sure. Koha is easy for novice cataloguers. As a small public library, we don't need detailed cataloguing for most records, and we do need fast records - we like to get our books on the shelf without delay. So we don't import MARC records any longer. We used to, but gave it up some years back, when we realised it wasn't meeting our needs - too slow and too detailed, and sometimes not appropriate. But I am very well aware that other libraries' priorities are different, and a team of Koha developers has been working on the MARC interface - notably Paul Poulain. I will leave him to comment on your questions about auto-coding. We love Koha. But then it was written to meet our needs, so we would say that, wouldn't we? But I can also say that everyone else here also likes it - and I'm thinking especially of people like volunteers, borrowers, casual users, all of whom find it easy to use. We are particularly proud of Acquisitions, which gives us much better budget control that we ever had in the past. We are just in the process of re-developing our web page (www.library.org.nz) improving the integration with the OPACs and adding functionality for our members to access their own records and renew and reserve from home. Watch out for it towards the end of this month. Cheers, Rosalie Blake Head of Libraries, Horowhenua Library Trust On 31 Oct 2002, at 15:56, Michelle Swanson wrote: > Hi: Is koha easy to use for "novice" catalogers? Does it have a fill > in the blanks template with author, title, publisher, etc., which > auto-codes marc? Does the cataloger need to be very familiar, > somewhat familiar or unfamiliar with marc code? Please advise. Also, > please share your personal views on the koha system. I tried out the > Koha OPAC at Horowhenua Library Trust via the web and it looks > impressive. best regards from, > > > Michelle Swanson > Acquisitions Dept > University of Winnipeg Library > 515 Portage Avenue > Winnipeg, MB Canada R3B 2E9 > m.swanson(a)uwinnipeg.ca > (204)786-9806 > > >

2 1

RE: [Koha-devel] [Bug 40] memberentry.pl and data of birth
by Anthony W. Youngman 05 Nov '02

05 Nov '02

Shouldn't you also permit ISO? This has several advantages namely 1) It's a formal standard. 2) Seeing as it is yy/mm/dd, you can sort on it. 3) In some countries (eg Sweden iirc) it is normal usage. Cheers, Wol -----Original Message----- From: bugzilla-daemon(a)wilbur.katipo.co.nz [mailto:bugzilla-daemon@wilbur.katipo.co.nz] Sent: 25 October 2002 18:32 To: koha-devel(a)lists.sourceforge.net Subject: [Koha-devel] [Bug 40] memberentry.pl and data of birth http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=40 tonnesen(a)cmsd.bc.ca changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From tonnesen(a)cmsd.bc.ca 2002-10-26 06:32 ------- New System preference (dateformat) can be set to 'US' to have 'mm/dd/yy' format, otherwise it will use 'dd/mm/yy' format. In either case, the memberentry page will show the correct format to use. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. ------------------------------------------------------- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/koha-devel This transmission is intended for the named recipient only. It may contain private and confidential information. If this has come to you in error you must not act on anything disclosed in it, nor must you copy it, modify it, disseminate it in any way, or show it to anyone. Please e-mail the sender to inform us of the transmission error or telephone ECA International immediately and delete the e-mail from your information system. Telephone numbers for ECA International offices are: Sydney +61 (0)2 9911 7799, Hong Kong + 852 2121 2388, London +44 (0)20 7351 5000 and New York +1 212 582 2333.

1 0

Errors in win32 version
by Van der Vyver Jan <13310623＠sun.ac.za> 04 Nov '02

04 Nov '02

Hi all I'm testing the win32 version and found a few bugs. I am running: Windows 2000 Service Pack 3 IE 6.0.2600.0000 Apache/2.0.36 (Win32) MySQL 3.23.49-nt ActiveState Active Perl 5.6.1.633 KohaW32_1.2.3RC23A I played around with koha and foud the next few bugs so far: 1. When deleting a brach, shows sql. 2. Can't add an Adult member. Get error: Premature end of script headers: newmember.pl 3. When adding an org. the Institution Name is not marked with a *. 4. When adding an org. an auto matic card number is not shown. 5. Allows to add org. with a card number that already exists. 6. When adding a child to an adult, no auto matic card number. 7. When adding a child, it show the parent's member card no. and with member no writeen under it. 8. Can delete branch when there is still books outstanding for that brach. 9. Help don't work, I get no page. 10. When I delete a member, it don't return to the full member page, but just the middel part. 11. When i go into catal. maintenace and select subject maintenace and select a subject. I get a to smaal window to work in which cannot be resized. And the next few questions: 1. What thus the issuing stand for when adding a branch? 2. Where is the Area set (The area that you see when adding a person) I am testing koha for implementing in a few schools here in South-Africa. So there it is, all my bugs so far. Now the question. Do you want me to submet every bug to bugzilla, or sould i mail directly to a developer? groete jan

1 0

Testing Win32
by Van der Vyver Jan <13310623＠sun.ac.za> 02 Nov '02

02 Nov '02

Hallo There Is there someone out there who is testing the win32 install of koha. If not, i will help to do it. The install it self works fine. But there is a bug or two still in the system :) groete Jan van der Vyver South-Africa PS. Sorry if my spelling is bad, i'am Afrikaans by birth

1 0

[Bug 119] New: Dewey Numbers like 000 or 581.0 aren't handled properly
by bugzilla-daemon＠wilbur.katipo.co.nz 01 Nov '02

01 Nov '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=119 Summary: Dewey Numbers like 000 or 581.0 aren't handled properly Product: Koha Version: 1.2.3 Platform: PC OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Catalogue AssignedTo: chris(a)katipo.co.nz ReportedBy: tonnesen(a)cmsd.bc.ca QAContact: koha-devel(a)lists.sourceforge.net Fixing this is going to require changing the dewey field to a character field instead of a numerical field and getting rid of all the hacks to strip trailing zeros etc. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 113] "class" does not narrow search
by bugzilla-daemon＠wilbur.katipo.co.nz 31 Oct '02

31 Oct '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=113 tonnesen(a)cmsd.bc.ca changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From tonnesen(a)cmsd.bc.ca 2002-11-01 16:54 ------- Search.pm was ignoring search strings less than 3 characters (ie class='JF' was ignored, but class='JNF' was okay) ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0