Per Eriksson wrote:
I personally agree this is better than uploading files to issues.
To be honest, I don't like the fact that we use issues to track docs
anyway. Issuetracker is bulky and obscure. I would strongly vote for having
a readily visible dashboard with links to project pages on the wiki that
describe what happens on a project/document. Wiki
allows
discussions on the topic, too, without the need to bring up
issuezilla.
I don't know how to handle document repository and versioning as such, collab.net does not appear to offer anything useful out of the box and
mediawikis capabilities are very limited here, too.

I have no experience with Pootle, I thought that was predominantly for
localization purposes. How would that need to be implemented? Can someone
explain?

Pootle is for localization only, but it has huge benefits. It's a web based
solution, it's easy to use, keeps track of users and changes.

So does a wiki. It keeps a full history of changed and is web based.

The right web-based solutions coult automatically export the content to XML,
HTML, PDF, ODF etc. without having to copy from the wiki, re-create all the
tables, do formatting etc. to export to different files.

That's also possible with wikis. There are some (perhaps low quality)
filters for mediawiki but it shouldn't be too hard to get from mediawiki
markup to XML, ODF, or HTML markup. When we put application help to the
wiki we will need to go that route.

I think if such a solution exist, it should be used, and serve the purpose
that Pootle serves. I really think that the wiki is plan Z here, as the
documentation has loads of formatting that doesn't work with the wiki.

I don't exactly agree. The problem with wikis is that they use a
simplistic markup language with little structural possibilities.
This can be worked around. But they have the huge advantage of allowing
easy contributions. But I need to look at Pootle to get a better idea
of it.

And as to the formatting, I don't exactly know what you are referring
to. I agree that some very sophisticated formatting is hard to
realize with wikis but most of it should be pretty straightforward.

Frank

--
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]

Reply via email to