faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
Re: Translation
by david on Monday 27/Jun/2005, @00:44
|
>>I mean the principle of wiki: low entrance barrier for participation.
>Not suitable for translating software
>You need some barrier, in order to maintain quality.
Equally unsuitable for an encyclopeadia then, since you need to maintain quality there too. |
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: Translation
by rinse on Monday 27/Jun/2005, @00:56
|
Well, you should at least keep in mind that a wiki encyclopeadia could contain errros.
But the difference between an wiki encyclopeadia and is that the lather uses instant publishing. You read the article, you notice an error, you change it, and it gets published as soon as you hit the 'publish' button (or similar)
This is not the case with software documentation, if you find an error and correct it, the improved docs won't be available until the next version of the application, which could take 6 months or even longer (depending on the release cycle the application uses...)
So in short, while a wiki encyclopeadia with a large audience would quite fast gain in quality, it would take a lot longer before software documentation would reach the same quality level if it was translated in the same way.
Also, users who don't upgrade everytime a new version of the application comes out, will be using the documentation with errors for a very long time..
|
[
Reply To This | View ]
|
Re: Translation
by ac on Monday 27/Jun/2005, @04:40
|
That's indeed commonly claimed to be a weakness of wikis.
|
[
Reply To This | View ]
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|