On Thu, 2004-06-10 at 09:14, Kate L Pugh wrote:
On Wed 09 Jun 2004, Mart?n Ferrari yo@martinferrari.com.ar wrote:
- To treat the templates entirely as user configuration, nobody will
use them as bundled, because we all want to have our own look&feel.
I'm not happy about people using anything other than the templates in the distro, since they still have some application logic in them. We have had bugs in the templates; I'm sure there are still some lurking. Using custom templates is very much done at your own risk.
Well, I think you will agree that -even in english speaking sites- is always neccessary to customize the templates. If there is danger because of the templates having logic, the logic thing would be to isolate that logic.
- To separate look&feel from strings and some logic inside the
templates. Look&feel would be config (css + structure), and the strings could be managed in two ways: language templates, defining variables (the templating system is *very* powerful); and using gettext (standard way, but more hacky to implement here)
Locale::Maketext looks interesting: http://search.cpan.org/~sburke/Locale-Maketext/
I have just read the Locale::Maketext doc, and I think it would be too complicated just for webpage translation...
One idea: the templates system allows for inclusion, branching and variable defining, so we can select the language at the start and then load language-specific files which define variables then replaced in the look&feel templates.