- Koha-translate - lists.koha-community.org

Ukrainian translation of Koha 3.0
by Serhij Dubyk Сергі й Дубик 20 Jan '08

20 Jan '08

Hi all I want to add Ukrainian translation: Language: українська Language in English: Ukrainian Country: Ukraine Cyrillic script code: Cyrl At this time I am main ukrainian translator: Serhij Dubyk (Сергій Дубик) Translation is maked localy with poEdit and posted on our translation service Pootle: http://www.library.lviv.ua:8080/uk/koha_3_0/ (to Ukrainians - please make suggestions and join to translation process) Some info in ukrainian will be collected on Wiki: http://wiki.koha.org/doku.php?id=ukrainian With best regards Serhij Dubyk, L'viv Scientific Library -- View this message in context: http://www.nabble.com/Ukrainian-translation-of-Koha-3.0-tp14980194p14980194… Sent from the Koha - Translate mailing list archive at Nabble.com.

2 2

Start Russian translation of Koha 3.0
by Serhij Dubyk Сергі й Дубик 20 Jan '08

20 Jan '08

Hi all I want to announce Russian translation for Koha 3.0: Language: русский Language in English: Russian Country: Russian Federation, Ukraine, ... Cyrillic script code: Cyrl Translators: Victor Titarchuk and Serhij Dubyk Translation maked on our on-line translation service Pootle: http://www.library.lviv.ua:8080/ru/koha_3_0/ To Russian-speaking people - please help with Russian translation, make suggestions, and look/work on Wiki: http://wiki.koha.org/doku.php?id=russian With best regards Serhij Dubyk -- View this message in context: http://www.nabble.com/Start-Russian-translation-of-Koha-3.0-tp14980243p1498… Sent from the Koha - Translate mailing list archive at Nabble.com.

1 0

Some questions
by Axel Bojer 19 Jan '08

19 Jan '08

Hello! I have some comments and questions concerning the Koha-translation, and hope there is someone out there that could help me :-) As you see for instance here: http://translate.koha.org/editpot.php?lg=en&db_table=fr__FR__i__opac__t__pr… there are strings like: $  But I suppose those are not to be localized at all, but just left as is? Something like: $  (translated to Norwegian) would supposedly not work, would it? But since it is there I assume something has to be configurable, so I am a little bit confused about those (there are more of them, some with some text in between, some without). Other than that, it would be nice if strings occurring twice could be eliminated, I am thinking of strings like this: In the staff file: ------------------ Catalogue by Item Type Catalogue by itemtype (strings 1447 and 1448) Other than inconsistent spelling, those are perfectly the same. Sometimes I see the same strings twice, but one of them misspelled, like this: Combinaisons de techiques diverses de detection thermique par infrarouge Combinaisons de techiques en faible emission Combinaisons de techniques diverses de detection thermique par infrarouge Combinaisons de techniques en faible emission (1683--86) Two of those obviously would have to be removed. String 1403 is also misspelled: Cannot Delete Currencey I also don't quite follow the necessity of string pairs like these: Couleur Couleur: (1179 and 1780) -- sometimes even more of them, just with * or extra an extra space before : added also, which makes up to four practically identical strings. with just a small effort in scripting these copies could be erased. I suppose some hundred, if not more, of the strings could be omitted by correcting such mistakes. I know I can search and replace (Kbabel and Kaider), copy and paste -- or even just use the translation database (Kbabel), but for the poor people using the web interface this is not easy to do. So if someone could take a look at this we could ease the translation job for everyone :-) Then for some mystic strings that I don't quite understand the meaning of: Bibs -- Is this a Unique Name and therefore not translatable? I could not find it on Google or Wikipedia. mc:v or mc-rtype:o and more of the same sort, are those really to be translated, and what do they mean? No added comment there, that could have helped :-) moon script -- What is this? I know what Braille is, but moon script? road type -- We are not talking about cars, are we, so what is it? http://en.wikipedia.org/wiki/Types_of_road reconcillation -- What is this according to Koha? If someone could clear this up, we would be happy :-) BTW: How do we give credits to the translators? I see some names in the staff-file, but no string like: Translator or similar, like KDE has. Do you add this, and do we then have to submit all the names of our translators to you to get it in? We are a group of four, maybe five translators, mainly because we have two writing languages :-P http://en.wikipedia.org/wiki/Norwegian Best regards Axel Bojer Norwegian translator of Koha

5 7

Re: Koha-translate Digest, Vol 19, Issue 10
by Selma Aslan 19 Jan '08

19 Jan '08

Hello Everyone I would like to make a comment on "Reconciliation": In one of the institutions I worked in the past we used to reconcile revenue records kept in the library and the accounts to make sure that they match. So, I don't know if this is relevant in the context of Koha, but I would expect it to be a kind of cross checking. Does that make sense? Selma Aslan ----- Original Message ---- From: "koha-translate-request(a)nongnu.org" <koha-translate-request(a)nongnu.org> To: koha-translate(a)nongnu.org Sent: Saturday, 19 January, 2008 7:00:45 PM Subject: Koha-translate Digest, Vol 19, Issue 10 Send Koha-translate mailing list submissions to koha-translate(a)nongnu.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.nongnu.org/mailman/listinfo/koha-translate or, via email, send a message with subject or body 'help' to koha-translate-request(a)nongnu.org You can reach the person managing the list at koha-translate-owner(a)nongnu.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Koha-translate digest..." Today's Topics: 1. Re: Some questions (Joshua Ferraro) 2. Re: Some questions (Axel Bojer) 3. Re: Some questions (Dorian Meid) 4. Re: Some questions (Joshua Ferraro) ---------------------------------------------------------------------- Message: 1 Date: Fri, 18 Jan 2008 18:59:59 -0500 From: "Joshua Ferraro" <jmf(a)liblime.com> Subject: Re: [Koha-translate] Some questions To: "Axel Bojer" <axelb(a)skolelinux.no> Cc: koha-translate(a)nongnu.org Message-ID: <2dfa91e40801181559p2f4bac5ai1b14e039b1247f75(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Hi Axel, Some answers to your excellent questions follow: On 1/17/08, Axel Bojer <axelb(a)skolelinux.no> wrote: > Hello! > > I have some comments and questions concerning the Koha-translation, and > hope there is someone out there that could help me :-) > > As you see for instance here: > http://translate.koha.org/editpot.php?lg=en&db_table=fr__FR__i__opac__t__pr… > > there are strings like: > > $  > > But I suppose those are not to be localized at all, but just left as is? > Something like: > > $  > (translated to Norwegian) > > would supposedly not work, would it? > But since it is there I assume something has to be configurable, so I am > a little bit confused about those (there are more of them, some with > some text in between, some without). You're right, the example should NOT be translated, but should be left as is. It's a failing of the gettext tool perhaps, or maybe we need to edit our base template in that case to prevent that example from showing up. > Other than that, it would be nice if strings occurring twice could be > eliminated, I am thinking of strings like this: > > In the staff file: > ------------------ > Catalogue by Item Type > Catalogue by itemtype > (strings 1447 and 1448) Yes, we should attempt to normalize the strings, sorry ... it's a lot of work, I know! > Other than inconsistent spelling, those are perfectly the same. > Sometimes I see the same strings twice, but one of them misspelled, like > this: > > Combinaisons de techiques diverses de detection thermique par infrarouge > Combinaisons de techiques en faible emission > Combinaisons de techniques diverses de detection thermique par infrarouge > Combinaisons de techniques en faible emission > (1683--86) > Two of those obviously would have to be removed. Agreed. I can attempt to do this for 3.0 beta > String 1403 is also misspelled: > Cannot Delete Currencey > > I also don't quite follow the necessity of string pairs like these: > > Couleur > Couleur: > (1179 and 1780) > -- sometimes even more of them, just with * or extra an extra space > before : added also, which makes up to four practically identical strings. Yes yes yes ... > with just a small effort in scripting these copies could be erased. > I suppose some hundred, if not more, of the strings could be omitted by > correcting such mistakes. I know I can search and replace (Kbabel and > Kaider), copy and paste -- or even just use the translation database > (Kbabel), but for the poor people using the web interface this is not > easy to do. So if someone could take a look at this we could ease the > translation job for everyone :-) Agreed. I will attempt to do this for 3.0 beta. > Then for some mystic strings that I don't quite understand the meaning of: > > Bibs -- Is this a Unique Name and therefore not translatable? I could > not find it on Google or Wikipedia. Bibs is an abbreviation of 'Bibliographic Records'. > mc:v or mc-rtype:o > and more of the same sort, are those really to be translated, and what > do they mean? No added comment there, that could have helped :-) Those are 'material category' and are mainly just CCL codes, you can ignore them as they are used for the internal search API. > moon script -- What is this? I know what Braille is, but moon script? This is a real script, identified by the Library of Congress apparently ... :) > road type -- We are not talking about cars, are we, so what is it? > http://en.wikipedia.org/wiki/Types_of_road We are talking about street types (such as 'St., Rd., etc.). It's a feature in Koha that you can have authorized value lists for road types. > reconcillation -- What is this according to Koha? Reconciliation (yes it is misspelled), is a term that has to do with the current day's activities I believe (transactions of the day). Someone else might know better than I. > If someone could clear this up, we would be happy :-) > > BTW: How do we give credits to the translators? I see some names in the > staff-file, but no string like: Translator or similar, like KDE has. Do > you add this, and do we then have to submit all the names of our > translators to you to get it in? We are a group of four, maybe five > translators, mainly because we have two writing languages :-P > http://en.wikipedia.org/wiki/Norwegian Please tell us who was responsible for the translation, by posting a mail to this list (koha-translate). I will add the credits to the 'About' page for the Koha 3.0 beta (I already have a list of some of you, but obviously if you want credit you must identify yourselves as a contributor :-)). Thanks again for these excellent questions, let us know if we can help further. Cheers, -- Joshua Ferraro SUPPORT 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 ------------------------------ Message: 2 Date: Sat, 19 Jan 2008 01:30:55 +0100 From: Axel Bojer <axelb(a)skolelinux.no> Subject: Re: [Koha-translate] Some questions To: Joshua Ferraro <jmf(a)liblime.com> Cc: koha-translate(a)nongnu.org Message-ID: <479144BF.8010809(a)skolelinux.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Joshua Ferraro wrote: > Hi Axel, > > Some answers to your excellent questions follow: Thank you! > On 1/17/08, Axel Bojer <axelb(a)skolelinux.no> wrote: (...) >> with just a small effort in scripting these copies could be erased. >> I suppose some hundred, if not more, of the strings could be omitted by >> correcting such mistakes. I know I can search and replace (Kbabel and >> Kaider), copy and paste -- or even just use the translation database >> (Kbabel), but for the poor people using the web interface this is not >> easy to do. So if someone could take a look at this we could ease the >> translation job for everyone :-) > Agreed. I will attempt to do this for 3.0 beta. Very good! >> Then for some mystic strings that I don't quite understand the meaning of: >> >> Bibs -- Is this a Unique Name and therefore not translatable? I could >> not find it on Google or Wikipedia. > Bibs is an abbreviation of 'Bibliographic Records'. That makes sense :-) >> mc:v or mc-rtype:o >> and more of the same sort, are those really to be translated, and what >> do they mean? No added comment there, that could have helped :-) > Those are 'material category' and are mainly just CCL codes, you can ignore > them as they are used for the internal search API. Will do :-) >> moon script -- What is this? I know what Braille is, but moon script? > This is a real script, identified by the Library of Congress apparently ... :) In the meantime we found this: http://en.wikipedia.org/wiki/Moon_code so perhaps it should be rephrased to moon code? >> road type -- We are not talking about cars, are we, so what is it? >> http://en.wikipedia.org/wiki/Types_of_road > We are talking about street types (such as 'St., Rd., etc.). It's a > feature in Koha > that you can have authorized value lists for road types. Really? hmm ... ok :-) >> reconcillation -- What is this according to Koha? > Reconciliation (yes it is misspelled), is a term that has to do with the current > day's activities I believe (transactions of the day). Someone else might know > better than I. Some sort of unification, we thought: http://www.m-w.com/dictionary/Reconciliation So probably, then, some way to unite something: <a1>Home</a> &rsaquo; <a2>Reports</a> &rsaquo; Till Reconciliation would perhaps, then, be the unification/merging of two different reports into one? That is our best guess by now :-) Perhaps also here a rephrasing (into some of the more well known (close to be) synonyms mentioned)? >> BTW: How do we give credits to the translators? I see some names in the >> staff-file, but no string like: Translator or similar, like KDE has. Do >> you add this, and do we then have to submit all the names of our >> translators to you to get it in? We are a group of four, maybe five >> translators, mainly because we have two writing languages :-P >> http://en.wikipedia.org/wiki/Norwegian > Please tell us who was responsible for the translation, by posting a mail > to this list (koha-translate). I will add the credits to the 'About' > page for the > Koha 3.0 beta (I already have a list of some of you, but obviously if you want > credit you must identify yourselves as a contributor :-)). We are: Norwegian Bokmål: Axel Bojer and Thomas Gramstad Norwegian Nynorsk: Unni Knutsen and Marit Kristine Ådland We will tell you if there are changes, but I suppose that will be it :-) > Thanks again for these excellent questions, let us know if we can help further. Actually, one more right away -- about the html-encodings :-) In Norway we don't citate with "word" but with «word». I see many places, that " is used instead (in English). Do we, then, have to change ours into » and « everywhere, or will « and » be recognized? I thought of doing a search and replace for all of them at the last moment before submitting, just to be sure everything is viewed correctly, or will some of the text be rendered differently than by html (just text f.i.), so that we will have to use « and » somewhere too? I suppose – (or —) will be better than -- too, will it not? I found this in many strings ... Best regards Axel Bojer ------------------------------ Message: 3 Date: Sat, 19 Jan 2008 15:58:49 +0100 From: Dorian Meid <dnmeid(a)gmx.de> Subject: Re: [Koha-translate] Some questions To: koha-translate(a)nongnu.org Message-ID: <0DC40086-6393-4879-BB01-453AC6DD3387(a)gmx.de> Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Am 19.01.2008 um 01:30 schrieb Axel Bojer: > Actually, one more right away -- about the html-encodings :-) > > In Norway we don't citate with "word" but with «word». I see many > places, that " is used instead (in English). Do we, then, have > to change ours into » and « everywhere, or will « and » > be recognized? I thought of doing a search and replace for all of > them at the last moment before submitting, just to be sure > everything is viewed correctly, or will some of the text be > rendered differently than by html (just text f.i.), so that we will > have to use « and » somewhere too? Another good question. Apparently the quotes have been left out while rewriting the html for CSS. I suggest to use the q-tag instead of quotes: <q>word</q> Then most browsers should handle the quotation marks correctly according to the browsers set language. For a better control we can specify how the q-tag is handeled in the stylesheet. Here is an excelent articel about that: http://www.456bereastreet.com/archive/200411/ quotations_and_citations_quoting_text/ This would also be a great advantage for theme-designers. Dorian Meid PS: if you want a quick and dirty solution: If you have encoded your files in UTF8 « and » will work. ------------------------------ Message: 4 Date: Sat, 19 Jan 2008 11:17:23 -0500 From: "Joshua Ferraro" <jmf(a)liblime.com> Subject: Re: [Koha-translate] Some questions To: "Dorian Meid" <dnmeid(a)gmx.de> Cc: koha-translate(a)nongnu.org Message-ID: <2dfa91e40801190817n188f788dl629f9b35dd8341f9(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 On 1/19/08, Dorian Meid <dnmeid(a)gmx.de> wrote: > > Am 19.01.2008 um 01:30 schrieb Axel Bojer: > > Actually, one more right away -- about the html-encodings :-) > > > > In Norway we don't citate with "word" but with «word». I see many > > places, that " is used instead (in English). Do we, then, have > > to change ours into » and « everywhere, or will « and » > > be recognized? I thought of doing a search and replace for all of > > them at the last moment before submitting, just to be sure > > everything is viewed correctly, or will some of the text be > > rendered differently than by html (just text f.i.), so that we will > > have to use « and » somewhere too? > > Another good question. > Apparently the quotes have been left out while rewriting the html for > CSS. > I suggest to use the q-tag instead of quotes: <q>word</q> > Then most browsers should handle the quotation marks correctly > according to the browsers set language. > For a better control we can specify how the q-tag is handeled in the > stylesheet. > Here is an excelent articel about that: > http://www.456bereastreet.com/archive/200411/ > quotations_and_citations_quoting_text/ > This would also be a great advantage for theme-designers. OK, I think this is the correct solution, I will also work to fix this for the 3.0 beta. Cheers, -- Joshua Ferraro SUPPORT 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 ------------------------------ _______________________________________________ Koha-translate mailing list Koha-translate(a)nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-translate End of Koha-translate Digest, Vol 19, Issue 10 ********************************************** __________________________________________________________ Sent from Yahoo! Mail - a smarter inbox http://uk.mail.yahoo.com

2 1

translation
by Ignacio Javier 17 Jan '08

17 Jan '08

Hi all: Is my intention start to translate koha 3 to: Language name: Galego English language name: Galician Character coding: ISO-8859-15 ISO 639-1: gl What is the preferred method for windows editing, windows Poedit or web manager interface?: http://translate.koha.org/get_tables.php?lg=en&view=all Greetings Ignacio Javier Gómez Rodríguez Analista - Programador Tfno: 902905590 - Fax: 981571425 ignacio.gomez(a)coremain.com www.coremain.com

2 1

Status of Koha 3 Translations (two weeks remaining)
by Joshua Ferraro 17 Jan '08

17 Jan '08

Hi all, Since the announcement on January 8th (8 days ago) that Koha 3 is ready to be translated, we've heard from dozens of translators around the globe who have collectively agreed to translate Koha into over 26 languages! So first off, a big round of applause to all who have volunteered! Just to give you all an update, I just approved all pending translations, and we're up to about 16% completion for all translations. Some are finished, and some haven't been started yet. Please bear in mind the deadline for submissions is 1 February, just two weeks away! I'll send another reminder in about a week. In the meantime, happy translating everyone! Finally, for those who would like to translate Koha into their langauge, and missed the original email, here are the relevant instructions (most folks seem to be using the web-based translation manager FYI): 1. Please take a look at http://translate.koha.org. Some translations already exist; please consider taking over an existing translation rather than starting a fresh one, unless the existing one is un-usably poor :-) 2. Please post your intent to translate Koha to the koha-translate list: http://lists.nongnu.org/mailman/listinfo/koha-translate In your email, please specify your Language, and Country/Region (and if your language uses a non-latin script, please also indicate the Script). Koha uses RFC4646 for managing language subtags, so it's important that we know all of those aspects of the language you're providing. It's important that you post your intent, this way we can avoid overlap and perhaps can even do some collaboration. Note: even if you've contributed a contribution previously, please announce your intent so we can have you on record for the 3.0 version. 3. Determine the application you intend to use to do the translation. You have a few options: a. http://translate.koha.org will allow you to add your translations via a web-based interface. If your language, region, country and script are not listed, please email me and I will add them. b. Desktop Application - there are a few: LocFactory Editor (for OSX), POEdit (for Windows), Kbabel (for Linux). If you use a desktop application, please ensure that your encoding is set either UTF-8 or UTF-16, depending on your language's script support in UTF-8. Most languages should use UTF-8. c. Text file -- yes, you can edit POT files directly in a text editor, but please make sure you have the proper encoding as with the Desktop application. 4. Obtain the Translation Files. (doesn't apply if you use translate.koha.org) You need to copy two files from the Koha 3.0 repository, one for the OPAC, and one for the Staff Client: http://git.koha.org/cgi-bin/gitweb.cgi?p=Koha;a=blob_plain;f=misc/translato… http://git.koha.org/cgi-bin/gitweb.cgi?p=Koha;a=blob_plain;f=misc/translato… 5. Naming your files. (doesn't apply if you use translate.koha.org) Starting with Koha 3, we're using RFC4646 language subtag naming conventions, (have a look at http://www.w3.org/International/articles/language-tags/ for an intro). RFC4646 has a concept of 'extensions' that Koha uses to tag for the 'theme' (t) 'interface' (i) and 'version' (v). For example, if you're creating a French translation from France, for the staff interface, and version 3.00.00.00, the filename would be: fr-FR-i-staff-t-prog-v-3000000.po 6. If you've used translate.koha.org to submit your translation, when you have finished, the system will have that indicated on the report (100%). Otherwise, you'll have to send the file to us somehow. You can do that via email to the list (in which case i recommend creating an archive of the completed files, rather than sending them through in raw format). Or, if you are reasonable comfortable with the command line, you can submit them via Git as a patch. Here are the basic instructions for how to contribute using Git: http://wiki.koha.org/doku.php?id=en:development:git_usage Translations go in the misc/translator/po file, and should utilize the standard naming conventions. If you have a question, don't hesitate to ask. Cheers, -- Joshua Ferraro SUPPORT 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

Accepting translations made on the Hungarian versions
by Agnes Imecs 16 Jan '08

16 Jan '08

Hello Joshua, You mentioned to contact you if we have a representative quantity of translations. I did worked on both files. Can you accept the translations, that someone can check them? Thanks! Agnes ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs

1 0

(no subject)
by Karen Myers 16 Jan '08

16 Jan '08

Hi I'd like to do the Tetun translation for Koha 3. Could I request a file to be setup on the translation site please? thanks Karen Myers _________________________________________________________________ New music from the Rogue Traders - listen now! http://ninemsn.com.au/share/redir/adTrack.asp?mode=click&clientID=832&refer…

1 0

about french strings in .po
by Paul POULAIN 13 Jan '08

13 Jan '08

Hello all, something like 4 years ago, when doXulting wrote unimarc plugin templates, they did it in french. Nobody ever translated them to english, that's why they are still now in french even in english, and thus appear in the .po file. Fortunatly, there is an option in tmpl_process3.pl (the script that generate the strings file) Just add -x .*unimarc.* as parameter of tmpl_process3.pl and they are gone. Of course, you'll stay with unimarc strings in french in your language. but if you don't use unimarc, you don't care. On the long term, the best solution will be to translate those strings to english (& for us reintroduce them in french po file) HTH -- Paul POULAIN BibLibre SARL Expert en Logiciels Libres pour l'info-doc Tel : 04 91 31 45 19

5 5

Re: [Koha-translate] tranlating into Hungarian
by Agnes Imecs 13 Jan '08

13 Jan '08

Hello, Thanks! It's my mistake. I copied the format from the previous email, which was Greek. Our script is Hungarian (UTF-8). All the best, Agnes ----- Original Message ---- From: Joshua Ferraro <jmf(a)liblime.com> To: Agnes Imecs <eloise212(a)yahoo.com> Cc: koha-translate(a)nongnu.org Sent: Thursday, January 10, 2008 4:03:03 PM Subject: Re: [Koha-translate] tranlating into Hungarian Hi Anges, On 1/10/08, Agnes Imecs <eloise212(a)yahoo.com> wrote: > > Hi! I would like to tranlate Koha 3 in Hungarian. > > Language: Hungarian (HU) > Region: Europe > Country: Hungary (HU) > Script: Greek (UTF-8) > > Is it possible to use the web interface for the Koha staff as well? I know you've been waiting for this a long time! I recall our conversations at ALA last year. So you'll be happy to know that I just added Hungarian as an option for the staff client to be translated. Happy translating! One quick question before you start. You mention that you'll be using the Greek script, is this always how Hungarian is written? or are there other scripts that are common? I ask because I want to make sure we identify the language correctly. Cheers, -- Joshua Ferraro SUPPORT 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 ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping

3 2