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

Call for Translation Manager
by Joshua Ferraro 12 Aug '08

12 Aug '08

Hi folks, Well, 3.0-stable is finally out, and includes over 31 translations, and that's really amazing ... thanks so much for all your hard work these past months! I'm writing this email to let you all know that I'm stepping down as the unofficial Translation Manager for future versions of Koha. For 3.0, I was serving as the Release Manager, de-facto QA Manager and the de-facto Translation Manager, and needless to say, that's too much for one person to bear -- I need a break. Many of you had excellent ideas for how to improve the translation framework in Koha to ease the process of translation, and improve the quality of the translations. I wish we'd had time to implement those ideas for 3.0, and I'm hoping we'll have a chance to do so for future versions of Koha. So ... I'm requesting candidates for the (hopefully) official position of Translation Manager. Here's a rough outline of the responsibilities: * Maintain a mechanism for non-technical translation teams to contribute translations to the Koha project (similar to the kartouche tool I've maintained at http://translate.koha.org, though as many of you have pointed out, better tools exist. * Keep all the translation .po files up to date from release to release, including translations submitted via the project-wide translation tool, and translations submitted by others * Coordinate with the RM to set 'string freezes' and communicate to the translation community about such dates * Coordinate with the RM to prepare and install translations of Koha An ideal candidate would have the technical skills necessary to to set up (host), maintain, and customize whatever project-wide translation tool we pick to replace Kartouche; and would be able to improve the existing tools within Koha for creating .po files, as well as make suggestions for how to improve transaltion of areas not currently covered by that tool (MARC Frameworks for instance). Such a candidate should also be able to manage the process of pushing translations upstream to the RM using Git, and providing the RM with access to patches that can't be transmitted easily via email due to length or encoding. As as side note, LibLime will continue to host the Kartouche installation at http://translate.koha.org until another tool is available, and we're happy to coordinate changing the DNS when such a tool is available. Any takers? -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE CEO migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS

7 7

Translation of Koha to Spanish
by Evelio Martínez 12 Aug '08

12 Aug '08

Hello all! I have a question concerning translation of strings . We have customized the koha intranet templates in english and now are trying to translate it to spanish. The aim is to reuse strings already translated by others and add or change some other. We have used the following commands: 1) ./tmpl_process3.pl install -r -i /www/koha/usr_share_koha/intranet/htdocs/intranet-tmpl/prog/en -o /www/koha/usr_share_koha/intranet/htdocs/intranet-tmpl/prog/es -s po/es-ES-i-staff-t-prog-v-3000000.po 2) ./tmpl_process3.pl update -i /www/koha/usr_share_koha/intranet/htdocs/intranet-tmpl/prog/en/ -s po/es-ES-i-staff-t-prog-v-3000000.po -r The install and update commands seems to be successful I suppose that tmpl_process3.pl can merge an old translated file like po/es-ES-i-staff-t-prog-v-3000000.po and merge it with the new english template. is it correct? I am not sure because some lines of the new spanish template are been taken and some not. is this normal? The string "New Preference" in line 234 has not been changed to "Establecer Preferencias" #: /www/koha/usr_share_koha/intranet/htdocs/intranet-tmpl/prog/es/modules/admin/systempreferences.tmpl:234 #, fuzzy msgid "New Preference" msgstr "Establecer Preferencias" <li><a id="newstopword" href="?op=add_form">New Preference</a></li> </ul></div> but the string "System Preferences &rsaquo; Data Added" it has been changed. #: /www/koha/usr_share_koha/intranet/htdocs/intranet-tmpl/prog/es/modules/admin/systempreferences.tmpl:2 #, fuzzy msgid "System Preferences &rsaquo; Data Added" msgstr "Administración de Preferencias del Sistema" <title>Intranet BBVA Infoblue &rsaquo; Administration &rsaquo;  System Preferences &rsaquo; Modify system preference ''Añadir una preferencia del sistema System Preferences &rsaquo; Data Added Any help will be appreciated Thanks in advance ------ Evelio Martínez Director proyectos software C/ Garcilaso, 15-bajo 46003 Valencia Telf: 96 369 41 23 Fax: 96 369 34 39 www.masmedios.com

2 1

Post-3.0 git branch and version numbering
by Galen Charlton 12 Aug '08

12 Aug '08

Hi, Congratulations to all on Koha 3.0 stable! But, no rest for the weary... To get the transition to 3.2 started, I plan to do the following later today: [1] Create a 3.0-maintenance branch from the current master HEAD. Future 3.0 packages and bugfix releases (e.g., 3.0.1) will be based on this branch. [2] Make several changes in HEAD to switch to 3.2 mode, including: - changing version string in kohaversion.pl to 3.01.00.000. - committing a separate copy of the 3.0-stable kohastructure.sql to t/data/db_schemas/ for use by future test cases that will validate the database update mechanism. Since a stable 3.2 will be months away, for current work I suggest we stick with using 3.1 as the version number, following the Linux kernel convention that an odd subrevision number signifies an unstable development version. Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 skype: gmcharlt _______________________________________________ Koha-devel mailing list Koha-devel(a)nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel

3 8

Wiki instructions for dealing with 3.0.x
by Galen Charlton 12 Aug '08

12 Aug '08

Hi, I've added instructions to the wiki about handling the new branch:: http://wiki.koha.org/doku.php?id=en:development:git_usage#create_a_branch_t… If anybody finds an error or a better way to do it, please update the wiki or let me know. Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 skype: gmcharlt

2 2

Koha 3.0.x Git branch created
by Galen Charlton 11 Aug '08

11 Aug '08

Hi, I have created a branch for maintaining Koha 3.0.x in the public Git repository located at git.koha.org. This branch and the master HEAD currently point to the same state of the Koha source tree, the 3.0-stable version, but this will change as patches are accepted for 3.1. Specifically, work destined for 3.1 will be added to the master HEAD, and patches for the 3.0.x maintenance versions will be cherry-picked from HEAD or added directly to the 3.0.x branch. The branch is called 3.0.x - I decided to use something shorter than "3.0-maintenance". For Git users, the next time you do a git fetch, a reference to the remote branch will be fetched automatically. If you want to make a local branch in your git repository that tracks the official 3.0.x branch, you can do git fetch git branch --track my3.0.x origin/3.0.x Here "my3.0.x" is the name of your local branch, and "origin/3.0x" is the name of the remote branch that is being tracked. To check out that tracking branch, do get checkout my3.0.x If you are running a dev-mode installation of Koha 3.0 and you *don't* want your installation to start following the 3.1 developments, you should fetch, create the tracking branch, and check out that branch BEFORE rebasing and going through the database update. Later tonight I will be pushing a patch to master's HEAD that updates the version number to 3.01.00.000. Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 skype: gmcharlt

1 0

RFC 3.2 : Koha Offline Circulation
by Kyle Hall 11 Aug '08

11 Aug '08

Hello All, This is a request for comments regarding the file format for the offline circulation system. The specification for the Koha Offline Circulation (.koc) file format can be found here: http://wiki.koha.org/doku.php?id=koha_offline_circulation_file_format which Andrew Moore and I have come up with. I believe it is simple but extensible in case we need to add new features to the offline circulation client in the future. Having a standardized format means that we can have more than one offline circ client. The code to process this file format is already completed for both the client and server side processors. Please let me know what you think. Kyle -- http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )

3 4

Convincing City IT Dept.
by Ed Veal 11 Aug '08

11 Aug '08

I have an interesting situation here. We had LibLime come and give us a presentation last week and I thought it would be best to invite the city IT staff to take a look so that they could be onboard with any decision that we make. However, what has happened is that they seem to think that they have the expertise to do this on their own. I shudder at the thought. They have already set up a server and are wanting my advice and guidance in migrating data. My advice is to contract it out, we don't have the resources or the expertise to accomplish this. So my question is how do I convince the IT department of this? I can't seem to get it through to them that this is not just any old SQL database. **************************************************************** Edward Veal (eveal(a)mail.ci.lubbock.tx.us) System Administrator Lubbock Public Library http://www.lubbocklibrary.com Mahon Library 1306 9th St. Lubbock, TX 79401 voice: 806-775-2849 fax: 806-775-2827 *******************************************************************

8 7

Application to get the KOHA cd package.
by itiwm Jonny 11 Aug '08

11 Aug '08

Hi, I am a librarian in kenya.I would like to get the cd installation package for the KOHA library software.We have a slow internet connection and we cannot download the program online.Any assistance in that aspect would help in the automation of our small library. Thank you. Tonny Mwiti My address is Tonny Mwiti, P.o.Box 11136-001100, Nairobi, Kenya.

2 1

Proposed schedule for 3.2
by Galen Charlton 11 Aug '08

11 Aug '08

Hi, For your consideration, an outline of a schedule for Koha 3.2. This is organized by weeks, with this week being Week 1. My main scheduling goals are to have more frequent intermediate releases, to explicitly schedule several periods of bugfixing between the feature pushes, and to release Koha 3.2 no later than the second quarter of 2009 (and preferably, by the end the first quarter). [1] Plotting and planning (weeks 1 to 5) During this period, we'll finishing submitting RFCs for 3.2 and review them. Patches to 3.1 will be accepted, but I may stick anything particularly controversial onto a topic branch until the community has had time to digest the relevant RFCs. At the end of this period, I hope to have: * A list of features that contributors are committed to delivering for 3.2, as well as those that may be pushed off to 3.4 and 3.6. * A list of any architectural and major technology changes for 3.2. * Final coding standards for 3.2. At the end of this period, I tentatively plan to do an initial release of 3.1 (to be called 3.1-dev-release-0), mostly to verify that I can put the package together correctly. This may coincide with release of 3.0.1 (first bugfixes for 3.0-stable). [2] Coding phase 1 (weeks 6 to 9) Period of intensive hacking. [3] Stabilization 1 (weeks 10 and 11) Freeze on major developments; during this time we focus on bugfixing. At the end of this period I will release 3.1-dev-release-1. [4] Coding phase 2 (weeks 12 to 15) More hacking. [5] Stabilization 2 (weeks 16 and 17) At the end of this period I will release 3.1-dev-release-2. [6] Coding phase 3 (weeks 18-21) More hacking. [6] Stabilization 3 (weeks 22 and 23). At the end of this period I will release 3.2-alpha. [7] Catchup feature developement (weeks 24 and 25). Last chance to put in small and medium-sized features. If we can swing it, after this period ends new feature work will go on a branch for inclusion in 3.4. [8] Stabilization 4 (weeks 26 and 27) At the end of this period I will release 3.2-beta. [9] General non-coder review and bugfixing (weeks 28 to 31). At the end of this period I will release 3.2-rc1. [10] Final release (weeks 32 and 33) At the end of this, 3.2-stable. If I'm counting the weeks correctly, that corresponds to the end of March, 2009. Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 skype: gmcharlt

1 0

Adding to or Editing the Koha Wiki
by Owen Leonard 10 Aug '08

10 Aug '08

For those of you who may be new to Koha, please note that the Koha Wiki is not editable by default. Because of wiki-spam problems in the past, users are required to register and log in to make changes. This is indcated on the Wiki home page by a message at the top, "Login from the link at the bottom of the page and contribute to the content." The wiki is a great place to get discussions and ideas down in a central place that might be easier to refer to than list messages and IRC chats. Please register and contribute where you can! http://wiki.koha.org Thanks, Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

3 2