Hi all,
What do dev-docs peoples think about it ?
if You want to be in the same direction as the de-section, You should use
the first alternative: Documentation/FR.
Thanks, in fact, this is what is noted for us in the NLC part ;)
:-)
Frank, are you evaluating other tool than the wiki to handle the
documentation ant its workflow?
Marko provided Frank another tool. He set up a testinstance of Plone 3.0.x as
playground. I put one of my docs inside that framework. There is also the
framework for translation installed. It's very easy to hold translations
inside Plone together. It's not necessary to operate with special URLs. It
works right out of the box ;-)
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 :-)
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.
- 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 :-)
- 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 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
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
- Building a localization (and publication) framework around
mediawiki would be an interesting thing to do and others
using mediawiki may benefit from 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'll see to draft something and send it out to NLC for
discussion after I returned (I guess I promised that
several times before, bear with me...)
Namaste
Frank
--
Frank Peters, Co-Lead
The OOo Documentation Project:
SIGN UP - PARTICIPATE - CONTRIBUTE
IT'S FREE! NO OBLIGATIONS!
http://documentation.openoffice.org
http://wiki.services.openoffice.org/wiki/Documentation
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
