It's not so simple. Most of the text is in templates, and easy to translate. However, a lot of important stuff is in the database and must be translated there. Plus, dates needs a proper configuration of the Date::Format library. And some things cannot be translated without having to manipulate the Perl code, for example a number of buttons in form!
So, it's not straightforward. To answer your questions, no, Slash was not designed with localisation in mind and in a lot of places in the code, it shows. But with some effort you can have a complete translated system, for example at Slash-Italian we have a 99% translated Italian version of Slash.
Keep in mind it's not an easy and especially short task.
Templates (Score:1)
Re: Templates (Score:2)
So, it's not straightforward. To answer your questions, no, Slash was not designed with localisation in mind and in a lot of places in the code, it shows. But with some effort you can have a complete translated system, for example at Slash-Italian we have a 99% translated Italian version of Slash.
Keep in mind it's not an easy and especially short task.
Check out the Slash in Italian Project [kenobi.it]
Parent
Re: Templates (Score:2)
--
You can't grep a dead tree.