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

tranlating into Hungarian
by Agnes Imecs 10 Jan '08

10 Jan '08

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? Agnes ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs

2 1

(no subject)
by Beda Szukics 09 Jan '08

09 Jan '08

Hallo I have done some tranlation work for 2.9.9 on tranlate.koha.org So I'll try to complete the tranlation of the OPAC till february 1st. Language: de Region: CH Country: Switzerland Thanks for your work. I managed to install the alpha on the first try :-) Greetings Beda

2 1

about translating koha, a small hint
by Paul POULAIN 09 Jan '08

09 Jan '08

Hello again, just to let you know : from my experience of translating koha to french : it's much more faster & easier to start by OPAC. And more useful (as all users benefit from it, where staff in your language is useful only for your librarians) Note also that translating is a long task, that you can't imagine doing between 2 cup of tea/coffee/wine/water/WhateverYouDrink -- Paul POULAIN BibLibre SARL Expert en Logiciels Libres pour l'info-doc Tel : 04 91 31 45 19

1 0

tranlating into Greek
by gogo 09 Jan '08

09 Jan '08

Hello! I would like to tranlate Koha 3 in Greek language: Greek (EL) Region: Europe Country: Greece (GR) Script: Greek (UTF-8) I think I would prefer to use the web interface (http://translate.koha.org) Is it possible? Georgia Katsarou

2 1

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