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

Fwd: [Koha-devel] Custom searches in opac
by Peter Hartmann 17 Jan '08

17 Jan '08

---------- Forwarded message ---------- From: Peter Hartmann <peter(a)hartmanncomputer.com> Date: Jan 17, 2008 8:29 PM Subject: Re: [Koha-devel] Custom searches in opac To: Henri-Damien LAURENT <laurenthdl(a)alinto.com> Can I make the search criteria not so strict? I did notice that with my previous 952p test that partial searches didn't work. Searching for '6' did not return results although that are many sixes in barcodes. These 521a fields have spaces in them as well which may be causing a problem. Examples: PreK. - K 4 / 3 - 7 Not sure what the second one indicates....but that's the librarians doing. With name="operator" value="contains": Searching for 'prek' gives 7 results even though there are man more there. Searching for any of the numbers doesn't work. name="operator" value="=" Single numbers and floating point numbers work but not 'Prek'. Is there some way of combining "=" and "contains"? I tried using 'or' like this but no good: <input type="hidden" name="operator" value="contains" or "=" /> and also two separate lines with each variation.... thanks, Peter here it is again... <th><label for="level">Reading Level:</label></th> <td><input type="hidden" name="marclist" value="521a" /> <input type="hidden" name="and_or" value="and" /> <input type="hidden" name="excluding" value="" /> <input type="hidden" name="operator" value="contains" /> <input type="text" id="level" name="value" /> </td> </tr> On Jan 17, 2008 7:33 PM, Peter Hartmann <peter(a)hartmanncomputer.com> wrote: > Hey Henri-Damien , > That's what this bit of code originally looked like. Just for > kicks I changed it to 952b -barcode- and searched for a valid barcode. > It does indeed work, just not for 521a which is populated in the > aforementioned table . So does this mean that I have to link 521a > with a koha-marc? Sorry this sliding in to userville. > > Thanks, > > Peter > > > > > On Jan 17, 2008 6:04 PM, Henri-Damien LAURENT <laurenthdl(a)alinto.com> wrote: > > Hi, > > Peter Hartmann a écrit : > > > Hey, I'm looking to set up a custom search in the npl opac for > > > 'Reading Level". This is a big one for elementary schools. This > > > information is under 521a in the marc records that I have imported > > > into koha database. This mysql query lists the information in a table > > > that I need: > > > > > > select * from marc_subfield_table where tag = 521 and subfieldcode = 'a'; > > > > > > Any ideas how I could search this as a temporary table from the opac. > > > Or is there an easier way? > > > > > > > > > <th><label for="level">Reading Level:</label></th> > > > > > > <td><input type="hidden" name="marclist" > > > value="marc_subfield_table.subfieldvalue" /> > > > > > try this here : value="'521a'" It should work. > > > > > <input type="hidden" name="and_or" value="and" /> > > > <input type="hidden" name="excluding" value="" /> > > > <input type="hidden" name="operator" value="contains" /> > > > <input type="text" id="subfieldvalue" name="value" /> > > > </td> > > > </tr> > > > > > > > > > this is how far I've gotten in altering the opac-search.tmpl file for > > > the npl template. It doesn't work. > > > > > So long. > > -- > > Henri-Damien LAURENT > > >

1 0

Custom searches in opac
by Peter Hartmann 17 Jan '08

17 Jan '08

Hey, I'm looking to set up a custom search in the npl opac for 'Reading Level". This is a big one for elementary schools. This information is under 521a in the marc records that I have imported into koha database. This mysql query lists the information in a table that I need: select * from marc_subfield_table where tag = 521 and subfieldcode = 'a'; Any ideas how I could search this as a temporary table from the opac. Or is there an easier way? <th><label for="level">Reading Level:</label></th> <td><input type="hidden" name="marclist" value="marc_subfield_table.subfieldvalue" /> <input type="hidden" name="and_or" value="and" /> <input type="hidden" name="excluding" value="" /> <input type="hidden" name="operator" value="contains" /> <input type="text" id="subfieldvalue" name="value" /> </td> </tr> this is how far I've gotten in altering the opac-search.tmpl file for the npl template. It doesn't work. Thoughts anyone? Thanks, Peter

1 0

Installation on Solaris
by Evelio Martínez 17 Jan '08

17 Jan '08

Hello everyone! I would like to know if someone tried to install KOHA on this platform: - OS: Solaris - Database: Oracle - Web Server: websphere I suppose minimum problems could appear on Solaris and Websphere, but there is a medium probability to have problems with Oracle database, concerning reserved word on columns names, tables names or similar things. I have search on google, have read some posts and also http://www.koha.org/download/other-os.html Has anyone first hand info about the previous configuration? Thanks in advance -- Evelio Martínez

2 3

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

16 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

Wiki Section on Bar Code Scanners
by Chris Nighswonger 15 Jan '08

15 Jan '08

Sorry for the cross post... FWIW, I added a section to the wiki containing bar code scanner info. The namespace follows 'en:documentation:barcode_scanners:foobrandscanner' I have munged up a section containing some config notes I made while getting my Metrologic VoyagerGS up and working. Any additions/corrections/criticisms (constructive) would be appriciated. Also, if you use a different scanner it would be nice to add a section for others as well. http://wiki.koha.org/doku.php?id=en:documentation:barcode_scanners:ms9590_v… Regards, Chris -- Chris Nighswonger Faculty Member Network & Systems Director Foundations Bible College & Seminary www.foundations.edu www.fbcradio.org

1 0

Koha 3.0 success
by Chadwick, John, DCA 14 Jan '08

14 Jan '08

We got two servers running with Koha 3.0 now. The backend works nicely. Our database admin likes the design and setup and she has been importing MARC records. The only issue we have now is that we can't do a search from the OPAC. The screens display okay, but a search by title or author of materials we have imported are not showing up in search results. John +----------------------------------------------------------------------- -----+ John Chadwick, Ed.D. Information Technology Manager New Mexico State Library 1209 Camino Carlos Rey Santa Fe, NM 87507 Phone: 505-476-9740 Cell: 505-629-8116 Fax: 505-476-9761 john.chadwick(a)state.nm.us http://www.stlib.state.nm.us Confidentiality Notice: This e-mail, including all attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited unless specifically provided under the New Mexico Inspection of Public Records Act. If you are not the intended recipient, please contact the sender and destroy all copies of this message. -- This email has been scanned by the Sybari - Antigen Email System.

2 7

OPAC Log error
by Chadwick, John, DCA 11 Jan '08

11 Jan '08

Here are the errors I am seeing in the OPAC search. [Fri Jan 11 12:50:33 2008] [error] [client 164.64.109.45] [Fri Jan 11 12:50:33 2008] opensearch: Use of uninitialized value in concatenation (.) or string at /usr/share/koha/opac/cgi-bin/opac/opensearch line 39. [Fri Jan 11 12:50:38 2008] [error] [client 164.64.109.45] [Fri Jan 11 12:50:38 2008] opac-search.pl: Use of uninitialized value in substitution (s///) at /usr/share/koha/lib/C4/Languages.pm line 399., referer: http://164.64.109.235/ +----------------------------------------------------------------------- -----+ John Chadwick, Ed.D. Information Technology Manager New Mexico State Library 1209 Camino Carlos Rey Santa Fe, NM 87507 Phone: 505-476-9740 Cell: 505-629-8116 Fax: 505-476-9761 john.chadwick(a)state.nm.us http://www.stlib.state.nm.us Confidentiality Notice: This e-mail, including all attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited unless specifically provided under the New Mexico Inspection of Public Records Act. If you are not the intended recipient, please contact the sender and destroy all copies of this message. -- This email has been scanned by the Sybari - Antigen Email System.

1 0

Announcing Koha 3.0 (Alpha)
by Joshua Ferraro 11 Jan '08

11 Jan '08

Hi folks, I'm happy to announce that a packaged alpha release of Koha 3 is now available. You can download from the usual location: http://download.koha.org/koha-3.00.00-alpha.tar.gz http://download.koha.org/koha-3.00.00-alpha.tar.gz.sig You can check the integrity of the package; either by verifying the provided GPG signature (.sig) or by comparing the MD5 checksum: 4fbd715cc6cd197264bba12b53391e42 koha-3.00.00-alpha.tar.gz I've also tagged this in Git as "version 3.00.00 alpha" v3.00.00-alpha This is the first packaged release of Koha 3. Prior to the official stable release of Koha 3.0, software issues, bugs, and unimplemented features must be addressed. These are documented on Koha's Bugzilla: http://bugs.koha.org and organized on the 3.0 RM's QA notes Wiki page: http://wiki.koha.org/doku.php?id=en:development:qanotes3.0 The release notes for this alpha version are pasted in below, and will also on the koha.org website sometime over the weekend. Cheers, -- Joshua Ferraro Koha 3.0 Release Manager ============================================================================== RELEASE NOTES FOR KOHA 3.0 ALPHA ============================================================================== Koha 3 is the next-generation release of the award-winning Koha open-source integrated library system. You can obtain Koha 3.0 Alpha from the following URL: http://download.koha.org/koha-3.00.00-alpha.tar.gz These Release Notes cover What's New in Koha 3, information about the new Revision control system (Git), and Version-release process, pointers to Download, Installation, and Upgrade documentation, a brief introduction to the new Templates, a call to Translation and Documentation writers, and finally, Known Issues with this version. ============================================================================== WHAT'S NEW IN KOHA 3? ============================================================================== 1. Zebra plugin - Zebra is a high-performance, general-purpose structured text indexing and retrieval engine. It supports large data sets (tens of millions of records) and includes support for SRU, Z39.50 and several query languages: CCL, CQL, and PQF. For more information about Zebra, please see: http://indexdata.dk/zebra Koha's new search engine, built on top of Zebra, supports features such as relevance ranking, field weighting, truncation, stemming, use of fuzzy operators, language-specific indexing, sorting, etc. Indexes are updated in real-time with circulation transactions, enabling limits by availability and statuses. Faceted refine-by limits are available from both staff and opac interfaces. For libraries that don't want the overhead of maintaing Zebra, Koha 3 ships with a NoZebra option, in which bibliographic and authority data is indexed in the RDBMS. 2. New installer - based on the common Perl module ExtUtils::MakeMaker, the new installer makes it a snap to get Koha running on just about any platform. The installer comes complete with a Developer's Toolkit target ('dev') that can be used to get a development environment linked directly to revision control, to support rapid prototyping and an agile development process. 3. Standard APIs - Koha 3 supports a number of important library search and retrieval standards and microformats, such as SRU/W, Z39.50 (http://www.loc.gov/standards/sru/) UnAPI (http://unapi.info/) and COinS/OpenURL (http://ocoins.info; http://www.niso.org/committees/committee_ax.html) Also supported is the popular Internet standard: OpenSearch (http://opensearch.a9.com/) created by Amazon's A9. Records are stored internally in an SGML-like format and can be retrieved in MARCXML, Dublin Core, MODS, RSS, Atom, RDF-DC, SRW-DC, OAI-DC, and EndNote; and the OPAC can be used by citation tools such as Zotero. Creating new export formats is a trivial exercise in writing XSLT; records can be passed through XSLT transformations either directly out of the index, or via a separate parsing function. To retrieve and interact with Circulation and Patron data, Koha 3 includes support for 3M's Standard Interchange Protocol (SIP2), using the OpenNCIP libraries (http://openncip.org) There are also an ever-expanding set of native REST APIs to handle interoperability with external tools such as third-party cataloging clients. These APIs provide authentication as well as add/edit/delete control over bibliographic data within a Koha system. For more information, see: http://wiki.koha.org/doku.php?id=en:development:web_services Koha 3 also includes pluggable authentication - easy integration with LDAP and Active Directory via the Auth_with_ldap module. The Amazon.com module can be enabled to enrich bibliographic data with jacket covers, professional reviews, ratings and comments from Amazon users, as well as point to 'Similar Items' within the catalog. OCLC's xISBN, and LibraryThing's ThingISBN can likewise be enabled to provide an 'Editions' tab on item detail pages. New with Koha 3 is service throttling for these services, to keep within subscription limits. 4. Cross-platform, multi-RDBMS, Web-server agnostic - Run Koha on the platform of your choice: Linux, Windows, Mac OS X, FreeBSD, Solaris. Koha 3 also includes better support for multi-RDBMS (MySQL 5.0 and PostgreSQL), and runs under Apache2, IIS, or the web server of your choosing. 5. Multi-lingual support - Koha was designed from the ground up for multilingual libraries. Koha 3 can handle Chinese, Japanese, and even right-to-left languages such as Arabic and Hebrew with ease (BiDi). Koha's index engine (Zebra) can handle record formats containing any UNICODE compliant script, such as Arabic, Chinese, Hebrew, Japanese and Korean. Zebra has this support via the ICU libraries created and maintained by IBM. You can translate Koha into your language using the built-in translation tools, or by visiting http://translate.koha.org. 6. New templates - Koha's staff and patron interfaces are developed with a template system that's easy to theme. The default templates are composed of 100% valid XHTML and CSS. Koha aims to meet or exceed U.S. Government Section 508 and W3C's WAI-AA standards for sight and motor impaired individuals. All Javascript usage comes with fallback modes that work in any web browser. 7. Koha 3 has quite a few new modules, as well as enhancements to existing modules, including: news writer, label creator, calendar, OPAC comments, MARC staging and overlay, notices, transaction logs, guided reports with a data dictionary and task scheduler, classification sources/filing rules. ============================================================================== REVISION CONTROL ============================================================================== With Koha 3, we've started using a new distributed revision control system called Git; it's the same system in use by many other projects, including the Linux Kernel. To learn more about how to develop Koha using Git, please see the Wiki page: http://wiki.koha.org/doku.php?id=en:development:git_usage ============================================================================== VERSION NUMBERING ============================================================================== With Koha 3, version numbering has been changed to use a method similar to Perl's: major.minor[.revision[.build]] * major: one digit * minor: two-digit * revision: two-digit * build: three-digit This alpha release of Koha 3.0 is versioned 3.00.00.041. Every database change or significant enough code change requires an update to the 'build' number, and developers will be able to easily upgrade their systems using the built-in updater. Koha 3.0 Release Schedule: This alpha release of Koha 3.0 will be followed by a beta release on Feb 1, 2008, including fixes to the following components: * General Bugfixing (everyone) * New API for item management (gmcharlt) * MARC21 Authorities (gmcharlt) * Improved I18N/L10N, lang detection (kados) * OPAC Templates re-design (oleonard) * Documentation and Translations (everyone) The final stable release of Koha 3.0 is slated for March 1 2008 and will include bugfixes to 3.0 beta. Subsequent releases of 3.0 will be bugfix releases, and won't include any new features. New features will be available in Koha 3.2 and subsequent releases. ============================================================================== UPGRADING FROM A PREVIOUS VERSION OF KOHA ============================================================================== The upgrade process from a previous version of Koha is documented on the Wiki at the following page: http://wiki.koha.org/doku.php?id=22_to_30 ============================================================================== TEMPLATES ============================================================================== You may have heard that the templates for Koha 3 have been re-skinned; there is also the start of a template style guide on the Wiki: http://wiki.koha.org/doku.php?id=en:documentation:templates_style_guide Kudos to Owen Leonard and the Nelsonville Public Library for their contributions! ============================================================================== TRANSLATIONS ============================================================================== Koha 3 alpha (this release) currently has complete translations for en-GB (English) and fr-FR (French). The Koha Team welcomes additional translations; please see http://www.kohadocs.org/usersguide/apb.html for information about translating Koha, and join the koha-translate list to volunteer: http://lists.nongnu.org/mailman/listinfo/koha-translate ============================================================================== DOCUMENTATION ============================================================================== User-contributed documentation for Koha 3 is available on the Koha Wiki (http://wiki.koha.org) The Koha Team welcomes documentation contributions; please join the Koha-devel list to volunteer: http://lists.nongnu.org/mailman/listinfo/koha-devel ============================================================================== KNOWN ISSUES ============================================================================== Known bugs are documented on the Koha wiki: http://bugs.koha.org and at the 3.0 RM's QA notes Wiki page: http://wiki.koha.org/doku.php?id=en:development:qanotes3.0

7 13

Translate Koha 3.0 into YOUR language
by Joshua Ferraro 09 Jan '08

09 Jan '08

Hi folks, Now that the alpha release of Koha 3.0 is out, we need to start lining up commitments from folks who want to translate Koha into their language. If you want your translation to be accepted for the 3.0 release, you MUST submit it before February 1st, 2008, which is the date that the Beta is released! Note: even partial submissions will be accepted. So, what is the procedure for submitting a translation? You can, of course, roll your own, but if you want your translation to be included in the main release of Koha 3.0, we'd best have a bit of a formal procedure ... so here's my crack at an overview of the process: 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, Region, and Country (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. So ... any takers? Feel free to post on-list or email directly to me, I'll try to coordinate the activity. 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

3 2

Koha 3.0 Staff Client Ready for Translation
by Joshua Ferraro 08 Jan '08

08 Jan '08

Hi all, Just a quick announcement for those of you interested in translating Koha 3.0 into your respective languages, the Staff Client POT file is ready for download and translation. I've created a generic POT that can be used, simply re-name the file to match your locale using RFC4646 conventions. Here's the link: http://git.koha.org/cgi-bin/gitweb.cgi?p=Koha;a=tree;f=misc/translator/po;h… (note that there is already a French translation written) The generic PO is called 'xx-XX-i-staff-prog-v-30000.pot'. You'll want to rename that file to match the language-script-region that you're translating. Starting with Koha 3.0, I'd like to propose a new naming convention for the PO/POT files in Koha that follows RFC4646 (have a look at http://www.w3.org/International/articles/language-tags/ for an intro). We can utilize RFC4646's concept of 'extensions' to tag for the 'theme' (t) and 'interface' (i) and 'version' (v). For example, if you're creating a French translation in France, the filename would be: fr-FR-i-staff-t-prog-v-30000.po Note that FR is a 'region' subtag ... but in some languages, such as Chinese, it's also useful to be able to distinguish between 'script's, such as 'Hans' (Simplified Han) or 'Hant' (Traditional Han). So you might, if you are translating Koha into Chinese, end up with a filename like: zh-Hans-i-staff-t-prog-v-30000.po RFC4646 gives us a lot of flexibility in how we distinguish between various translations. There are two excellent programs for doing your translation, depending on which platform you're running: LocFactory Editor (for OSX) POEdit (for Windows) Of course, you're free to simply use a text editor if that suites you, but please make sure you're in UTF-8 mode. Once you've got your PO file into a state where you're happy with it, you have a number of choies: 1. you can email it to the koha-translate list 2. you can email it to me 3. you can add it to Git yourself In the coming weeks I'll be updating translate.koha.org in preparation for the 3.0 cycle of releases, and improving the documentation on how to internationalize your Koha system, but if you prefer to work with local PO files, I wanted to make sure you had that opportunity. 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

2 1