Hi Frank, hi all, Am Samstag 08 Dezember 2007 05:31:51 schrieb Frank Peters: > Hi all,
(...) > > sorry for the delay in reply. I am currently in India > presenting OOo Documentation at FOSS.in hoping we can > shanghai dozens of new contributors for docs :-) > I hope so too :-) > As to the tools: I have taken a *very quick* look at > plone and although it looks nice and seems to be a little > better suited for content management I'd be reluctant > to use it for localizations for the following reasons: > > - The wiki is already there and presents an easy way for everyone > to contribute. It's inside the OOo domain and hopefully > in the future we will be able to use some federated > identity approach so an OOo member can use one set > of credentials to login everywhere. > I think there would be also no problem to do that with plone. If you want to contribute to the wiki you had to register: nothing different to plone. In plone you are able to set different rules for publication. In the wiki i don't see actual this posibility (that's normal for a wiki). > - The plone instance would be yet another access point > for users to get documentation unless we just use plone > to localize and then transfer back. The wiki is currently > not maintained by us (docs project) so we need not worry > spending maintenenace resources for it. > Leaving the wiki completely is a bad idea IMO. I am a wikophile :-) > Wiki is a good and quick tool to develop ideas and to organize work in groups. It is also fine to get informations together. But it's in in my opinion not the best framework to organize high-value documentation (because of it's name, that means quick-quick) ;-) > - Switching languages in the wiki should be an easy thing > provided we agree on one common schema: > o the localized pages sit in a defined hierarchy so URLs > to switch languages are easily generated automatically > o the localized pages need to have the same names. With the > new MW version (which we currently test and hopefully > implement soon) it will be possible to still use localized > *titles* to show up. Just the URL is the same (except for > the language identifier). That's very easy to organize in plone. The contributor has not to be aware about the URL: that's a task of the framework. > That's about all we need. If we implement a language bar > as template a user would be able to > o switch to another language with one click In plone always there ;-) > o instantly see if a localization is available or not, and if > not, start localizing right away > o add languages easily by just adding them to the template > In plone there is a translation framework insde (no need to add templates manually). You are able to translate to every supported language (I don't know, which of our languages are not supported.). > - Building a localization (and publication) framework around > mediawiki would be an interesting thing to do and others > using mediawiki may benefit from that. > May be. But I don't think, if we have enough resources to do that. > Of course, since it's you guys doing the actual work :-), > it's you to make the call, but from a users perspective, > I think, extending the wiki is the better option. > I think we should use a tool, that make it easy to contribute. My experience with the wiki is the following: It's not difficult to contribute text to the wiki. But if you want to contribute text with tables, images etc. it's very difficult to format it in a good looking way. If I do the same in plone, I get my work done in less than the half of the time. 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]
