Martin Sarfy wrote:
Hi folks,
I lack multiple language support in HTML::Template.
Hi,
(back from holidays, hence the late answer)
The Koha project (www.koha.org) uses HTML::Template.
and has several languages (english, french, polish, chinese, others to come)
To do this, we wrote a script that
Markus Spring wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Sarfy wrote:
| Hi folks,
|
| I lack multiple language support in HTML::Template.
..SNIP..
3 is done by subclassing HTML::Template to recognize filter arguments as
a part
of the cache key (idea and code from Cees Hek), so tha
On Fri, Aug 27, 2004 at 03:33:23PM +0200, Markus Spring wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Martin Sarfy wrote:
> | Hi folks,
> |
> | I lack multiple language support in HTML::Template.
>
> My way to do it is as following:
>
> 1 Have Templates in one basic language
> 2 U
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Sarfy wrote:
| Hi folks,
|
| I lack multiple language support in HTML::Template.
My way to do it is as following:
1 Have Templates in one basic language
2 Use Locale::Maketext as basic functionality to retrieve localized text strings
3 Use templa
* Martin Sarfy <[EMAIL PROTECTED]> [August 24 2004, 23:23]:
> > > Using construct isn't appropriate for several reasons:
> > > -- $lang is not accessible in context
> > Use global_vars and it will be.
> It's good that global_vars is not set by default, clean namespace in
> is advantage and I
> On Tue, 24 Aug 2004, Martin Sarfy wrote:
>
> Using construct isn't appropriate for several reasons:
>
> -- $lang is not accessible in context
> -- it's too clumsy for manual writting
> -- is not 'system' solution, it cannot handle e.g.
> substitution of similar languages or so.
H
Here's the solution I applied to this program in a project of mine.
In my templates, I prefix my tokens with lang_.
e.g.: , , etc...
Then, I overloaded HTML::Template and used my own new method to which, on
top of the usual HTML::Template parameters, I pass the language I want to
use.
In there,
On Tue, Aug 24, 2004 at 12:07:32PM -0400, Sam Tregar wrote:
> On Tue, 24 Aug 2004, Martin Sarfy wrote:
>
> > Using construct isn't appropriate for several reasons:
> >
> > -- $lang is not accessible in context
>
> Use global_vars and it will be.
It's good that global_vars is not set by defa
Mark, first of all, thank you for a wonderful piece of expirience!
Your way of separating things definitely worth attention. I'm going to
try it for my next i18n-enabled project.
One little thing I'd like to mention. Let us all use full locale names
instead of ISO language codes.
de_DE.ISO8859-1
From: Sam Tregar <[EMAIL PROTECTED]>
>> -- it's too clumsy for manual writting
>
>I don't understand what you mean by this. If you consider
>HTML::Template's syntax to be too clumsy then why are you using it?
I understand what he's saying. When initially facing the chore of international
langu
On Tue, 24 Aug 2004, Martin Sarfy wrote:
> Using construct isn't appropriate for several reasons:
>
> -- $lang is not accessible in context
Use global_vars and it will be.
> -- it's too clumsy for manual writting
I don't understand what you mean by this. If you consider
HTML::Template's
An alternative that I use:
In the template file, use a simple VAR tag,
Store all the different language's text in a database or text files.
In the CGI, load the appropriate language based on input parameters or
cookie value,
my $lang = $cgi->param('lang') || 'en';
my $gui = load_gui ($lang);
T
12 matches
Mail list logo
