docs/master

changeset 189:22feb390ccc4

Applied suggestions by Lydi.
author markus schnalke <meillo@marmaro.de>
date Wed, 11 Jul 2012 15:53:53 +0200
parents a0b5050878a0
children 2443264b1745
files summary.roff
diffstat 1 files changed, 22 insertions(+), 18 deletions(-) [+]
line diff
     1.1 --- a/summary.roff	Wed Jul 11 15:53:40 2012 +0200
     1.2 +++ b/summary.roff	Wed Jul 11 15:53:53 2012 +0200
     1.3 @@ -26,30 +26,32 @@
     1.4  
     1.5  .U2 "Outlook
     1.6  .P
     1.7 -The work done during the project is not finished.
     1.8 +The work done during the project is not finished. \" XXX yet?
     1.9  Several tasks are left to do.
    1.10  .P
    1.11  MIME handling is the most complex part of mmh and it requires
    1.12  general rework.
    1.13 -The changes already done to it build upon the existing structure.
    1.14 -Yet, MIME support is not truly integrated.
    1.15 +.\" XXX rewrite these sentences for more smoothness
    1.16 +The changes already accomplished build upon
    1.17 +the existing structure only.
    1.18 +To integrate it fully into the concepts.
    1.19  For instance, accessing messages and accessing MIME parts of messages
    1.20  have inherently different concepts, although a single concept should
    1.21  cover both.
    1.22 -The sequence notation should provide a way to address MIME parts directly.
    1.23 -Furthermore, the sequence notation should be made more powerful in general.
    1.24 +The sequence notation should provide a way to address MIME parts directly
    1.25 +and should be more powerful in general. \" XXX more powerful
    1.26  For instance, it is currently not possible to access the second last
    1.27  message in a given sequence.
    1.28 -Displaying messages with
    1.29 +Also, displaying messages with
    1.30  .Pn show
    1.31  requires further rework.
    1.32 -Encrypted messages should, for example, be decoded automatically
    1.33 +Encrypted messages should be decoded automatically
    1.34  and digital signatures should be verified on-the-fly.
    1.35  The whole task should be aligned with the common behavior of other
    1.36  mail clients.
    1.37  MH's unique features should not be lost, but the default should become
    1.38  less surprising.
    1.39 -Transfer-decoding of the quoted text in replys and encoding of non-ASCII
    1.40 +Transfer-decoding of the quoted text in replies and encoding of non-ASCII
    1.41  characters in message header fields like
    1.42  .Hd Subject
    1.43  remain unsolved.
    1.44 @@ -64,13 +66,13 @@
    1.45  .Pn sortm .
    1.46  Related to
    1.47  .Pn sortm ,
    1.48 -a threaded message view is completely missing in mmh, yet.
    1.49 +a threaded message view is completely missing in mmh, so far.
    1.50  .Pn pick
    1.51  could be enhanced by message indexing.
    1.52 -These fields are worthwhile for research.
    1.53 +These fields deserve further research.
    1.54  .P
    1.55  The features most often asked for are Maildir and IMAP support.
    1.56 -Yet, both of them collide with MH in the same fundamental way as
    1.57 +But, both of them collide with MH in the same fundamental way as
    1.58  different filesystem approaches would collide with Unix.
    1.59  Nevertheless, an abstraction layer could provide a mapping from such
    1.60  storage back-ends to the MH storage format.
    1.61 @@ -98,7 +100,7 @@
    1.62  I started to create an experimental version to convicce by demonstration
    1.63  of the result.
    1.64  .\" behind closed doors; talks I've given
    1.65 -My work on mmh was independent of the nmh community.
    1.66 +My work on mmh was independent of the nmh community. .\" XXX clarify
    1.67  .\" XXX straight?
    1.68  This enabled me to follow my vision straightforwardly and thus produce
    1.69  a result of greater pureness.
    1.70 @@ -108,23 +110,25 @@
    1.71  improvements by change.
    1.72  It shall present a lean appearance that is simpler to understand
    1.73  and work with for developers and users.
    1.74 -By all means, my work on mmh shall improve nmh in some way.
    1.75 -Improving nmh directly in the way I wanted was impossible for me
    1.76 +By all means, my work on mmh shall improve nmh somehow.
    1.77 +Improving nmh directly in the way I wanted was impossible
    1.78  due to personal and community-related circumstances.
    1.79  The mmh project is my way to offer my gifts though.
    1.80 +.\" XXX zweimal ``my way''
    1.81  .P
    1.82 +.\" XXX
    1.83  During my work on mmh, the community of nmh suddenly became very active.
    1.84 -They have worked on nmh in parallel to my work on mmh.
    1.85 +In parallel to my work on mmh, they have worked on nmh. \" XXX rewrite
    1.86  There was no collaberation in our work, except that I have pulled some
    1.87  changes from nmh to mmh.
    1.88  Our work was motivated partly by similar and partly by different aims.
    1.89  Although some changes are common among both projects,
    1.90  fundamental differences exist.
    1.91  My experimental version thus more and more felt like being a fork.
    1.92 -I am undecided how I like to treat it.
    1.93 +I am still undecided how I like to treat it.
    1.94  .P
    1.95 -Yet, I am strongly convinced that the decisions taken for the
    1.96 -development of mmh were good ones with regard of my goals,
    1.97 +I am strongly convinced that the decisions taken for the
    1.98 +development of mmh were good ones regarding my goals,
    1.99  and I like to push the project farther in this direction.
   1.100  
   1.101