Re: [Krang-devel] Template localization in place

[Bodo S. <bo...@le...>]

> P.S. Just to clarify, all future template development should be done to the 
> .base files, correct? What about bug fixes on the branch? Should every fix 
> done to a legacy template on a branch be duplicated in the new template on 
> the trunk? (For example, I made a fix yesterday to Group/edit_view.tmpl on 
> the v3.01 branch; should I now go and update Group/edit_view.base.tmpl on 
> the trunk?)

On the trunk at least, all development should be done in the *.base.tmpl
templates, yes.  And of course, it would be nice if you ported your
changes on branches to those new base templates. :)

Then, even if you don't want to use the localized templates, it's easy
to update the legacy one from there.

As an example, lets take your Group/edit_view.tmpl.

1. Put your changes in Group/edit_view.base.tmpl

2. Generate the English version (that's the default, even without having
   any AvailableLanguages in conf/krang.conf)

   bin/krang_localize_templates --verbose --pkg Group --tmpl edit_view

This will generate:

   Group/en/edit_view.tmpl

3. Move the generated template one level up in the dir tree and delete
   the 'en' subdir.

The only difference between the legacy template and the generated
English version will be in the JavaScript part, because alert() and
prompt() will pass their argument to Krang.L10N.loc() first.  This might
seem strange, because we could localize those messages and prompts right
away. However, it may be useful in the future, when possibly putting all
the JavaScript in their own file(s).  If this is considered bad, it's
easy to replace Krang.L10N.loc() with tmpl_lang tags.

Thanx for looking in it, Noam.

Best, Bodo