Re: Setting correct double-nested quotes (was: Changing the Mime type of the outgoing message by default?)
* On [010511 22:45] Thomas Roessler [EMAIL PROTECTED] wrote: On 2001-05-11 15:56:33 -0400, adam morley wrote: I've just been told that is non-standard though. which means we are distributing a software package that is non-standard. is that bad? Is not _what_ standard? If we don't say this is format=flowed, we also don't have to emit format=flowed. This non-standard refers to quoting levels, in conjunction with format=flowed text, how to consider quoted text, and what defines the quote depth, as far as I can make out. The relevant RFC is; RFC 2646 section 4.5. Though, from what I can make out from it, it doesn't apply when the text format is not format=flowed.(?) Lawrence -- Lawrence Mitchell | http://members.tripod.co.uk/EVSvienna/ [EMAIL PROTECTED]
Re: Setting correct double-nested quotes (was: Changing the Mime type of the outgoing message by default?)
On Sat, May 12, 2001 at 02:36:07PM +0200, Lawrence Mitchell wrote: * On [010511 22:45] Thomas Roessler [EMAIL PROTECTED] wrote: On 2001-05-11 15:56:33 -0400, adam morley wrote: I've just been told that is non-standard though. which means we are distributing a software package that is non-standard. is that bad? Is not _what_ standard? If we don't say this is format=flowed, we also don't have to emit format=flowed. This non-standard refers to quoting levels, in conjunction with format=flowed text, how to consider quoted text, and what defines the quote depth, as far as I can make out. The relevant RFC is; RFC 2646 section 4.5. Though, from what I can make out from it, it doesn't apply when the text format is not format=flowed.(?) non-format flowed text is definately a gray area, and open to a little interpretation based on what is seen in multiple rfcs. i see what you are saying, and i understand what thomas was saying. Lawrence -- Lawrence Mitchell | http://members.tripod.co.uk/EVSvienna/ [EMAIL PROTECTED] -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Setting correct double-nested quotes (was: Changing the Mime type of the outgoing message by default?)
On Fri, May 11, 2001 at 06:49:19PM +0200, Lawrence Mitchell wrote: * On [010511 18:02] adam morley [EMAIL PROTECTED] wrote: Your nested quoting was also done incorrectly. According to section 4.5 of RFC 2646 there should be no space between the '' marks at the start of quoted lines. that, my friend was mutts doing, not mine. so if someone could explain why/how to change that, then thanks! Using vim as an editor, I came up with this: change double-quoted text to RFC 2646 format autocmd BufNewFile,BufRead .followup,.letter,mutt*,nn.*,snd.* :%s/^\(.*\)/\1/ The command on one line of course, hope that helps ah, if mutts not putting in the right, then MUTT is what is non-compliant, correct? i shouldn't have to make a vim macro to fix mutt's non-compliance? lawrence -- Lawrence Mitchell | http://members.tripod.co.uk/EVSvienna/ [EMAIL PROTECTED] | He says gods like to see an atheist around. Gives them something to aim at. -- (Terry Pratchett, Small Gods) -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Setting correct double-nested quotes (was: Changing the Mime type of the outgoing message by default?)
On 2001-05-11 13:21:40 -0400, adam morley wrote: ah, if mutts not putting in the right, then MUTT is what is non-compliant, correct? i shouldn't have to make a vim macro to fix mutt's non-compliance? It's configurable, and the mutt version you are using doesn't even claim that it's producing text/plain; format=flowed. -- Thomas Roessler http://log.does-not-exist.org/
Re: Setting correct double-nested quotes (was: Changing the Mime type of the outgoing message by default?)
On Fri, May 11, 2001 at 07:45:46PM +0200, Thomas Roessler wrote: On 2001-05-11 13:21:40 -0400, adam morley wrote: ah, if mutts not putting in the right, then MUTT is what is non-compliant, correct? i shouldn't have to make a vim macro to fix mutt's non-compliance? It's configurable, and the mutt version you are using doesn't even claim that it's producing text/plain; format=flowed. so how do i make mutt set the quote thing correctly? and im not setting format=flowed right now. mainly because nobody's told me how to automate it save editing the source. -- Thomas Roessler http://log.does-not-exist.org/ -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Setting correct double-nested quotes (was: Changing the Mime type of the outgoing message by default?)
On Fri, May 11, 2001 at 01:37:16PM -0500, Paul Cox wrote: On Friday, May 11, 2001, adam morley wrote: ah, if mutts not putting in the right, then MUTT is what is non-compliant, correct? i shouldn't have to make a vim macro to fix mutt's non-compliance? indent_string Type: string Default: Specifies the string to prepend to each line of text quoted in a message to which you are replying. You are strongly encouraged not to change this value, as it tends to agitate the more fanatical netizens. I've just been told that is non-standard though. which means we are distributing a software package that is non-standard. is that bad? -- [EMAIL PROTECTED], ICQ#: 25370820, OpenPGP key at www.keyserver.net 1024D/39F0BBF4 2024 B7CB 10BF 6BE7 2ECE E0FD 1360 0181 39F0 BBF4 Current Linux uptime: 5 days 22 hours 55 minutes. -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Setting correct double-nested quotes (was: Changing the Mime type of the outgoing message by default?)
On 2001-05-11 15:56:33 -0400, adam morley wrote: I've just been told that is non-standard though. which means we are distributing a software package that is non-standard. is that bad? Is not _what_ standard? If we don't say this is format=flowed, we also don't have to emit format=flowed. (Also, as I said, the CVS has an option to do nice and correct format=flowed when used together with the right kind of editor.) -- Thomas Roessler http://log.does-not-exist.org/
