Good Evening, >> > True also, but is adding code to the wiki the answer every time >> > something new is needed? Maybe Moin is not the right web app. What >> > usually happens every time just about when you start patching and adding >> > on to apps? >> >> Any suggestions from you, then? Which app can be the right app (being able >> to move content without hassle is a must)? >> >> Ralph > --- > Actually I have thought about it since Karan explained the exact > problems and still thinking. Let me think a day or so on it. > > The Huge problem is wiki marked up text file content. Content in web > apps is all ways a problem in migrating to a new content managment > system. So that is expected of. Thankfully so far there is not that much > of it yet. Around 150MB? As per the wiki page says. The wiki marked up > text files are not a big deal in my opinion. The biggest problem is an > app that will suffice every thing needed which in no way will ever > happen. Every system has it's advantages and disadvantages, especially when it comes to i18n. Here are a few suggestions to handle the language specific wiki content: - We could add something like a language chooser to every site, (as on openSUSE's mediawiki, e.g). - The 'auto-fallback to English' could be replaced with a 'manual fallback link with an advice' and perhaps a 'back' button. This would force the user to stay in their language context. Also we should make sure that translations are maintained continuously. This would solve most of our problems. I would suggest to set up $LANG teams who work on the l10n. Best Regards Marcus