[pkgsrc/trunk]: pkgsrc/mail/fix-mime-charset Initial import of fix-mime-chars...

[wiz <wiz%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/1e69f159cd3a
branches:  trunk
changeset: 462082:1e69f159cd3a
user:      wiz <wiz%pkgsrc.org@localhost>
date:      Fri Sep 26 10:21:51 2003 +0000

description:
Initial import of fix-mime-charset-0.4.0:

In non-English mailing lists (particularly in Russian) there is a
big problem with messages, where charset parameter of Content-Type
header is set incorrectly. Sometimes software is buggy, sometimes
people cannot set up their software properly, sometimes web-based
email clients do not implement charsets.  While reading such a
mail, one should manually switch encoding in MUA back and forth.
Incorrectly encoded or plain 8-bit Subject field is another big
problem.  Such fields often get corrupted while passing e-mail
gateways.

This program can be used to solve this problem while used as mail
filter (in MTA, procmail, or a similar program).

diffstat:

 mail/fix-mime-charset/DESCR    |  12 ++++++++++++
 mail/fix-mime-charset/Makefile |  16 ++++++++++++++++
 mail/fix-mime-charset/PLIST    |   3 +++
 mail/fix-mime-charset/distinfo |   4 ++++
 4 files changed, 35 insertions(+), 0 deletions(-)

diffs (51 lines):

diff -r 486354274312 -r 1e69f159cd3a mail/fix-mime-charset/DESCR
--- /dev/null   Thu Jan 01 00:00:00 1970 +0000
+++ b/mail/fix-mime-charset/DESCR       Fri Sep 26 10:21:51 2003 +0000
@@ -0,0 +1,12 @@
+In non-English mailing lists (particularly in Russian) there is a
+big problem with messages, where charset parameter of Content-Type
+header is set incorrectly. Sometimes software is buggy, sometimes
+people cannot set up their software properly, sometimes web-based
+email clients do not implement charsets.  While reading such a
+mail, one should manually switch encoding in MUA back and forth.
+Incorrectly encoded or plain 8-bit Subject field is another big
+problem.  Such fields often get corrupted while passing e-mail
+gateways.
+
+This program can be used to solve this problem while used as mail
+filter (in MTA, procmail, or a similar program).
diff -r 486354274312 -r 1e69f159cd3a mail/fix-mime-charset/Makefile
--- /dev/null   Thu Jan 01 00:00:00 1970 +0000
+++ b/mail/fix-mime-charset/Makefile    Fri Sep 26 10:21:51 2003 +0000
@@ -0,0 +1,16 @@
+# $NetBSD: Makefile,v 1.1.1.1 2003/09/26 10:21:51 wiz Exp $
+#
+
+DISTNAME=              fix-mime-charset-0.4.0
+CATEGORIES=            mail converters
+MASTER_SITES=          ${MASTER_SITE_SOURCEFORGE:=fix-mime-chr/}
+
+MAINTAINER=            wiz%NetBSD.org@localhost
+HOMEPAGE=              http://fix-mime-chr.sourceforge.net/
+COMMENT=               Correct MIME charset type in mail headers
+
+USE_BUILDLINK2=                yes
+USE_PKGLOCALEDIR=      yes
+GNU_CONFIGURE=         yes
+
+.include "../../mk/bsd.pkg.mk"
diff -r 486354274312 -r 1e69f159cd3a mail/fix-mime-charset/PLIST
--- /dev/null   Thu Jan 01 00:00:00 1970 +0000
+++ b/mail/fix-mime-charset/PLIST       Fri Sep 26 10:21:51 2003 +0000
@@ -0,0 +1,3 @@
+@comment $NetBSD: PLIST,v 1.1.1.1 2003/09/26 10:21:51 wiz Exp $
+bin/fix-mime-charset
+man/man1/fix-mime-charset.1
diff -r 486354274312 -r 1e69f159cd3a mail/fix-mime-charset/distinfo
--- /dev/null   Thu Jan 01 00:00:00 1970 +0000
+++ b/mail/fix-mime-charset/distinfo    Fri Sep 26 10:21:51 2003 +0000
@@ -0,0 +1,4 @@
+$NetBSD: distinfo,v 1.1.1.1 2003/09/26 10:21:51 wiz Exp $
+
+SHA1 (fix-mime-charset-0.4.0.tar.gz) = b64dee1f20d915fcb53e848c9111646e5fbd0a04
+Size (fix-mime-charset-0.4.0.tar.gz) = 88018 bytes