November 2007 - Koha-translate - lists.koha-community.org

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

Re: [Koha-translate] Norwegian translation of Koha
by Thomas Dukleth 28 Nov '07

28 Nov '07

Reply inline: [Sorry for my late reply. I intended to reply earlier but a lingering cold kept me from some things last month.] On Fri, October 12, 2007 10:42 am, Axel Bojer wrote: [...] > We have good news from Norway: > NUUG ( Norwegian Unix User group, http://nuug.no/ ) have agreed to pay > two translators to translate koha into norwegian (bokmål, by the way, we > also have nynorsk :-). So now the next question is: > > How far has the translation files for Koha 3.0 come by now? As quoted > above, they ought to be in good shape now, but, well, delays seems to > happen, so: How is the status by now? Is it advisable and possible to > start translating koha 3.0 already now or will there be major changes > that will render our work (partly) useless? > > I also wonder how difficult it will be to make a local build with our > translations? The koha-translate list is not read by as many people who should read it as it ought to be. I will try to obtain an answer for you about the current status of Koha 3.0 HTML stability for translation. > My experiences with other translation project (Scribus, OOo, KDE) shows > me that it is essential to be able to look at what you have actually > committed. Often it is impossible to know exactly how to translate a > spesific phrase without knowing how this function works and/or what the > GUI looks like. > It will therefore be important for us to be able to make our own > localised builds continuously to see the changes and the results. > > And third: If all the other questions are answered with «GO FOR IT > (NOW)», then: Is it possible to put the needed files out on the net like > this: > http://translate.koha.org/use.php?lg=en > > or do you have pot- and po-files ready for us? > While setting up something like "http://translate.koha.org/use.php?lg=en" may be possible, I suspect that is not likely to happen given other development priorities. Although, you could do that yourself using a git repository clone. See the Koha git documentation at http://wiki.koha.org/doku.php?id=en:development:git_usage . I will press for the current status of po files. > And, finally, what about the mentioned «MARC frameworks», are there any > ready made translation files for them? > There has never been a proper translation model for frameworks. A diff based model at least should be created for future. At present simply adapt the most current copy of the frameworks in SQL format for your language. I recommend carefully editing the most current Koha frameworks as SQL files using a text editor designed for editing source code such as vim. Using the frameworks editor inside Koha is suitable for small changes but it is too slow and has too many bugs to be really suitable for translation work. Whether you are translating current MARC 21 into Norwegian or adapting it for the similar NORMARC, you should start with the most recent version of the Koha MARC 21 bibliographic framework, http://git.koha.org/cgi-bin/gitweb.cgi?p=Koha;a=blob;f=installer/data/mysql… . Use the NORMARC documentation whether you are translating the current version of MARC 21 or adapting for NORMARC, http://www.nb.no/fag/kompetansesenter/kunnskapsorganisering/dnk . Use the most recent version of Koha MARC 21 authorities framework, http://git.koha.org/cgi-bin/gitweb.cgi?p=Koha;a=blob;f=installer/data/mysql… . I would be pleased to offer any assistance I can for the frameworks. I edited the English frameworks but I do not have any facility with the language of my ancestors. Also, I would personally be interested in a formal English translation of the relatively few NORMARC elements which do not match MARC 21 elements. Thomas Dukleth Agogme 109 E 9th Street, 3D New York, NY 10003 USA http://www.agogme.com 212-674-3783 [...]

4 3

Re: [Koha-translate] I wanna a new language addition for koha
by Thomas Dukleth 26 Nov '07

26 Nov '07

Reply inline On Sun, October 21, 2007 2:38 pm, Br. Cesar wrote: > Hi... > > Im from Brazil, and since portuguese from Portugal isnt the same thing we > speak here, I think that the Koha Team should add "Portuguese (BR)" in the > list for translation. > > Will be a great pleasure for me to contribute with that translation :D Do not let anyone stop you. If you provide a translation, provision will be made for placing it, even if a similar translation exists already. At this point, as Koha 3.0 is being finished for release, translating Koha 3.0 would be likely to be much more useful than translating Koha 2.2.X. Furthermore, Koha 3.0 has no Portuguese translation at all. See the instructions for using the Koha git repository, http://wiki.koha.org/doku.php?id=en:development:git_usage . I will enquire whether Koha 3.0 HTML is ready for translation. Thomas Dukleth Agogme 109 E 9th Street, 3D New York, NY 10003 USA http://www.agogme.com 212-674-3783 [..]

2 1

Koha frameworks internationalisation
by Thomas Dukleth 26 Nov '07

26 Nov '07

Do you use MARC 21 in a language other than English? Do you use UNIMARC in a language other than French or English? Do you use a MARC variant other than MARC 21 or UNIMARC? If you have any language specific or MARC variant specific Koha frameworks for sharing, please contact me on or off the list. LibLime has asked me to prepare whatever MARC frameworks I can obtain for use in the forthcoming version of Koha 3.0. Share yours so that others do not need to do redundant work. [MARC frameworks are either bibliographic or authorities frameworks and go by various names in Koha depending upon how you access them. In the system administration intranet interface, they are identified as Biblio framework (MARC structure) for bibliographic frameworks or Thesaurus structure for authorities. In the installation directories, they have names such as structure_def.sql for bibliographic frameworks or authorities_normal_marc.sql for authorities.] I will supply very simple instructions for exporting your frameworks from your SQL database if you need such assistance. Thomas Dukleth Agogme 109 E 9th Street, 3D New York, NY 10003 USA http://www.agogme.com 212-674-3783

1 0