[mew-int 00668] Re: encoding problems with Addrbook
Kazu Yamamoto ( 山本和彦 )
kazu at example.com
Wed Dec 26 15:04:59 JST 2001
Werner,
I considered your problems again.
From: Werner LEMBERG <wl at example.com>
Subject: [mew-int 00656] encoding problems with Addrbook
> It seems to me that the encoding of Addrbook should be fixed somehow
> (by adding a proper -*- coding: ... -*- line, for example). It just
> happened to me that I had a Japanese entry in iso-2022-7bit and later
> on a Korean one in euc-kr, making the Korean entry unreadable because
> autodetect selected iso-2022-7bit for AddrBook.
You are right. The best way to fix this problem is insert
#-*-coding:ctext;-*-
in Mail/Addrbook.
I won't modify Mew to automatically insert this to
Mail/Addrbook. Rather, I will add this explanation to info.
From: Werner LEMBERG <wl at example.com>
Subject: [mew-int 00657] permissions of Addrbook
> It seems to me that the permissions of Addrbook are 644. Shouldn't
> this be 600 for obvious reasons? If someone has changed the
> permission of files in the Mail directory (maybe I did that, but I no
> longer can remember why), it might be a good idea to ask the user
> whether he or she wants to fix that. Maybe the permissions of the
> directories should be controlled also.
Mew creates the Mail directory with 600. So, privacy is protected by
default (unless you are using NFS). Also, Mail/Addrbook can include
other files. Since it is hard to detect all inserted files and set
their file modes, I won't modify Mew in this area.
--Kazu
More information about the Mew-int
mailing list