Hatuka*nezumi - IKEDA Soji writes:
sqwebmail-5.1.1-noflowed.patch:
o "wbnoflowed" user authentication-time option.
Old "flowed" format (RFC2646) is not suitable for some (e.g.
East-Asian) languages. So until most of MUAs implement current
"flowed" format (RFC3676) correctly, any option to disable
"flowed" format will be desired by users of such languages.
"wbnoflowed" user option controls behaviour of message composition
as:
0 - composing "flowed" format (default).
1 - composing "fixed" format.
2 - composing "fixed" format, and textarea of composition form
hard-wraps the text (recommended for non-flowed format).
What I would really like to see is a different approach.
I'd like to a new flag to unicode.h, and use that to set the textarea
wrapping automatically, based on the composition character set.
But: modern browsers that default to UTF-8 will send composed text as UTF-8,
and UTF-8 should use flowed format.
So, after thinking about it, I believe that when typing in Asian characters
you must explicitly hit enter at the end of every line, which inserts a hard
linebreak.
Now, RFC 3767 is a separate issue. I wasn't aware of this -- I'll need to
read this, when I have some free time, and see what needs to be done in
order to generate messages using RFC 3767 coding, while still being able to
display all existing RFC 2646 or RFC 3767-formatted messages.
8 messages in net.sourceforge.lists.courier-sqwebmailRe: [sqwebmail] patches: No flowed fo...
.patch, .patch
