Debian Bug report logs - #86817
debconf sends mail in EUC-JP encoding

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Fumitoshi UKAI <ukai@debian.or.jp>

To: submit@bugs.debian.org

Subject: debconf sends mail in EUC-JP encoding

Date: Wed, 21 Feb 2001 13:47:04 +0900

Package: debconf
Version: 0.5.34
Severity: wishlist

debconf supports descripion in templates for several languages.
For Japanese, it uses EUC-JP encoding, because it is well supported
in libc and several application than other encoding such as Shift-JIS
and ISO-2022-JP.  So, debconf will send it directly via mail for 
"note" type.  However, we don't use EUC-JP encoding in mail, but
we use ISO-2022-JP encoding.  All mail user agent for Japanese
support ISO-2022-JP encoding, but few of them supports EUC-JP.
(There is some historial reason. EUC-JP needs 8bit through, but
 ISO-2022-JP is 7bit encoding, so in old Internet ISO-2022-JP is
 more suitable than EUC-JP.)

I think it is good that debconf has some locale aware hooks to send mail.

Thanks,
Fumitoshi UKAI

Message #10 received at 86817@bugs.debian.org (full text, mbox, reply):

From: Joey Hess <joeyh@debian.org>

To: Fumitoshi UKAI <ukai@debian.or.jp>, 86817@bugs.debian.org

Subject: Re: Bug#86817: debconf sends mail in EUC-JP encoding

Date: Tue, 20 Feb 2001 20:49:16 -0800

Fumitoshi UKAI wrote:
> debconf supports descripion in templates for several languages.
> For Japanese, it uses EUC-JP encoding, because it is well supported
> in libc and several application than other encoding such as Shift-JIS
> and ISO-2022-JP.  So, debconf will send it directly via mail for 
> "note" type.  However, we don't use EUC-JP encoding in mail, but
> we use ISO-2022-JP encoding.  All mail user agent for Japanese
> support ISO-2022-JP encoding, but few of them supports EUC-JP.
> (There is some historial reason. EUC-JP needs 8bit through, but
>  ISO-2022-JP is 7bit encoding, so in old Internet ISO-2022-JP is
>  more suitable than EUC-JP.)
> 
> I think it is good that debconf has some locale aware hooks to send mail.

If you want it done send me a patch; I don't know anything about this
stuff.

-- 
see shy jo

Message #17 received at 86817@bugs.debian.org (full text, mbox, reply):

From: Michal Čihař <michal@cihar.com>

To: Debian Bug Tracking System <86817@bugs.debian.org>

Subject: wrong charset in emails sent by debconf

Date: Fri, 18 Jun 2004 21:22:09 +0200

Package: debconf
Version: 1.4.28
Severity: normal
Followup-For: Bug #86817


Email hadersa should contain charset information, otherwise non-ASCII
messages can not be displayed correctly in MUA.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.7
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8

Versions of packages debconf depends on:
ii  debconf-i18n                  1.4.28     full internationalization support 
ii  perl-base                     5.8.4-2    The Pathologically Eclectic Rubbis

-- debconf information excluded

Message #22 received at 86817@bugs.debian.org (full text, mbox, reply):

From: Alexis Sukrieh <sukria@sukria.net>

To: 86817@bugs.debian.org

Subject: [Bugfix submission]

Date: Fri, 1 Oct 2004 13:49:09 +0200

[Message part 1 (text/plain, inline)]

Here is a ja.po file converted from EUC-JP to ISO-2022-JP enconding.

I've converted the file with iconv so it souhld be ok but as I am not a
*real* Japanese user, I cannot test it though de japanese chars seems to 
appear correctly in my terminal.

-- 
Alexis Sukrieh <sukria@sukria.net>
 * Another Linux Debian Geek Enthusiast
 * http://www.sukria.net
   

[ja.po (text/plain, attachment)]

Message #27 received at 86817@bugs.debian.org (full text, mbox, reply):

From: Alexis Sukrieh <sukria@sukria.net>

To: 86817@bugs.debian.org

Subject: Cancel my previous patch...

Date: Fri, 1 Oct 2004 16:19:32 +0200

Well, sorry to send 2 mails for one thing :

Charset ISO-2022-JP does not seem to be supported, when compiling the
package, at po files time, the following occurs :

$ fakeroot dpkg-buildpackage -us -uc
[...]
msgfmt -o gl.mo gl.po
Merging debconf.pot and ja-ISO-2022-JP.poja-ISO-2022-JP.po:23:31: parse
error
ja-ISO-2022-JP.po:23: keyword "G" unknown
ja-ISO-2022-JP.po:24:12: invalid control sequence
ja-ISO-2022-JP.po:35:51: parse error
ja-ISO-2022-JP.po:35: keyword "B1" unknown
ja-ISO-2022-JP.po:35: keyword "$B$D0J" unknown
ja-ISO-2022-JP.po:35: keyword "e$N" unknown
ja-ISO-2022-JP.po:35: keyword "F" unknown
ja-ISO-2022-JP.po:35: keyword "H" unknown
ja-ISO-2022-JP.po:35: keyword "U" unknown
[...]

Otherwise, even if we could have the proper po file for this enconding,
how could we switch - only for Japanses locales - to an alternative
locale when sending mail ? 

That sounds pretty weird to do doesn't it ? :-/

-- 
Alexis Sukrieh <sukria@sukria.net>
 * Another Linux Debian Geek Enthusiast
 * http://www.sukria.net
   

Message #32 received at 86817@bugs.debian.org (full text, mbox, reply):

From: barbier@linuxfr.org (Denis Barbier)

To: Alexis Sukrieh <sukria@sukria.net>, 86817@bugs.debian.org

Subject: Re: Bug#86817: Cancel my previous patch...

Date: Fri, 1 Oct 2004 21:28:59 +0200

On Fri, Oct 01, 2004 at 04:19:32PM +0200, Alexis Sukrieh wrote:
> Well, sorry to send 2 mails for one thing :
> 
> Charset ISO-2022-JP does not seem to be supported, when compiling the
> package, at po files time, the following occurs :
> 
> $ fakeroot dpkg-buildpackage -us -uc
> [...]
> msgfmt -o gl.mo gl.po
> Merging debconf.pot and ja-ISO-2022-JP.poja-ISO-2022-JP.po:23:31: parse
> error
> ja-ISO-2022-JP.po:23: keyword "G" unknown
> ja-ISO-2022-JP.po:24:12: invalid control sequence
> ja-ISO-2022-JP.po:35:51: parse error
> ja-ISO-2022-JP.po:35: keyword "B1" unknown
> ja-ISO-2022-JP.po:35: keyword "$B$D0J" unknown
> ja-ISO-2022-JP.po:35: keyword "e$N" unknown
> ja-ISO-2022-JP.po:35: keyword "F" unknown
> ja-ISO-2022-JP.po:35: keyword "H" unknown
> ja-ISO-2022-JP.po:35: keyword "U" unknown
> [...]
> 
> Otherwise, even if we could have the proper po file for this enconding,
> how could we switch - only for Japanses locales - to an alternative
> locale when sending mail ? 
> 
> That sounds pretty weird to do doesn't it ? :-/

You should not modify ja.po, but the code which sends mails.
It seems that /usr/share/perl5/Debconf/Element/Noninteractive/Note.pm
is concerned.

Denis

Message #37 received at 86817@bugs.debian.org (full text, mbox, reply):

From: Joey Hess <joey@kitenet.net>

To: Alexis Sukrieh <sukria@sukria.net>

Cc: 223039@bugs.debian.org, 260189@bugs.debian.org, 98611@bugs.debian.org, 67097@bugs.debian.org, 86817@bugs.debian.org

Subject: Re: debconf bugs

Date: Fri, 1 Oct 2004 15:52:06 -0400

[Message part 1 (text/plain, inline)]

Alexis Sukrieh wrote:
> I've been using Debian for 4 years now and really want to contribute.
> 
> I give sometimes a look at the orphaned Debian packages list for some stuff to
> look at.
> 
> And then I saw that you requested some help on debconf...
> 
> Well, it's a big piece of cake to start with ! But I'm pretty interested
> in trying to help you...

I appreciate your help. At the moment a team is slowly forming around
debconf, if you're able to keep sending patches and fixing bugs, I'd not
be suprised if you ended up on the team with commit access to the
subversion repository and so on. This is a good start.

> So to start with, I'll take some of the bugs you listed and which I
> think I can solve :
> 
> #223039 (what to do ?)
> 	Well, a philosophical bug it seems. I read the whole thread.
> 	What should we do here ? change the path to /var/lib or just
> 	close the bug whithout doing anything ?

I'm inclined to close it via improved documentation, that perhaps
explains the result of deleting the cache and notes how to move it to a
different directory if the admin desires.

> #260189 (patched)
> 	Here is a patch to avoid some annoying warnings during Perl 
> 	runtime. I've only patched Debconf/Format/822.pm because the 
> 	other reported warning, in the file Debconf/DbDriver/Stack.pm 
> 	is no longer pertinent according to the current version of 
> 	debconf.
> 	See attachment : patch-260189.diff for the patch.

I've thought about doing this, but since I don't understand why the
database corruption problem happens, I'd rather leave the warnings in,
in the hope that I can someday get enough data to explain it. Hiding the
problem won't fix it.

> #98611 (to be closed ?)
> 	According to your last comment, this bug should be closed :
> 	"No shell does that and the debconf text frontend won't either."

Nope, since it turns out he is using the dialog frontend, my comment
does not apply. It's a real bug, but it probably is best fixed in
whiptail, although one fix might be to make debconf clear the screen
after the user selects something in whiptail.

> #67097 (patched)
> 	I've fixed this bug but am not sure if this is the good way.
> 	I just use a "print" to list the packages but tried to use 
> 	$frontend->add($frontend->makeelement($pkg)) instead without 
> 	getting it working... Could you tell me if this is the good 
> 	way or not ?
> 	See attachment : patch-67097.diff for the patch.

Using the frontend is certianly not necessary. I think your patch is
pretty good, although I have not looked at it in detail. The reason I
have not implemented this before is that there was hope of merging the
configure-debian package into debconf, and that package provides ways to
get a list of packages to reconfigure. But with a patch, may as well fix
the bug that way..

> #86817 (patched)
> 	I've converted po/ja.po to the proper encoding : ISO-2022-JP 
> 	with iconv and have update the mail header :
> 	"Content-Type: text/plain; charset=ISO-2022-JP\n"
> 	This should be enough for this bug :)
> 	See attachment : ja.po (diff is not pertinent here so I give
> 	you the file).

I would not dare to apply this unless a Japanese speaker has verified
that it works and displays ok. Character set conversion can be buggy
from/to Japanese, I understand.

-- 
see shy jo

[signature.asc (application/pgp-signature, inline)]

Message #42 received at 86817@bugs.debian.org (full text, mbox, reply):

From: "USPS International" <rafael.boone@femdompics.de>

To: 86817@bugs.debian.org

Subject: Notification status of your delivery (USPS 08244550)

Date: Thu, 26 Jan 2017 08:02:41 +0100

[Message part 1 (text/plain, inline)]

Dear Customer,

USPS courier was unable to contact you for your parcel delivery.

Postal label is enclosed to this e-mail. Please check the attachment!

Yours sincerely,
Rafael Boone,
USPS Senior Station Manager.

[Delivery-Receipt-08244550.zip (application/zip, attachment)]

Send a report that this bug log contains spam.