FAQ about patches | More patches in the web | Main Page

Justify paragraphs that contain more than one level of indentation (Example)
 
Click in the link to go get the patch!
 
Here there are more examples of what this patch does for you.
 
Text before justification (from a post in the c-client mailing list). Note that there are several levels of indentations (exactly 2 before replying), and also note that there are short lines.
:) > > As NFS seems to be out, is it possible to have a large central disk
:) > > solution
:) > > which can be accessed by multiple IMAP servers?  Or is this simply not
:) > > worth
:) > > doing as you say that the disk usage is higher than CPU usage so such a
:) > > central disk solution would be crippled by all the concurrent accesses
:) > > from
:) > > the servers?
:) >
:) > This is a controversial point, but I believe the latter.  That is, I
:) > believe
:) > that a central disk solution is not the way to distribute something as
:) > I/O-
:) > intensive as mail.
:) >
:) > Of course, a central disk solution is ideal for files, which have very
:) > different usage/access patterns than mail.
:) >
After justification (without the patch). Notice it is more difficult to read because of the appearence of the ">" characters in the text. Without the patch you can not quote properly after you justify, since it's not possible to distinguish who said what.
:) > > As NFS seems to be out, is it possible to have a large central 
:) disk > > solution > > which can be accessed by multiple IMAP
:) servers?  Or is this simply not > > worth > > doing as you say that
:) the disk usage is higher than CPU usage so such a > > central disk
:) solution would be crippled by all the concurrent accesses > > from >
:) > the servers? > > This is a controversial point, but I believe the
:) latter.  That is, I > believe > that a central disk solution is not
:) the way to distribute something as > I/O- > intensive as mail. > >
:) Of course, a central disk solution is ideal for files, which have
:) very > different usage/access patterns than mail. >
After justification (with the patch), notice that now all lines were filled correctly.
:) > > As NFS seems to be out, is it possible to have a large central disk
:) > > solution which can be accessed by multiple IMAP servers? Or is this
:) > > simply not worth doing as you say that the disk usage is higher
:) > > than CPU usage so such a central disk solution would be crippled by
:) > > all the concurrent accesses from the servers?
:) > 
:) > This is a controversial point, but I believe the latter. That is, I
:) > believe that a central disk solution is not the way to distribute
:) > something as I/O- intensive as mail.
:) > 
:) > Of course, a central disk solution is ideal for files, which have
:) > very different usage/access patterns than mail.
:) > 
Here's another example taken from comp.mail.pine. Notice that there are three different quote strings: ":)  ", ":  " and ">  ". Notice how they are all recognized correctly when justifying: Text without justification:
:) : > Do you think that I'd be able to copy these DLL files from my 98 machine
:) : > to my 95 box w/o breaking anything?  Would you happen to know what the
:) : > names are?
:)
:) : The most important DLL is SChannel.DLL, but I rather doubt that it would
:) : be as simple a matter as copying over just that one file.  Also, the
:) : appropriate DLL may be Security.DLL instead of SChannel.DLL.
:)
:) Actually, it worked :)  The Secur32.dll I got from the DCOM update for
:) Win95.  I copied the Schannel.DLL from my win98 partition.  No crash on
:) ssl PC pine now :)
After justifying with the patch (total of 74 characters wide).
:) : > Do you think that I'd be able to copy these DLL files from my 98 
:) : > machine to my 95 box w/o breaking anything? Would you happen to
:) : > know what the names are?
:)
:) : The most important DLL is SChannel.DLL, but I rather doubt that it 
:) : would be as simple a matter as copying over just that one file. Also,
:) : the appropriate DLL may be Security.DLL instead of SChannel.DLL.
:)
:) Actually, it worked :) The Secur32.dll I got from the DCOM update for
:) Win95. I copied the Schannel.DLL from my win98 partition. No crash on  
:) ssl PC pine now :)
Here's an example where you can see justification of indent strings including text. First you can see the unjustified text.
:) JW> I was wondering if there is a limit to the number of audio tracks burncd
:) JW> can accept as input.  I can safely burn 20-25 tracks, but anything above
:) JW> that gives me an error.  If this isnt an issue with burncd, how can I fix
:) JW> it?
Now justifying, we get
:) JW> I was wondering if there is a limit to the number of audio tracks 
:) JW> burncd can accept as input.  I can safely burn 20-25 tracks, but
:) JW> anything above that gives me an error.  If this isnt an issue with
:) JW> burncd, how can I fix it?
Now, you can see an example where there's some previous indentation in the paragraph. Notice that the patch will keep that indentation. First, the text to justify,
~    -i extension
~         Edit files in-place, saving backups with the specified extension.
~         If a zero-length extension is given, no backup will be saved.  It
~         is not recommended to give a zero-length extension when in-place
~         editing files, as you risk corruption or partial content in situ-
~         ations where disk space is exhausted, etc.
And now the text justified,
~    -i extension
~         Edit files in-place, saving backups with the specified 
~         extension. If a zero-length extension is given, no backup will   
~         be saved.  It is not recommended to give a zero-length extension
~         when in-place editing files, as you risk corruption or partial   
~         content in situ- ations where disk space is exhausted, etc.
Now a combination of the above examples
:) DP>    Uh, so what you're saying is that FreeBSD is tremendously insecure
:) DP>    as shipped?   Is this _really_ what you want to say about FreeBSD?
Which justified gives us
:) DP>    Uh, so what you're saying is that FreeBSD is tremendously 
:) DP>    insecure as shipped?  Is this _really_ what you want to say
:) DP>    about FreeBSD?
If you are interested in technical information about this patch (explanation of the algorithm and comments) click here. I hope you notice the difference and use the patch!.

Last Updated Mon Oct 15 23:29:03 PDT 2001