We''re working out the roadmap now but a fully internationalized version of CS probably won''t be available for a month or two.
We will have our issue tracker public soon and when it''s up we''ll create an issue for i18n and you can track (and vote!) for it there.
What do you mean by "fully internationalized version" ? Unicode support, localization to different languages, something else ?
In my experience things seem to be working pretty well for iso8859-1 text and not so well for anything else.
What surprised me is that setting the environment to use UTF8 throughout broke even iso8859-1 text functionality (notably search).
However, keeping Clearspace with default iso8859-1 allows you to store and view text even in other codepages. In this case it seems the browser is smart enough to encode the text with the &#nn; character syntax which kind of gets around the single-codepage limitation. However, Clearspace itself doesn''t seem to interpret this syntax so I''m not entirely sure of possible side-effects. In any case changing to utf8 later might become problematic.
Can you give us an update on this, including whether CS will be i18n''able per user (meaning each user can pick their own language)?
Right now we''re looking at the next major version after 1.1 comes out. So, it''ll be more like the end of Q2 before this is fully finished. We originally hoped to have this done in 1.1 (at the end of this month) but we didn''t have enough time to finish the work before then.
(Direct link to the issue is here: http://www.jivesoftware.com/issues/browse/CS-161)