Smarty

Serzhik · Posted: Fri Mar 12, 2004 1:10 pm Post subject:

AZTEK, I found you method better then others! Respect! And thanx for it! Wink

AZTEK · Posted: Fri Mar 12, 2004 1:48 pm Post subject:

shaka · Smarty n00b Joined: 16 Mar 2004 Posts: 1

I think this problem applies for most Smarty i18n techniques. Using {t}Translatable string{/t} works fine, but who said all text can be surrounded by tags? What about attribute values?

I just started using the gettext method myself and ran into problems when using the default-modifier. I want to do: {$variable|default:"{t}Translatable string{/t}"}. Is there some smart(y) way to do this? Of course I can put the value in a variable in php or something, but then the whole point of the modifier is gone.

sagi · Smarty Regular Joined: 30 Jul 2003 Posts: 43

Personally I feel all variables should be translated in the PHP level.

The only other exception is |default like you say. Perhaps you could just use a regular {if}. It is also possible to add "assign" option for the block function.

Sagi

boots · Posted: Tue Mar 16, 2004 3:30 pm Post subject:

@shaka: perhaps override the provided default modifier with your own that can handle translations?

Justin · Posted: Tue Mar 16, 2004 6:42 pm Post subject:

or perhaps you could use smarty prefilters. there are some examples about such solution in this theme and in http://smarty.incutio.com/?page=SmartyMultilanguageSupport
_________________
http://www.baubas.net

DinoM · Smarty n00b Joined: 17 Mar 2004 Posts: 4

AZTEK · Posted: Wed Mar 17, 2004 11:06 am Post subject:

You will need to change your call to $smarty->register_block so that the third parameter is false meaning the output of the block is not cacheable. I just added that to my original post.
_________________
"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

messju · Posted: Wed Mar 17, 2004 11:27 am Post subject:

sorry, why would you turn on caching and then don't cache the translated texts?

AZTEK · Posted: Wed Mar 17, 2004 11:37 am Post subject:

DinoM · Smarty n00b Joined: 17 Mar 2004 Posts: 4

AZTEK · Posted: Wed Mar 17, 2004 2:23 pm Post subject:

Yea the approch by which you use the locale string as a cache id is much more useful then to just skip caching translated words entirely. Its what I would do.
_________________
"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

xces · Smarty Regular Joined: 09 Apr 2004 Posts: 77

I ain't sure it has allready been posted here, but i am building a CMS using smarty. Because i am still building this and i am adding a lot of translations i have thought of your implementation aztek but i decided to make my own.

Basicly what i have done is this; I made 3 tables in the database they are build up like this:

messju · Posted: Wed Apr 28, 2004 8:08 am Post subject:

@xces:

if your "[here.the.variable.tag]" are just in the template, you can translate your templates at compiletime:
- use the selected language as compile_id
- transform your tags to the translated text in a pre-filter
done

if you also have these tags in the php, things get a little more complicated.

xces · Smarty Regular Joined: 09 Apr 2004 Posts: 77

Hmz, so you are saying that it is possible to create compiled templates for each language. That is interesting I did not know that. That means i don't have to do the caching of mysql.

Secondly, i am using this from within my PHP tags, but that is very rarely. I could think of a way to skip that and just use the templates for the variables.

edit:
Actually, looking at prefilters right now, i did it all wrong :0 The way it works right now is ok, but not perfect;
Because right now i have:
- Run PHP code and assign translated text to smarty
- Run a postfilter to replace all remaining translations

This all could be done like this:
- Run PHP code and assign translated text to smarty
- Run a prefilter to replace all remaining translations, because postfilter is kinda obsolete here.

Right?

(but)

Why i assign the translated text from within PHP:
For example, i have this string in the database:
"This album was last edited by %s on %s at %s."

Eventually, this will be replaced by this:
"This album was last edited by me on 28-04-2004 at 18:24"

Is there a way to change this so my templates will hold all the translation strings? I could try to use a

Some remaining questions:
- Right now i have force_compile to true, because i am developing, but is this really needed? When i change a translation of a variable and i don't have force_compile on but do have compile_check on, does smarty recognize the changes?
- Can you explain some more on the compile_id, this is kinda "not yet" documented enough for me to understand it correctly.