On Tue, 2004-06-08 at 15:49, Dominic Hargreaves wrote:
Hmm. Has anyone been thinking about internationalizing
yet? I assume the non-English language sites are currently doing this by
I have mixed-opinions about this. First of all, the templates *are*
going to be changed, this is normal in building a separate website, and
it may also be necessary in the process of moving to a different
language/culture. So while it may be a good idea to provide stock
templates in different languages, I very much doubt that this is going
to be the end of the story.
I actually planned to do this using a CVS repository, storing OG
releases on the "vendor branch", working for my Italian templates on the
main trunk and merging new releases as they appear. This is similar to
the work I've done with friend to translate Slash (the slashdot.org
engine, and another Template Toolkit project) into Italian.
For a simple software like OG based on templates, I'd suspect that a
full-blown localisation layer like Locale::Maketext will just add too
much overhead and users will write their own text in place of the
template strings. My idea is to supply more than one set of templates so
users can choose their base language, and after that they have to take
care of upgrades to their existing installation.
Multi-language sites are a different story and I don't see them
happening soon IMHO.
Alessio Bragadini <alessio(a)sevenseas.org>