Zitat von Michael <[EMAIL PROTECTED]>:
>>> Why does IMP operate in this inconsistent manner? Is unalterable
>>> insertion of foreign whitespace into quoted text in a subset of cases
>>> truly desirable behaviour?
>
>> this has nothing to do with quoting. The indention is added by the
>> html-to-t
> RFC 2646 does have this to say about leading spaces in plain text bodies:
> "…the aesthetic consequences of unreversed space-stuffing are minimal …
> this is not expected to be a significant problem."
Of course, this view is predicated upon the fundamental introductory phrase:
"Since lines
On Wed, Jan 16, 2008 at 09:06:35AM +, [EMAIL PROTECTED] wrote:
>
> Zitat von Michael <[EMAIL PROTECTED]>:
>
> > In which email clients is this layout common? I cannot recall ever
> > seeing this elsewhere, at least not as a default. It also runs
> > contrary to traditional Usenet quoting st
>> Why does IMP operate in this inconsistent manner? Is unalterable
>> insertion of foreign whitespace into quoted text in a subset of cases
>> truly desirable behaviour?
> this has nothing to do with quoting. The indention is added by the
> html-to-text converter.
Where else is this evident in
Zitat von Michael <[EMAIL PROTECTED]>:
> Hi
>
> When an HTML message _without_ a plain text alternative part is quoted
> for reply in IMP 4.1, two extra spaces are inserted between the
> chevron and the first word of every proper paragraph ('/]*> ?/i'
> => "\n\n "). The result is an odd-looking
Hi
When an HTML message _without_ a plain text alternative part is quoted
for reply in IMP 4.1, two extra spaces are inserted between the
chevron and the first word of every proper paragraph ('/]*> ?/i'
=> "\n\n "). The result is an odd-looking first-line-only indent for
each quoted paragraph, n
