Everyone seems to like and support the Arch wiki.
Do the licenses allow a simple mirror of Arch wiki
Append a large capitol A at the end of all article/chapter/heading

replace with an S or nothing at all when changeover is complete.

Or is that cheating?

[FLAME_THROWERS_ON]

john

Some of us think that documentation must be written in English *then* translated in other languages if need be.

But why not let people write directly in their native language?

<off topic>This discussion reminds me that more than 30 years ago, I translated in French a Basic interpreter (both keywords and messages).
By that time I could load into 64 KB of RAM two versions of the interpreter, and there was still enough room for other stuff. Oh, well... </off topic>

Fair enough, people are free to do whatever they want but I'm sure everyone [edit: s/everyone/I/] would rather have one complete Slackware wiki (as opposed to a number of incomplete wikis in 10 languages)

I am not sure what *everyone* wants, but I am sure that people who do not speak nor read English would be pleased to get *some* documentation in their native language.

That certainly would not prevent *anybody* willing to complete the English documentation to do so.

I suppose that people writing documentation will be volunteers, so let them choose the tasks they would like to complete, as long as they are useful.

Otherwise you will soon lack volunteers.

As I said, everyone is free to do whatever they want.

My view on the project was that there will be one "official" wiki in English (ideally verified and approved by Slackware developers) and the rest will be translations (ie. mirror copies of the official one). If people first start writing in their native languages, there will be a number of wikis being developed independently from one another and most probably sooner or later differing in contents, which I guess is not the end of the world but... Nevermind, these are just my ramblings...

Sounds like a great idea and something I'd like to contribute too. Problem is I don't know where to start or what to contribute!

Not sure if this will be the "official" one or not, but this is the link that AlienBOB put up earlier. Here

deleted.

deleted.

1 members found this post helpful.

Just one minor edit needed:
Change this:
To this:
OK otherwise.

deleted.

I've registered at SlackDocs now.

I think it is great to see this initiative picked up so enthousiastically!

There is a mailing list now, http://lists.alienbase.nl/mailman/listinfo/slackdocs
It can be used for content related discussions, kikinovak and I had a small email exchange which I will also forward to that list. Like, he suggested that the SlackBook content gets copied as part of the Wiki so that we have a body to work on.
That will require us to find a docbook-to-wiki-markup converter...

Eric

---------- Post added 20th Aug 2012 at 10:41 ----------

I think it is great to see this initiative picked up so enthousiastically!

There is a mailing list now, http://lists.alienbase.nl/mailman/listinfo/slackdocs
It can be used for content related discussions, kikinovak and I had a small email exchange which I will also forward to that list. Like, he suggested that the SlackBook content gets copied as part of the Wiki so that we have a body to work on.
That will require us to find a docbook-to-wiki-markup converter...

Eric

Is this any use: Pandoc?
http://johnmacfarlane.net/pandoc/index.html
EDIT
http://slackbuilds.org/repository/13.37/office/pandoc/
EDIT AGAIN & AGAIN
Needs a hell of a lot of Haskell!
But there is a sbopkg queuefile for it.

I subscribed to the mailing list. I hope in some small way I can eventually make a contribution.