Re: [SMARTY] smarty and GNU gettext

hi -

> > also, for performance and clean templates, what about just using config
> files?
> > {#someString#}
>
> They're clumsy and unmanageable when the ammount of translation items and
> languages goes beyond a certain limit. A db is much more manageable.

well, there are a few different issues:
authoring (maintaining)
template cleanliness
runtime performance

whether or not we build a web front end + db to manage the string
editing (we have) is a different matter from how smarty accesses
things.

I wonder if you have an idea for runtime performance which is quicker:

{"someKey"|localize}

which would look up the key (db read) and then return the right lang value.

vs.

{#someKey#}

which would replace the above based on a config file (means reading in
the config as a text file eg "strings.jp" ).

i guess (2) is faster. then we just need a web front end to manage
(read/write) config files.

for many people collaborating on basis of text files would also be easier.

as written below. took us more than an hour to build it tho!

/dc

>
> > of course, some kind of management GUI would be needed for building
> > the config files, but this isnt too big a deal.
> >
>
> You can have  a q&d web front end in less than an hour, adapted to your
> needs.
>
> --
> Vicente Werner y Sánchez
>


-- 
_______________________________________________
           David "DC" Collier

[email protected]
           skype: callto://d3ntaku
           http://www.pikkle.com
           +81 (0)80 6521 9559

http://charajam.com　【★キャラ♪ジャム★】
人気キャラとJ-POP最新ヒット曲を自分で組み合わせて
待受Flashや着Flashを作っちゃおう！
_______________________________________________