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

Spanish translation
by Desarrollo Koha 27 Jan '04

27 Jan '04

Hello: I am working on translate the english stuff of the default theme to spanish, but I have some problems with the translation tool (it seems not to catch all the strings and not to process others- specially strings with template vars in the middle of them-). I don't know the way to publish the work. Don't know what could be better translation file (not all the templates will be translated) or the translated templates (with some manual work that will be overwritten). Regards.

2 1

Translator tool improved
by paul POULAIN 16 Jan '04

16 Jan '04

Hi, I've just commited many translator tool improvements. Now, the translator tools works perfectly fine. * managing strings with LIMITED pragma when the string is a koha intenral code too (like search) * improving speed by 50 : just by reading the whole file before s///g, instead of doing a s///g on each line ! (on 1000 lines translation file, that makes a HUGE difference !) * NOT overwritting unchanged file => now, we can commit only what has changed ! * removing useless chars (., ?, spaces...) at end of strings. WORKS on french OPAC AND INTRANET without problems. Enjoy, and publish new localised versions of Koha in a few hours :-) PS : thanks to Jean Blaise that translated the intranet (1130 lines) to french. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Re: Koha translation
by paul POULAIN 12 Jan '04

12 Jan '04

Desarrollo Koha a écrit : > >>> DO NOT translate manually the spanish templates, that are outdated >>> you're right. >>> But look in misc/translator directory, file translator_doc.txt >>> >>> ¿where ?. I have downloaded the koha-2.0.0RC1.tgz file from >>> sourceforge and i can not find the file you are talking about. >> >> It is NOT in 2.0.0RC1, only in CVS. >> if you don't want to play with CVS, i can send you the 4 interesting >> files. Ask me. > > > Ok, I have found that in CVS, but it seems to have problems in order > to translate to spanish. > > Some of the strings (with more than one word) are ignored (the > "Advanced Search (More Options)" for instance). > > I don't know how to solve that. And I don't think the english > expressions can be easily translated (with the embeded variables). > I will be working in the translations :-):-) (with the automated > translator while possible) I think the problem is only on strings where there is a regexp special char, like ()$^... I've fixed this in CVS/rel2_2_0. Tell me if it's better now. PS : pls post in koha-devel/koha-translate. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

[important]NEW TRANSLATION TOOL
by paul POULAIN 05 Jan '04

05 Jan '04

I've just commited a new translation tool. Feel free to test it AND IMPROVE IT. TRANSLATION TOOL : ============ This transation tool should greatly help Koha translators. It's composed of 2 script : * test-extract.pl, that extracts the texts in a template. It is called by * tmpl_process. tmpl process can do 3 things : - create a file with all sentences all files in a directory (& it's subdirectories) - update an existing translation file. - rebuild translated templates from english & translation file. Call tmpl_process --help to get full explanations. HOW TO TRANSLATE Koha : ============ 1- create your translation file : ./tmpl_process.pl update -i /home/paul/koha.dev/koha/koha-tmpl/opac-tmpl/default/en/ -s opac.fr -r 2- translate your opac.fr file (english & french being separated by a tab 3- create your translated version : ./tmpl_process.pl install -i /home/paul/koha.dev/koha/koha-tmpl/opac-tmpl/default/en/ -o /home/paul/koha.dev/koha/koha-tmpl/opac-tmpl/default/fr2/ -s opac.fr -r 4- copy images in your new directory (as they are NOT moved by tmpl_process.pl install) If something changes in english version, go back to pt1 & repeat. WEAKNESSES ======= I've found some weaknesses (some solvable probably, but maybe some unsolvable) - HTML::Templates pb : if there is only a <TMPL* > tag between 2 strings, text-extract sometimes merges both strings, and so can't replace them in the translated template. I've solved all those cases with a <br/> or another HTML statement. - SHORT STATEMENTS short statements (like "in") can be replaced stupidly (like in cgi-bin => gives cgi-bdans in french). the workaround has been to replace only complete words ( line 185 of tmpl_process : $line =~ s/(\W)$text(\W)/$1$subst$2/g; ) Don't seem to have any side effect. - WORD exist in FILENAME words that are in the templates and in a perl script name are replaced ! For example : Search is replace by Recherche in french, thus,giving <a href="cgi-bin/opac-Recherche.pl">, which is wrong... The only way I've found to solve this is to ignore any translation whose translation string is IGNORE (search is the only cas i've found in french opac) - MISSING STRINGS Maybe some strings that should be translated are missing. You can add whatever you want in text-extract.pl. For instance, it extracts : - standard text - text in alt="SOMETEXT" - meta html encoding (8859-1) to enable non european translations. COPYRIGHT ====== @ paul poulain (paul.poulain _@_ free.fr) & Jerome Vizcaino vizcainj _@_ esiee.fr -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

2 3