On Sat, Oct 13, 2007 at 03:17:51PM +0200, Alain Bench wrote:
> On Friday, September 21, 2007 at 1:02:40 +0200, Adrian Bunk wrote:
>
> > if you e.g. use the € sign in an email (not that uncommon in the areas
> > covered by iso-8859-1) or write in French and use the character œ mutt
> > already has to send it as UTF-8 with the current default.
>
> Very right. However, this is an excellent argument for inserting
> Latin-9 into the default $send_charset, between Latin-1 and UTF-8. I'm
> not against such change: Once granted Mutt already has a moderately
> western-centric default config, why not make it better?
Latin-9 (ISO/IEC 8859-15) exists since 1997.
UTF-8 exists since 1993.
While UTF-8 is becoming the de-facto standard under many operating
systems, ISO/IEC 8859 is no longer being developed.
We are at the point in time where you have to bring good points for
_not_ simply using UTF-8.
Even more when you suggest mutt should choose between 4 different
charsets. It would be better with only us-ascii:utf-8 which would
result in only 2 charsets with one being a superset of the other one.
And more globally, using UTF-8 everywhere is the solution to all
problems that occur when mixing different charsets.
> > On Thu, Sep 20, 2007 at 04:57:11PM +0200, Alain Bench wrote:
> >> this can in no way justify breaking the $send_charset feature.
> > "breaking" is really a hard word.
>
> Sorry: I unwrite it, and instead "prevent it to work optimally".
>
>
> > Consider your locale uses charset A, you create a patch for a source
> > file in charset B, include it using "insert-file" in your editor, and
> > let your MUA send it with charset C.
>
> Patches are indeed a special case among other texts. I'd generally
> attach them via compose:<attach-file> (a), then force their outgoing
> charset to B via compose:<edit-type> (^T), and reply negatively to the
> following "Convert to B upon sending? ([yes]/no):" prompt. Result sent
> is the straight B patch under the MIME charset=B label.
>
> If I "insert-file" a short patch in my editor, it's not to apply it,
> but to discuss it. I then want it to follow the normal $charset to
> $send_charset processing, as my own text, so that composed text and
> patch are readable together.
How to send patches depends on whom to send them.
I'm mostly actice in Linux kernel development, and there the preferred
format for patches intended to be applied is inline in the email. There
doesn't exist a clear distinction between patches sent for review and
patches sent for being applied - and a quiet common case are comments
against a patch sent for being applied.
> But in fact I most frequently <attach-file> a patch.gz as
> application/x-gunzip. That's even a script that helps me doing it: Adds
> a PATCHES tag, GnuPG --clearsign --not-dash-escaped it, gzips it, and
> copies it to Mutt's directory ready to be <attach-file>d.
You better not do this on linux-kernel...
>...
> Bye! Alain.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
