[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nmh-workers] UTF-8 message bodies

From: Ken Hornstein
Subject: Re: [Nmh-workers] UTF-8 message bodies
Date: Thu, 31 May 2012 00:01:55 -0400

>I've been thinking a bit of this and I can see (as a user not
>programmer) a couple of possibilities. 
>It is possible to keep almost unchanged state with addition of
>one more clause to mhbuild like pair #off #on which marks the
>region where ^# is not interpreted as directive.

Yeah, to me that's just simply making the problem only slightly better.

Here's what I'm thinking:

- As you have pointed out, it's kinda lame that nowadays we don't include
  MIME headers; sure, they're not required but it would be good to include
  them today anyway.
- We already have a tool to generate the right headers: mhbuild.  So why
  aren't we using it always?  Well, some people do.  My question to everyone
  who uses automimeproc: 1 is: are you doing this for character set issues,
  or do you really use mhbuild directives that much?  Or a combination
  of both?
- If we assume both of the above statements are true, then it seems logical
  that we should always be running mhbuild.  But to me it seems dumb that
  # characters can't be in the beginning of a line, and having people have
  to know about #on/#off directives just seems like the wrong solution.
  So that's why I'm proposing that the automatic run of mhbuild doesn't
  process those directives at all.  But if you run "mime" at a WhatNow?
  prompt then presumably you're smart enough to know you have to escape
  any leading # characters.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]