Hi,
Scott Carr schreef:
Frank Peters wrote:
Per Eriksson wrote:
[...]
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.
Maybe limited, but I think wiki is the way to go.
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.
Yes!
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 can create any filters that are needed between the different formats.
Ideally we would have two buttons on every wiki-page. A pdf-button and a
odf-button. The first one is probably already possible. The second one
is a very important rfe for OpenOffice.org and for the ODF-standard.
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.
Simplistic Markup is actually a good thing in this case. It means a low
barrier for contributions.
Having another way to contribute for the "heavier" documentation is a
good idea as well.
No matter how big a document is. A wiki-page can be a Chapter or a
paragraph. Wiki-pages can automatically build a toc and every
sub-paragraph can have it's own edit button.
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.
Some of the pages on WikiPedia have some pretty nice formating.
I am a little bit worried about screenshots (pictures in general).
--
Regards/Groeten,
Arthur Buijs
Co-lead NL.OpenOffice.org
Open software is a joy forever!
http://nl.openoffice.org
#nl.openoffice.org (irc.freenode.net)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
