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

XHTML valid OPAC avaible
by paul POULAIN 06 Jan '04

06 Jan '04

Hi all, On CVS, in 2.0.0 branch, i've just commited a theme called css. It's 100% based on a stylesheet (so it's name :-) ), and validator.w3c.org like it too ( :-) again ) Enjoy. opac.css is documented a little. Remember to create an entry called "LibraryName" in Systempreferences, it's used in window title & on top. -- 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

OPAC & valid HTML & CSS positioning template
by paul POULAIN 05 Jan '04

05 Jan '04

Hi all, I've spend some hours during my holidays (between 2 huge dinners ;-) ) writing a new template for OPAC, that : * use only stylesheet for graphic presentation. * uses CSS positionning. * should be valid HTML (not tested yet because no web connexion during holidays). Do you think I should commit this new opac : * as new theme, with the problem it will have to be maintained with the default one. * as default theme, overwritting the previous one, with the problem it is graphicaly different from the default theme (not completly, but enough to be a trouble for a end user) I prefer as default theme, but in HEAD branch only, and as new theme in 2.0.0 branch. What is you opinion ? -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

2 1

recent acquisitions feature & translation tool
by paul POULAIN 05 Jan '04

05 Jan '04

Hi, a "recent acquisition" tool has been added in OPAC : in the main opac screen, you can choose itemtype (X) & duration (Y). Then you can see books acquired since less than Y days with itemtype X. Will be released with 2.0.0RC2 Note : for those not reading koha-dev : i've also created a translation tool that should highly ease translation of Koha. If someone want more info, see koha-dev. opac in french has been entirely re-reated with this tool. Translation in a new language means editing a SINGLE text file. 250 line for opac, 1200 for intranet. All "developper" lines are hidden, you just have to translate english strings. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

2 3

Subject: Re: [Koha-devel] Problem modifying user with new installation
by Edward M. Corrado 05 Jan '04

05 Jan '04

Joshua Ferraro <jferraro(a)athenscounty.lib.oh.us> wrote: > Hi Edward, Hi Joshua, > I thought this problem was fixed already, but it looks like it's coming back :-) > I wonder if it's bug 491... I didn't notice a place to look up bugs before. However I just noticed the koha-bugs mailing list on sourceforge. I'll have to remember to check it in the future. > It would help us diagnose the problem better if we could see the error logs, > which would give the location in the perl scripts/modules of the problem. > The log to check in this case is koha-error_log. The log files should be > in /usr/local/koha/log but if you can't find them there you can run a search: > > find / -name koha-error_log -print I just replicated the error and this is what is showing up in the koha-error_log that looks related: [Mon Dec 29 08:41:26 2003] [error] [client 127.0.0.1] autoMemberNum is 1, referer: http://127.0.0.1:8080/cgi-bin/koha/moremember.pl?bornum=1 Is there a setting for autoMemberNum that would be more appropriate? I'd like to keep the member numbers automated if possible. While I'm mentioning things in the error log, I'm also getting a number of entries that look like this: [Sun Dec 28 12:37:48 2003] [error] [client 127.0.0.1] File does not exist: /usr/local/koha/intranet/htdocs/images, referer: http://127.0.0.1:8080/cgi-bin/koha/admin/stopwords.pl [Mon Dec 29 08:40:58 2003] [error] [client 127.0.0.1] File does not exist: /usr/local/koha/intranet/htdocs/images, referer: http://127.0.0.1:8080/cgi-bin/koha/mainpage.pl I'm assuming that these are just because I didn't add images to replace the text across the top of the screen - so I'm not that worried about it. Should I be? I noticed a few other issues, but I'll save them until I get to check the bugs list. Edward

3 2