December 2003 - Koha-devel - lists.koha-community.org

Re: [Koha-devel] templates & translation
by Owen Leonard 11 Dec '03

11 Dec '03

> So i've written a little script that changed ALL > <TMPL > to <!-- TMPL > > in both OPAC and INTRANET. Is that script in CVS? I looked but didn't see it. Maybe I just missed it. I'd like to be able to use it to convert our custom template. -- Owen

2 1

Re: [Koha-devel] templates & translation
by Owen Leonard 10 Dec '03

10 Dec '03

> > No, because HTML::Template doesn't support > this. > > That is why I suggested we ask for it. > > > I've asked H::T mailing list to accept > <TMPL_ELSE /> and <TMPL_VAR > > name="x"/> > > syntax, but they said : > > * with <!-- you can do what you want Sounds like Paul already asked them, which is great. I agree that the comment format is a little awkward. Templates will look pretty strange in my editor with color-coded syntax-highlighting. But if it means being able to use Paul's translation tool, I think it's worth it. Maybe we can keep trying to make the case to the H::T folks for an alternative. -- Owen

1 0

templates & translation
by paul POULAIN 09 Dec '03

09 Dec '03

Hi, HTML::Template has invalid tags from a html point of view : <TMPL_VAR xx> is not closed, and <TMPL_ELSE> neither. But... there is another method to write template : use <!-- TMPL_VAR xx> instead of <TMPL_VAR xx>. with this method, HTML::TreeBuilder create better the string list. So i've written a little script that changed ALL <TMPL > to <!-- TMPL > in both OPAC and INTRANET. I've commited them. So, update your CVS copies, and for future templates, use <!-- TMPL > form and NOT <TMPL > one. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

2 3

translation tool
by paul POULAIN 08 Dec '03

08 Dec '03

Hi all, I've improved the translation tool. It now delete useless character at end of string (like ":" ) It also mark ***** ( five stars) on untranslated strings. It's just easier to find untranslated strings. I've commited 100% translated french opac with this tool. It works fine. I also have added a minor feature in opac, and can confirm it's easy to translate Koha with this tool. Only 1 thing will be added in the next days : not writting a translated template if it hasn't been modified since previous "tmpl_process.pl install", to avoid dozen of commits. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Output.pm and include files
by Owen Leonard 08 Dec '03

08 Dec '03

I was deleting some include files from the directory of our custom template, and now we're getting errors about missing files. It looks like Output.pm is trying to find some of these includes, but why? What's it trying to do here: sub startmenu($) { # edit the paths in here my ($type)=shift; if ($type eq 'issue') { open (FILE,"$path/issues-top.inc") || die "could not find : $path/issues- top.inc"; } elsif ($type eq 'opac') { open (FILE,"$path/opac-top.inc") || die "could not find : $path/opac- top.inc"; } elsif ($type eq 'member') { open (FILE,"$path/members-top.inc") || die "could not find : $path/members- top.inc"; } elsif ($type eq 'acquisitions'){ open (FILE,"$path/acquisitions-top.inc") || die "could not find : $path/acquisition-top.inc"; } elsif ($type eq 'report'){ open (FILE,"$path/reports-top.inc") || die "could not find : $path/reports- top.inc"; } elsif ($type eq 'circulation') { open (FILE,"$path/circulation-top.inc") || die "could not find : $path/circulation-top.inc"; } elsif ($type eq 'admin') { open (FILE,"$path/parameters-top.inc") || die "could not find : $path/parameters-top.inc"; } else { open (FILE,"$path/cat-top.inc") || die "could not find : $path/cat- top.inc"; } my @string=<FILE>; close FILE; # my $count=@string; # $string[$count]="<BLOCKQUOTE>"; return @string; } -- Owen ---- Nelsonville Public Library Koha 2.0.0-pre-x (CVS)

2 1

hard coded stuff?
by Benedykt 08 Dec '03

08 Dec '03

Hi all, I am wondering whether this is good or not but in the directory of the includes there appeared a css file with hard coded path of .koha { text-align:center; background-image:url("/intranet-tmpl/default/en/images/background-mem.gif"); } Now if the whole idea by introducing templates was to separate the code from the design then this behavior does not stick to the rules. A person who tries to maintain a given translation needs to visually inspect every aspect of code in order not to overlook those kind of changes. An example: a file in .default/en directory changes. The modification includes a language string and a path to a perl file ON THE SAME LINE OF CODE. Not all diff software packages will show both but rather the whole line will be highlighted as having been modified. For a translator that means visual inspection of the code. Translators are NOT programmers. They may overlook a lot of such little modifications. I have voiced this over and over again that there is something wrong about the way koha chose to internationalize. Before koha-1.2.3 all the language strings where in the perl scripts. Now they are found in the template files. I wonder whether there exists a method of still going back to a flavor of GETTEXT to take care of translations? Benedict

3 6

character encodings in koha 2.0.0
by Benedykt 08 Dec '03

08 Dec '03

Hi, Is there a general, worked-out policy about character encodings so they stay consistent throughout a translation? By this I mean character encodings of the data in mysql, in template files. I know that the perl scripts generate "an obligatory" content-type headers to the template files before output is generated. . But the headers provide to browsers only the first part of the header, without encodings information in it, hence incomplete. Has any work been done on putting it in order? By the way, what does this mean: output_html_with_http_headers $query, $cookie, $template->output; Is the first part of the line a variable? thanks Benedict

3 2

for Chris
by paul POULAIN 04 Dec '03

04 Dec '03

Hi chris, In the DB schema (see previous post), i've listed 10 tables that are not used, or almost not used in Koha. Could you check the list & confirm deletion (look at branchcategories & branchrelations specifically) Note : i'll drop tables only in 2.0.x branch, not in 2.0.0 one (to avoid last-minut bugs) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

2 1

Koha 2.0.0RC1 released
by paul POULAIN 04 Dec '03

04 Dec '03

Hi, I've just released Koha 2.0.0RC1 : http://sourceforge.net/project/shownotes.php?release_id=201672 Pate should do a press release on friday, as this release has been put in the STABLE tree. Some bugs still present, but fully useable (& used in +5 libraries) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

english stopwords
by paul POULAIN 04 Dec '03

04 Dec '03

Hi, Could someone send me a mysqldump of an english version of stopwords table. For instance, this table is empty when you install Koha (& it can be filled, like in french installation) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0