in reply to perldoc in translation
Moin,
well, the translators will probably have a hard time. I once started writing a german introduction to xemacs (which by now has become the 'official' german intro page) and I can tell that writing docs is no fun. Usually you won't be as accepted in the open source scene when you're writing docs (or do graphics or webstuff) compared to writing a programm. This is a real problem with the commnunity! You're probably off with a better reputation when you're writing the 10,000th email programm/IRC client or editor than when you're providing good docs.
More than that I have made the experience that you receive patches/bug reports and feature requests for a programm _much_ more than for the docs you wrote.
well, the translators will probably have a hard time. I once started writing a german introduction to xemacs (which by now has become the 'official' german intro page) and I can tell that writing docs is no fun. Usually you won't be as accepted in the open source scene when you're writing docs (or do graphics or webstuff) compared to writing a programm. This is a real problem with the commnunity! You're probably off with a better reputation when you're writing the 10,000th email programm/IRC client or editor than when you're providing good docs.
More than that I have made the experience that you receive patches/bug reports and feature requests for a programm _much_ more than for the docs you wrote.
An argument from a totally different direction is that I really prefer reading the docs in english. For one it keeps my english uptodate, or even improves it, on the other hand I always have the feeling of "missing" something in german docs; it's the (unconscious) feeling that translated docs are probably outdated.
And as a closing I will hereby offer to help translating a bit :) (insert usual time blurb here...)
| Regards... | Stefan |
| you begin bashing the string with a +42 regexp of confusion | |
|
|---|
In Section
Meditations