Maybe this answer os not what you meant but I use some tags stored in
the database so all the translations I have it stored and then retrieved
passing the desired language as a parameter, then put all the data in
the stash so the template could be used for every language you can think of.
Giancarlo
Keith Hasely wrote:
Hey All,
We are evaluating different frameworks to use, and one big aspect of the
project is how translations are handled, we deal with at least five languages
on a regular basis. I am hoping to get some input on different template
systems, and ways you all have dealt with the multilingual issues in Catalyst.
We've been using XML XSLT translations, but people in the office find it
challenging working with instead of an HTML template system.
I've seen some modules in CPAN that help with the issue such as "Catalyst::Plugin::I18N"
which seems to work with Template Toolkit, and Pedal. There seems to be some concern over here
with the overhead HTML template systems will take up compared to working with XML XSLT
translations. I've also noticed the "Catalyst::View::XSLT" class which means we wouldn't
need to come up with a new system to get our content translated before we publish.
Thanks,
Keith
_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
