Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

Archive /

Our old forums are still available as a read-only archive.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo


Go to End

5 Posts   2558 Views


Community Member, 21 Posts

13 April 2007 at 1:29am

I did not see i18n support on the road map. Is it planned and if - when will it be implemented?

What kind of workaround do you have to offer for multilingual sites?

Thanks for answer.


Forum Moderator, 628 Posts

13 April 2007 at 8:54am

Edited: 13/04/2007 9:09am

Definitely planned... as part of the Google Summer of Code program, the blog :)

By "work around", do you mean for the public facing part of a website to have two (or more) languages available, like ?

(rather than the admin area)

You should also see


Community Member, 21 Posts

13 April 2007 at 8:10pm

Exactly like at - two different languages at the front page.

The admin interface is another thing - I guess it is not priority 1 since most of the people are able to read english - but offering content in several languages is an important feature and could be a showstopper in many cases for systems which do not offer this feature.

How is the multilingual content realized?

Thanks for answer.


Google Summer of Code Hacker, 11 Posts

13 April 2007 at 10:09pm

Hello everyone, I am the person who is going to do the i18n work. I am Catalan and have previously worked in translating applications like SmartFTP or QCD Player, and Content Management Systems like Exponent or phpBB Plus.

I'd love to know what sorts of features you have in mind, so we can consider all of these for when I begin. So this topic is open to discussion :)


Community Member, 1 Post

17 April 2007 at 6:06am

Edited: 17/04/2007 6:07am

Yes, i18n is indeed a point many CMS miss to implement in an elegant way. Often you have to build up an individual page tree per language. That way pften makes it impossible for visitors to switch from page "foo" in language 1 to the same page "foo in language 2. Instead, the user is taken to the start page when switching the language.

I like the way language switching is done on Can someone tell me how this is accomblished? I'd like to switch to SilverStripe and this way of i18n is a key feature I need. I'm usually working with Typo3 (which does i18n very nicely) but would love a CMS that's less resource-hungry and easier to understand for my customers. And I think SilverStripe could do it!