Smarty

[fabhren]

Greetz y'all,

I decided to 'share my lovin`' and show what a mess i made with AZTEK b-e-a-u-t-i-f-u-l-l multilang solution.

Put up a dir called xmlang. All files are [template_name]_[lang_initials].xml (eg index_de.xml).

And it goes:

[messju]

I also like Azteks approach, although i never used it. There is just one thing that joscha mentionend ages ago ( http://www.phpinsider.com/smarty-forum/viewtopic.php?t=84&p=327#327 ) that should not be underestimated: the use of a prefilter for translation.

if the translation is done in a prefilter (with distinct compile_ids for each language) the translation can be done at compile-time of the template and not at display-time (like with a block-function). this is neglibible if you employ caching on your site, but if not, a prefilter would boost performance tremendously: the xml-files don't even have to be loaded and parsed anymore when displaying the page, once it was compiled.

just my 2c.

[fabhren]

I've checkec joscha solution but when you're dealing with heavy hitting db's like oracle, and you'll have to dump a bundle o'dough in extra language packs , i'd rather build a small library of languages in xml, even if it takes the extra time to compile .

As I am thinking of cacheing most of the scripts, those that are heavy on text are always cached, while the dynamic one's have less text to translate .

In any case, xml to db is always a possibility ( when we can pay up for the extra functionality )

[messju]

maybe i misunderstand you or you misunderstood me.

i suggested a prefilter that does merely the same as your (or azteks (?)) block.translate.php . it should use the same xml-files and, if doable, use the same syntax in the templates as block.translate.php does.

[fabhren]

You're right messju I completely misunderstood you. That was, in fact, what I had in mind. I would keep the same structure but filter it a lot faster and having the complementary advantage to compile with a different compile_id for each language.

But I am just a small shrimp in this ocean of smartiness . I am just beggining to grasp the extensiability of it all.

If anyone already has this whole prefilter business sorted out , it would make my life a whole lot easier

Thanx
Fabhren

[messju]

okay, some lunchbreak-hacking:

(i took azteks stuff from http://www.phpinsider.com/smarty-forum/viewtopic.php?p=326#326
to have functiont t() etc. )

[php:1:08301de9da]
<?php


function smarty_pcallback_translate($match) {
global $__compiler;

$_ld = $__compiler->left_delimiter;
$_rd = $__compiler->right_delimiter;

$string = $match[2];
$attrs = $__compiler->_parse_attrs($match[1]);
$params = array();
foreach ($attrs as $key=>$value) {
$params["%$key"] = $_ld . 'php' . $_rd
. ' echo ' . $value . '; '
. $_ld . '/php' . $_rd ;
}
return t($string, $params);
}


function smarty_prefilter_translate($source, $compiler) {
require_once($compiler->_get_plugin_filepath('shared', 'translate'));
$GLOBALS['__compiler'] =& $compiler;

$_pld = preg_quote($compiler->left_delimiter, '!');
$_prd = preg_quote($compiler->right_delimiter, '!');
$source = preg_replace_callback("!${_pld}translate(.*)$_prd(.*)$_pld/translate$_prd!Us",
'smarty_pcallback_translate', $source);

unset($GLOBALS['__compiler']);
return $source;
}

?>
[/php:1:08301de9da]

i know i won't win a price for beauty with it and there are some questionable design-issues with the one above, but aztek's example is working with it and maybe it's a starter for somebody who is in need of this

greetings
messju

[fabhren]

Hyia messju,

Been fiddling witcha code and no can work , although it was an awesome solution , but only in a postfilter stage.

If you check in the beginning I was sending the language by php to the template. If this is a prefilter, it parses BEFORE the var gets any value and afterwards he'll try to get the xml and it'll crash and burn .

Do you have a hint to make it a postfilter ?

Thanx a lot in advance
Fabhren

[messju]

hmm, making it a postfilter won't gain you anything.

as a hint: look at the results of $compilter->_parse_attrs();
you'll get a hash array with the attribute-name as a array-key and the php-code to obtain the attribute-value as the array-value.

if (you don't need compatibility to php5 yet and) do "$this =& $__compiler;" you can eval the array-values and should get the correct results (i hope i didn't spoil and hinted too much now). but this only works if the values where assigned from php and not within a template.

another way would be using $__compiler->compile_id to get the $lang and $__compiler->_current_file to get the template-name.

HTH and have a nice weekend
messju