🚀 go-pugleaf

In article <INAMURA.96Dec9201615@caesar.ats.nis.nec.co.jp>,
	inamura@ats.nis.nec.co.jp (=?ISO-2022-JP?B?GyRCMHBCPBsoQiAbJEJNOhsoQiA=?= =JANE=) writes:

>$B$NJ}$O$H$b$+$/!"I|9f$9$k$HM>J,$J6uGr$,2C$o$k$+$i$H$$$&M}M3$@(B
>$B$1$G!"HsBP1~(B MUA $B$G$b1Q8lItJ,$@$1$OFI$a$k$H8@$&L@$i$+$J%a%j%C(B
>$B%H$r;}$D(B

SK>     Subject: =?ISO-2022-JP?B?GyRCRnxLXDhsGyhC?= /Japanese
SK>         (decode $B;~$K6uGr$,;D$k(B)

>$B$NJ}$^$G@5$7$/$J$$$HCG$:$k$N$O(B overkill $B$@$H;W$$$^$9$1$I!#(B

$B!HI|9f$9$k$HM>J,$J6uGr$,2C$o$k!I$H$$$&$3$H$O!"(BRFC 1342 $B$N(B 

|Use of encoded-words in message headers
$B!J>JN,!K(B
|   When
|   displaying a particular header field" (in the RFC 822 sense)
|   containing one or more encoded-words, an unencoded SPACE character
|   that immediately follows the encoded-word is not displayed.

$B$O4{$KL58z$K$J$C$F$$$k$H$$$&$3$H$G$7$g$&$+!)(B
--
$BJR;3!w#P#F#U(B