Fixed wrong german translation

[claws.git] / README.claws

diff --git a/README.claws b/README.claws
index 8b4c37c6bf7caaf8dc956a7e27c3bb20cd777649..8c3f199cbafa7f58e128a9251065d7bf93e5b026 100644 (file)
--- a/README.claws
+++ b/README.claws
@@ -74,10 +74,12 @@ are hardly noticable, but deserve mentioning:
   You can also share or use shared mail folders. Right-click a folder and
   select Property. Change the Folder chmod setting.
 
-* default reply-to address for folders
+* default to address for folders
   Most people filter mailing list mails to separate folders. Claws allows
-  you to associate a folder with a mailing list. Right-click a folder, 
-  select Property and change the Default To setting.
+  you to associate a folder with a mailing list or a person. Right-click a
+  folder, select Property and change the Default To setting. When you
+  compose a new mail, when this folder is selected the recepient address
+  will be set to this address.
 
   (NOTE: this is also a shoot-yourself-in-the-foot-setting! If you want
    to send a private mail, don't have a folder selected with this setting
@@ -99,6 +101,11 @@ are hardly noticable, but deserve mentioning:
   the path in the text entry. You can select the default dictionary.
   When composing, use the right-button click.
 
+* quotation wrapping
+  Quotation is wrapped like VIM would wrap it (at least that was the
+  goal). To enable this feature go to Common preferences->Compose and
+  make sure Wrap quotation is enabled. The text is automatically
+  wrapped when you reply to an e-mail if this feature is enabled.
 
 There are a lot more options. If you find one, don't hesitate to
 mention it.
@@ -107,13 +114,30 @@ mention it.
 How to contribute
 -----------------
 
-Write a patch, submit it to the Sylpheed ML, Sylpheed Claws Users ML,
-or bother any of the current Claws developers. There's no way to
-predict whether your patch will or will not end up in Claws or Main.
-Mostly they will. And if not, there's probably nothing wrong with
-your code - or maybe there is. Generally, adding a cool or useful
-thing to your patch will attract a lot of attention of other users
-or developers.
+Sylpheed Main: 
+
+       submit it to the Sylpheed ML, Hiroyuki, or Paul Mangan
+       (for incorporation on the Sylpheed Patches page)
+
+Sylpheed Claws:
+
+       It is highly recommended to use the sourceforge project page
+       of claws. Check: 
+       http://sourceforge.net/tracker/?atid=384600&group_id=25528&func=browse
+
+       If that's too troublesome, either contact Paul Mangan or consider
+       posting to the sylpheed claws users mailing list.
+
+       Bugs can be reported in the same way; the recommended web page:
+       http://sourceforge.net/tracker/?group_id=25528&atid=384598
+
+       Ofcourse you can also post to the sylpheed claws users
+       mailing list.
+
+Also, we really try to incorporate good contributions, but sometimes we
+don't have enough time. If the contribution is really big, or requires
+a long time to stabilize, send a mail to Paul Mangan. We can probably
+arrange access to the Claws branch.
 
 
 How to request features
@@ -122,8 +146,7 @@ How to request features
 Ask around in both Sylpheed ML and Sylpheed Claws Users ML. Note
 that some developers may already thought about your feature, may
 perhaps be implementing it - or the feature was already discussed
-and rejected for whatever reason. Don't complain, be patient. Or
-you might want to go ahead and hack a patch for it. That would
-be very cool! (c. How to contribute)
-
-
+and rejected for whatever reason.  You might want to go ahead and 
+hack a patch for it. (That would be very cool!) Another
+possibility is to use the Feature Request Tracker at the
+sourceforge project page.