Why can't we have multiple languages for pages?
Right now it is only possible to manage languages for CD articles. HTML pages can't be managed in different language. Why's that? Multi-language site needs every page to be presented in its own language.
Coming from a multi-lingual country (Switzerland) I can only agree with this. I would also like to stress the fact that VARIABLES need to be maintained multi-lingualy, and that there should be directives (conditional processing) in templates and HTML files that would allow text to be targeted for specific languages and/or audiences. Maintaining seperate files for is just not practical enough.
Agree. We are currently developing multi-language site (English+Norwegian, hopefully more languages to come). Our big problem is to be able to specify language-specific variables that will be automatically replaced with respective language version when publishing the site. Translating the whole article is just not good enough. I like the way CD works in general, but unfortunately its multi-language support is too limited.
It's good to hear from people who could actually use the multilingual version of CityDesk! We haven't had enough feedback on this yet (as you can tell).
Probably not quite what you need, but this site:
Unfortunately our site is still being developed, so I can't point you there. Here is in brief the problem we have. We have the set of tags (variables) that we want to set globally. Your suggestion to have a variable per language is a workaround, but ideally we'd like to have an indication of which variables have been created/updated. For example, we create a new variable for a new product: "KillerApp". If we have to create "KillerApp-English", "KillerApp-Norwegian", we won't see if some language is missing. Basically we need the same principle that you use for articles: good indication of what's left to translate.
I would suggest that the variables also be translated. This would allow all languages to use the same templates.
Fog Creek Home