Smarty

[boots]

@cod3x: nice, but constants are a little bit expensive. For my limited needs, config files do the trick and work very similiarly. Also, AFAIK, the ## syntax resolves to fewer method calls than a plugin function.

[AZTEK]

This all just goes to show that much like anything else in programming it can be done multiple ways. Each with its own strengths and none better then another.
_________________
"Imagine a school with children that can read and write, but with teachers who cannot, and you have a metaphor of the Information Age in which we live." -Peter Cochrane

[cod3x]

@boots: from what I understand in php versions later than 4.3.3 the performance impact of constant usage is much less than it use to be. Here's a bench test done over at phpmag: http://www.phpmag.net/itr/online_artikel/psecom,id,546,nodeid,114.html

The cost of constants is something worth checking into though, I'll see if I can set up some benchmarks for the different approaches. I'm not sure what you meant by '## syntax' though, can you explain that one for me?

@AZTEK: Indeed, and the more ideas that people bring forth gives more tools for people to select the best one for a particular job. Mine filled a need as I was working with a system that had already established a multi-lingual system built on constants.

Just a side note, you live right down the road from me AZTECH lol, I live in humble Crawfordsville, IN.

[boots]

@cod3x: when loading (static) data from config files, you access vars (or labels, if you prefer) using the {#var#} syntax. This gets replaced in the compiled template as a direct lookup into the array structure loaded by {config_load}. On the other hand, using a plugin results in at least one function call (and I think, perhaps a method call) per substitution.

http://smarty.php.net/manual/en/language.config.variables.php

Thanks for the link, btw, I'll give it a look.

@aztek: you hit the nail on the head. It is a good thing to have many different solutions since each has different strengths and weaknesses.

[cod3x]

@boots: thanks for that. after looking over that, I have to agree with you that that method would be significantly faster than the constant alternative. I have another project that I'm working on that this would work great with. Thanks again!

[boots]

@cod3x: of course, profiling and benchmarking is the only way to measure which method is truly faster in your usage pattern. My instinct is that the config files will perform better, but that doesn't make it necessarily so

[szen]

I use this:
http://smarty.incutio.com/?page=SmartyMultilanguageSupport
But i want to use ##L_EXAMPLE## in template and directly in PHP is ther any way to do this?

[kills]

have a try:

$smarty->config->YourConfWar
http://smarty.php.net/manual/en/language.config.variables.php

not tested yet

[timurv]

I use xml method for translation storage.
And use simple smarty block function like {t}{/t}

May be it's offtop, but:

[kills]

[AZTEK]

You could probably do something like

[kaiska]

Hi,

I use this multilingual template solution ({t}{/t}) but I don't understand how to make cache work with it. If I cache the french page, the I switch to italian, the page shown is ever in french. I would really apreciate any help
Thanx in advance !

[AZTEK]

You need to use the current language in the cacheid. So [php:1:54254210d4]$smarty->display('blah.tpl')[/php:1:54254210d4] would become [php:1:54254210d4]$smarty->display('blah.tpl', $lang)[/php:1:54254210d4]
_________________
"Imagine a school with children that can read and write, but with teachers who cannot, and you have a metaphor of the Information Age in which we live." -Peter Cochrane

[Dr DLP]

Hi

This seems very complicated!
I really prefer using lang_keys :

[s0undt3ch]