Hi Orchard fans, I'm a bit stuck on creating a multilingual website (2 languages). There is documentation available on how to create global-ready applications, but not so much on working with multiple languages at the same time. That part is 'work in progress'.
Now, I don't have a full knowledge of what the 'Localize' module does, but it enables me to translate pages and blog posts. But what about other content, like the taxonomies vocabulary? Tried to add 'Localization' to the Taxonomies content-type, but didn't get that to work. To enable language selection, I tried the Culture Picker module, which implements the ICultureSelector interface. That works for pages but not (yet) for blogs or lists. 'At the end of the day' I feel as if the localization feature (with respect to multilinguals sites) is not fully a first class citizen, am I right? I like the new ideas by the steering committee for future versions of Orchard very much, but it might also be wise (and the dev team is probably doing that already) to take a moment and focus on quality for the existing features. In my opinion, it should be possible to localize every module and use it in a multilingual site. My gut feeling is that it's getting harder to correct a system at a later point. Luckily, Orchard is so flexible and extensible that you can create modules that solves all kinds of system issues, but I think it´s good to temper the growth of modules in the gallery that do things to ´correct´ the core. The fact that the Culture Picker needs to do all kinds of stuff not related to 'selecting a culture' (like filtering menu-items) states that the core/framework is not anticipating enough to enable a culture switch in a multilingual website. I'd like to know how far the 'work in progress' is regarding to localization and, of course, contribute to the system in any way I currently can. Best Regards, Geert Doornbos
