Home > Archive > PHP Smarty Templates > August 2005 > Re: [SMARTY] I18N/L10N: Best practice
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: [SMARTY] I18N/L10N: Best practice
|
|
| Katana 2005-08-08, 5:04 pm |
| > Would you recommend solutions which use a marker inside the sources
> to mark strings for translation, leaving the original strings inside
> the sources, like gettext does ('t("no messages")'), or prefer a
> solution which only refers to abstract hierarchical IDs inside the
> sources, for example like 't("msg.list.nomsgs")'?
If you go for the DB driven solution, you have to implement caching
using flat files, definitely.
As far as I'm concerned, I think that using a DB here doesn't make much
sense... you would be reinventing the wheel. Whatever you do, you have
to identify the strings, so you need to run a script or something in
order to index the content...
I would definitely suggest the good old gettext approach :)
Bertrand
| |
| Joe Stump 2005-08-08, 5:04 pm |
| Might want to check out the PEAR Translation package too (there are
two of them I think).
--Joe
On Aug 8, 2005, at 2:30 PM, Katana wrote:
> If you go for the DB driven solution, you have to implement caching
> using flat files, definitely.
>
> As far as I'm concerned, I think that using a DB here doesn't make
> much sense... you would be reinventing the wheel. Whatever you do,
> you have to identify the strings, so you need to run a script or
> something in order to index the content...
>
> I would definitely suggest the good old gettext approach :)
>
> Bertrand
>
> --
> Smarty General Mailing List (http://smarty.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
--
Joseph C. Stump
joe@joestump.net
http://www.joestump.net
|
|
|
|
|