Re: Format=flowed

2002-11-01 02:01:21
I have a couple of further thoughts about format=flowed.

1. Maxwidth

Ken Hirsch wrote:
I purposely did not use the maxwidth parameter for format=flowed because there are explicit provisions in RFC2646 for longer lines.

The maxwidth argument does not break lines without spaces, even if they exceed the maxwidth length, so those provisions wouldn't be violated. I think that maxwidth should be recognized also for fixed paragraphs in format=flowed messages:

>            if ($maxwidth) {
>                $para =~ s/^(.*)$/&break_line($1, $maxwidth)/gem;
>            }

2. Quote marks separated by space

I have noticed examples of messages whose quote marks are separated by spaces, like:

> > > asdf

instead of:

>>> asdf

even if they were generated as format=flowed. Accordingly, it may be a good idea to use the same code for counting the quote marks as is applied for the "fancyquote" option. This might not be in accordance with RFC2646, but it would lead to more nicely converted messages.

3. Controlling the body font

Personally I have concluded that the mixing of fixed and variable width fonts, which the current handling of format=flowed results in, isn't good-looking. Accordingly, I prefer a fixed font all through, and I so far I have achieved it by adding these resource settings:

    <div class="body_text_plain">


and setting the style "font-family: 'courier new', monospace". However, even if this style declaration only is intended to affect conversion of text/plain messages, it will appear in other messages as well. Whether it makes a difference in the other messages or not, it would be convenient IMO if such <div></div> elements were generated by instead.

/ Gunnar

To sign-off this list, send email to majordomo(_at_)mhonarc(_dot_)org with the

<Prev in Thread] Current Thread [Next in Thread>