if i couldn't use a database for this, i might personally opt for
using an include system. something like this:
-translations.mako
* defines textblocks like:
website_right( language ):
%if language == 'en':
hello!
%elif language == 'fr':
bonjour
%endif
page.mako
* includes translations.mako
* makes calls to translations.mako as needed
I'd do this for the following reasons:
1. if you use a different template per language , the templates will
get out of sync a lot faster and it will be harder to maintain.
updating a 'zone' would require finding it in 5 templates and then
editing those. in this solution, you'd only update 1.
2. if you have the text in an included template, instead of the app,
then you have the 'frontend' or 'integration' team responsible for it,
and testing would only be on the frontend code. i wouldn't want to
spend backend resources or regression tests on ensuring that each
change makes the code okay.
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en.
