Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: unreadable jp text
- To: tlug@example.com
- Subject: Re: unreadable jp text
- From: "Frank BENNETT (=?iso-2022-jp?B?GyRCJVUlaSVzJS8hISVZJU0lQyVIGyhC?= )" <bennett@example.com>
- Date: Mon, 18 Dec 2000 14:40:40 +0900
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=iso-2022-jp
- In-Reply-To: <3A3D9FAE.9FAC4DB6@example.com>; from B0Ti on Mon, Dec 18, 2000 at 02:25:02PM +0900
- References: <3A3D9FAE.9FAC4DB6@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <iVud-.A.1eF.aNaP6@example.com>
- Resent-Sender: tlug-request@example.com
On Mon, Dec 18, 2000 at 02:25:02PM +0900, B0Ti wrote: > I can't convert this mail to human readable form: > **** cut **** > Content-Type: text/plain; charset=ISO-2022-JP > Content-Transfer-Encoding: 7bit > [...] > ^[$B#G#O#O#D^[(J ^[$B#B#Y#E^[(J > [...] > **** cut *** :-) You're too close to the forest to see the trees. Hash marks are often associated with double-width ASCII. Filter out the hash marks and what do you see? Cheers Frank Bennett
- Follow-Ups:
- Re: unreadable jp text
- From: YAMAGATA Hiroo <hiyori13@example.com>
- Re: unreadable jp text
- From: B0Ti <9915104t@example.com>
- References:
- unreadable jp text
- From: B0Ti <9915104t@example.com>
Home | Main Index | Thread Index
- Prev by Date: unreadable jp text
- Next by Date: unreadable jp text
- Prev by thread: unreadable jp text
- Next by thread: Re: unreadable jp text
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links