Am 2008-10-10 10:08:47, schrieb Kyle Wheeler:
On Friday, October 10 at 10:05 AM, quoth Jörg Sommer:
attach_charset
Type: string
Default:
I've set this variable to us-ascii:utf-8, but Mutt still uses
iso-8859-1.
Huh... That's weird. It shouldn't do that.
Am 2008-10-09 11:54:22, schrieb Kyle Wheeler:
The easiest way is to compress them first.
Right, but on all Devel-Liste I am, sending of compressed po/pot files
or diffs are stronly discouraged because you can not read it inline
without head standing...
In mutt it works fine but not other
Hi Kyle,
Kyle Wheeler [EMAIL PROTECTED] wrote:
On Thursday, October 9 at 02:27 PM, quoth Jörg Sommer:
when sending LaTeX files or translations of program strings mutt
recodes them and breaks them. How can I prevent mutt sends the
attachment with a different encoding as the local? In the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, October 10 at 10:05 AM, quoth Jörg Sommer:
attach_charset
Type: string
Default:
I've set this variable to us-ascii:utf-8, but Mutt still uses
iso-8859-1.
Huh... That's weird. It shouldn't do that.
Does
Hi,
when sending LaTeX files or translations of program strings mutt recodes
them and breaks them. How can I prevent mutt sends the attachment with a
different encoding as the local? In the LaTeX file I define the encoding
of the file as option of the package inputenc. If I say utf8 there, mutt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, October 9 at 02:27 PM, quoth Jörg Sommer:
when sending LaTeX files or translations of program strings mutt
recodes them and breaks them. How can I prevent mutt sends the
attachment with a different encoding as the local? In the
