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

Comments on terminology in the interface
by lars＠rovaniemelainen.com 11 Oct '04

11 Oct '04

Two comments. What do others here think? 1) The string "issue" seems to pop up in many different contexts where other words might be less ambiguous to humans and cause less trouble with kbabel. kbabel seems to search after strings, which gets screwed up over words with the same spelling but mean different things. e.g. issue (as in problem), issue (as in to lend), issue (as in journal number) Perhaps, some other words could be found for the first two and the last one could be 'disabmiguated' by saying 'number' or journal issue. 2) 'digital' or 'electronic' have been established terms when referring to online and computerized information resources for a long time within the library community. So, "virtual shelves" and "virtual bookshelves" probably ought to be called "electronic shelves" and "electronic bookshelves" respectively. In English, virtual tends to mean "not really" or "almost" and is often a weasel word in advertising campaigns. The information being aggregated using the metaphor of a shelf is quite real even if it has no physical manifestation. -Lars ------------------------------------------------- This mail sent through L-secure: http://www.l-secure.net/

1 0

Framework == controlled vocabulary / classification scheme?
by lars＠rovaniemelainen.com 11 Oct '04

11 Oct '04

I'm still chugging through making a Swedish translation and expect to be able to upload preliminary draft "Real Soon Now (tm)" However, I have a question about the term "framework". What is "framework" refering to? It's hard to be sure what the context is from kbabel. Perhaps it refers to a controlled vocabulary or classification scheme. e.g. ERIC or LCSH for the former or DDC for the latter. A controlled vocabulary is merely a list of subject terms or keywords used to describe the content or topic of a resource. A classification scheme is a subset of controlled vocabularies. If it does refer to a controlled vocabulary or classification scheme, then it might be better to say that so that the interface will be in more familiar terms for librarians / catalogers. -Lars ------------------------------------------------- This mail sent through L-secure: http://www.l-secure.net/

1 0

Re: [Koha-devel] Koha Documentation Structure
by Owen Leonard 10 Oct '04

10 Oct '04

> Surely we can pick one or two known free software copyright > licences which express the authors' wishes? I agree with MJR on this one, but *if* the consensus is that authors should be able to retain more rights that these licences allow, perhaps this is a resource we could use: http://creativecommons.org/ -- Owen

5 12

Arch Questions
by Mike Mylonas 08 Oct '04

08 Oct '04

I suppose the following is more specifically for MJ, but please feel free to jump in and clarify a couple of items for me. Let me start by saying I haven't fully investigated Arch yet, and I reaslise some of my question maybe answered elsewhere. All of my revision control experience has been based on CVS and Subversion. (1) From the sound of it, we all can maintain our own individual repositories under Arch, so is there no central repository? I am just concerned that if there are no central repositories, apart from the individual developers, about data backups etc (2) How does one manage the potential different "development" versions ... for example, I get some time to do some QA and bug squashing work on the latest vesion and I use my own Arch repository, and I archive and publish it on my public file space. Doesn't this potentially just get really messy with what could in fact look like numerous forks poping up around the web? I accept that these questions are probably just process questions, that I have missed seeing the answers to (and I also realise that Arch requires a completely different mindset from what I have been used to. Cheeres M

4 3

Re: [Koha] Koha 2.2 release plan & translations
by Gerry Arthus 08 Oct '04

08 Oct '04

Paul, If you send me the files, I would be willing to do translations for Russian, Turkish and Kyrgyz.. I would like to use Koha as the Opac front end for a project which I am working on in Central Aasia. Gerry Gerry Arthus Systems Administrator: Long Island Library Resources Council SUNY at Stony Brook Stony Brook, New York US 11794-3399 Phone: 1-631-632-6652 FAX: 631-632-6662 Home: 631-289-7565 Email: garthus(a)lilrc.org Professor: Departments of: Graduate Computer Engineering, Earth and Environmental Science, and Engineering Management C.W. Post Campus of Long Island University 720 Northern Boulevard Brookville, New York US 11548-1300 Phone: 516-299-2293 POULAIN wrote: > Gerry Arthus a écrit : > >> Paul, >> What languages are already translated for koha. >> >> Gerry > > > in 2.0 we had english, french, polish, chines. > In 2.2 we have english, french soon, don't know other languages status > yet. >

1 0

Koha 2.2 release plan & translations
by Paul POULAIN 08 Oct '04

08 Oct '04

Hi Koha fans, I'm fixing a lot of bugs at the moment (some on bugs.koha.org, some reported directly by EMN and not on bugzilla) There are a few features to add (like searching in order history), but 95% of the software is ready. So, there are 2 major needs to release a great 2.2 : * OnlineHelp * Localized versions. OnlineHelp : ************ I already asked on those lists for help to write OnlineHelp. I ask again. Some stuff has been done by Stephen Hedges, thanks to him. But he NEEDS HELP to complete this help. You can do it on a 2.0 install, i'll take care of improvements when needed. Anyone can help here : http://www.saas.nsw.edu.au/koha_wiki/index.php?page=OnlineHelp Localized versions : ******************** The ./tmpl_process3.pl is a great tool that generates a .po file that can be translated with many tools. The french translation will use it and the old ./tmpl_process.pl script is deprecated & will be dropped soon. I encourage all the translators team to work on actual CVS. I can send a uptodate file to translate to anyone requesting it. the opac is about 500 lines, the librarian interface is about 3000 lines (without OnlineHelp for instance) RELEASE PLAN : ========= The next release can be called 2.2RC1 I think. Question to the QA manager : do you want see it in stable or in unstable on sourceforge ? The next version should be released in a week or two (maximum) Note that I think we waited too much to announce 2.0 officially stable, in France that was a problem for some librarians that hesitates to install the soft even if 5+ libraries already used the 2.0.0rcX version. So I think we should release a 2.2.0 sooner and then 2.2.1, 2.2.2, as quickly as needed. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

2 1

Re: [Koha] Koha 2.2 release plan & translations
by Paul POULAIN 05 Oct '04

05 Oct '04

Indranil Das Gupta a écrit : >Hi Paul, >On Tue, 2004-10-05 at 15:07, Paul POULAIN wrote: ><snipped> > > >>I encourage all the translators team to work on actual CVS. I can send a >>uptodate file to translate to anyone requesting it. the opac is about >>500 lines, the librarian interface is about 3000 lines (without >>OnlineHelp for instance) >> >> >Requesting the uptodate file. I'm volunteering to translate Koha into my >mother tongue - Bangla/Bengali (BN), spoken by about 200 million people >in India and Bangladesh. > > Really great, I've stored on CVS (http://cvs.sourceforge.net/viewcvs.py/koha/koha/misc/translator/po/) 2 _en_EN.po files. get them, then rename them match your language (like fr_FR.po for french), then begin translation. note : the file may not appear immediatly, but they are here -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Koha Documentation Structure
by Stephen Hedges 04 Oct '04

04 Oct '04

I have attached a file called "koha_docs_structure" which contains an outline for all of the Koha documentation. This is _not_ the documentation itself, but a description of the structure that will be used to organize the documents. (If you have trouble with the attachment, you should be able to find this file on Sourceforge at http://cvs.sourceforge.net/viewcvs.py/koha/koha-doc/ within the next few days.) The outline contains some words in brackets <Like This> that are names for document containers. Many of these containers simply hold other containers. Only the text that is not enclosed by brackets (for example, "Description in English") refers to an actual document. The goal is to have a place for every type of Koha-related document. If you have Koha-related documents that do not seem to have a place in the structure, please let me know. If you can think of some possible Koha-related documents that do not seem to have a place in the structure, please let me know. It is not intended that we have a document that matches every document described. But it is intended that every document that gets submitted can be easily "plugged in" to this document structure. I will be retrieving existing documents, such as Nicholas Rosasco's "Koha Manual," converting them to XML, and fitting them into this structure. All documents will be stored in XML format, but you can submit documents in any format that is comfortable for you. (XML was chosen as the format for storage because it is basic and can easily be converted to many other formats using a wide variety of tools.) I will also be looking through old e-mail messages for relevant information, and may contact some e-mail writers and ask that they expand their comments into a document that can be used as part of the Koha documentation. If you would like to submit a document, please include the following statement in the document: "This document is copyrighted (c) 2004 by <your name here>. Unless otherwise stated, Koha documents are copyrighted by their respective authors. Koha-related documents may be reproduced and distributed in whole or in part, in any medium physical or electronic, as long as this copyright notice is retained on all copies. You may create a derivative work and distribute it provided that you: 1. Send your derivative work to the Koha Project for possible posting on the Internet. 2. License the derivative work with this same license, or the Linux Documentation Project License (http://www.tldp.org/manifesto.html) or the GNU General Public License (http://www.gnu.org/copyleft/gpl.html) Include a copyright notice and at least a pointer to the license used. 3. Give due credit to previous authors and major contributors. Commercial redistribution is allowed and encouraged; however, the author would like to be notified of any such distributions. Please check your local laws on copyright." OK, that's it. All comments or suggestions for improvement are welcome. --- Stephen Hedges Skemotah Solutions

3 3

RE: [Koha-devel] Koha Documentation Structure
by Anthony Youngman 04 Oct '04

04 Oct '04

Take a look at some of the O'Reilly books. I don't know how many of them are "Free" books that they have taken off the net, but there are a fair few where O'Reilly includes the source of the book and is not able to stop users copying the text. I thought DocBook was one of these but I'm not sure. If you want a "publisher friendly" licence, contact O'Reilly and ask them. As for all the documentation "being XML" and someone pointing out that XML is more a meta-format than a format, I would say that you should use DocBook for the documentation. I seem to remember hearing something about DocBook being updated recently, but it is a structured markup language, I think it does have an XML DTD, and it's pretty much the standard for Free Software documentation (the master copy, at least). The nice thing about it is that all the scripts, programs and everything are all there so that you can convert it into a help file, an html manual, a print manual, whatever. And if a publisher should decide it's worth printing, it's in a nice, convenient, STANDARD form for them to just drop into their system and run with ... Cheers, Wol -----Original Message----- From: koha-devel-admin(a)lists.sourceforge.net [mailto:koha-devel-admin@lists.sourceforge.net] On Behalf Of Joshua Ferraro Sent: 04 October 2004 15:15 To: koha-devel(a)lists.sourceforge.net Subject: Re: [Koha-devel] Koha Documentation Structure On Mon, Oct 04, 2004 at 02:39:49PM +0100, MJ Ray wrote: > froody... If you want CC, use that one ;-) Free software needs free > software manuals. However, I do think we should at least consider the possibility of a printed manual at some time in the future. So which license is likely not to prevent a publisher from signing on? Or would we self-publish? Joshua ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ 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 8272 5300, Hong Kong + 852 2121 2388, London +44 (0)20 7351 5000 and New York +1 212 582 2333. ****************************************************************************

1 0

[OT] announce
by Paul POULAIN 02 Oct '04

02 Oct '04

Hello Koha developpers, I'm very, very, very happy to give you this link and announce that my 3rd son is born. Official annoucement (in french) and some pictures at : http://www.paulpoulain.com/jeremie/ -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

3 2