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

Re: [Koha-devel] Koha & UNICODE
by Owen Leonard 13 Oct '04

13 Oct '04

> > If you were using tidy to clean up templates, you'd have > > to configure it to only alter the character encoding, > > and not touch the document structure, right? > > I'd probably take the chance to fix any structure bugs too. I doubt Tidy would be able to pick apart a complex template like circulation.tmpl. I don't have any experience configuring Tidy, though. -- Owen

1 0

Thoughts on documentation -- please feedback
by Stephen Hedges 12 Oct '04

12 Oct '04

Hello, all - I have been looking more closely at formats for the Koha documentation, and I like the Simplified DocBook DTD for our XML sources (http://www.docbook.org/xml/simple) It seems to me that the sdocbook.dtd has all the elements we are likely to need for the component documents people write about Koha. An example of an XML source tree that uses the DocBook XML DTD is the Linux Documentation Project's template for authors (http://www.tldp.org/authors/template/Sample-HOWTO.xml) I think this might also make a good template for the individual Koha documentation components. I also looked through the DocBook wiki section on XML tools (http://wiki.docbook.org/topic/DocBookAuthoringTools) and looked a little at XXE Standard Edition from xmlmind.com. It's not open source, but it doesn't cost anything. I may download it and try it out. Has anyone used XXE SE? Anyone have any thoughts about the sdocbook.dtd or the LDP template? Stephen -- Stephen Hedges Skemotah Solutions, USA www.skemotah.com -- shedges(a)skemotah.com

2 3

Koha & UNICODE
by Paul POULAIN 12 Oct '04

12 Oct '04

Hi, i'm "speaking" with a french library that is highly interested by Koha, but needs absolutely UNICODE support. They ask me what wil it "cost" to add unicode support. They may involve a developper to add this, (or maybe fund). Does anyone have an opinion on this ? Do we have to use utf16 or is utf8 possible ? For me, it means : * rewrite all templates in utf * parse all perl scripts for unicode support (what does it means exactly ? i'm not sure. chapter 15 of Perl Programming is not enough for me) * dump non utf DB & reload it in utf (specifis pragmas in mySQL) * other things ? Thanks for more infos -- 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 Library 11 Oct '04

11 Oct '04

hai all, i want to set up my OPAC for 2.0.0 because it shows only title,author,copyright & location but i also want the calssification no. in the OPAC.But i don't know how to do it,if anyone knows about it,please tell me...? kanwaljit Librarian GNDEC,Ludhiana > 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. > > cheers, > -indra. > > >

1 1

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