Hi Sophie, Frank, all, as I explained on dev-documentation-list I see some difficulties with the wiki framework. I'll try to explain them inline.
Am Freitag 11 Januar 2008 10:44:42 schrieb sophie gautier: > Hi Frank, all, > > Frank Peters wrote: (...) > > With the updated wiki engine (that will hopefully be available > > soon), however, we will get the DISPLAYTITLE functionality that > > allows a different title to be displayed. This would allow the > > pages to share a common page name, but still display a > > localized title. > > > > We would also need to agree upon a wiki page title scheme > > that makes it easy to handle the URLs. Engslih being the > > lingua franca of IT, I propose to use English page names > > for the wiki pages. That means, even if you create a French > > page inside the French Documentation hierarchy it would need to > > have an English page name (that would only affect its URL!). > > This is the difficulty I see here. The wiki is open to every body, how > do you do if do not know a word of English? > I worked a bit with the doc-wiki and found it difficult to set multilingual switches (beside the other problems with the actual wiki-version). If we want to involve more contributors from nat-lang-projects we need a much easier way to set and hold together the relations between documents on the same topic in different languages. Inside the wider OOo-Community we use tools that fit much better to this requirement, because there is a multilingual support right out of the box inside: plone. There are some community members around that can share there experience with this framework. It's not that difficult to implement and maintain ;-) And you could set up rights for contribution for every folder/part from very low to high(er) (without workflow to workflow with many steps). So the entry level for a contribution for the user mustn't be higher than inside the wiki (only login). (...) > > Another issue that must be addressed is how to get notified > > if wiki page localizations get out of sync. To be able to > > do that, one must define a master language and I don't know if > > we actually want to do that. > > We always take English as the master language, but the difficulty here > is what Alex have very well explained in his mail [1]. Do we have > localized page in sync or do we have topics/features that we document in > our own language (meaning different requirements)? If we use the recommened CMS the contributor is able to use his natural language as the starting point. He mustn't translate the topic into another language and the 'translator' mustn't use the same title/URL. Regards, Andreas -- ## Content Developer OpenOffice.org: lang/DE ## Freie Office-Suite für Linux, Mac, Windows, Solaris ## http://de.openoffice.org ## OpenOffice.org Portable: http://oooportable.org ## Meine Seite: http://www.amantke.de --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
