Date: Thu, 11 Apr 2002 06:19:29 -0400 From: "Dan Langille" <dan@langille.org> To: Terry Lambert <tlambert2@mindspring.com> Cc: chat@freebsd.org Subject: Re: what are these characters please? Message-ID: <20020411102024.3E6283F30@bast.unixathome.org> In-Reply-To: <3CB4FBFB.9D2AC7E0@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10 Apr 2002 at 19:59, Terry Lambert wrote:
> Dan Langille wrote:
> > I found these characters in a recent cvs-all commit:
> >
> > 20 20 20 20 20 5b 53 75 62 6d 69 74 74 65 64 20 | [Submitted | 62
> > 79 3a 20 56 69 6c 6c 65 20 53 6b 79 74 74 1b |by: Ville Skytt.| 2c 41
> > 64 1b 28 42 20 3c 76 69 6c 6c 65 2e 73 6b |,Ad.(B <ville.sk| 79 74 74
> > 61 40 69 6b 69 2e 66 69 3e 5d 0a 20 20 |ytta@iki.fi>]. |
> >
> > When viewed under vi, I get:
> >
> > Ville Skytt^[,Ad^[(B <ville.skytta@iki.fi>
>
> ANSI character set selector escape sequence for 7 bit representation
> of 8 bit characters.
>
> If I had to guess, I would say "eth", which is a "D" with a bar in it,
> unlike "thorn", which is an "O" with a forwars slash through it. 8-).
>
> Obviously a deficiency in the encapsulation of a cut-and-paste
> that was not attributed by encoding, because CVS commit logs are
> not MIME encapsulated.
Given that I'm trying to process the cvs-all messages into XML documents
(using the perl module XML::Writer which does not do any encoding beyond
characters such as >, <, etc), any suggestions as to how to deal with such
characters? I've been looking through cpan but I suspect I'm using the
wrong search criteria ("encoding"). Any clues?
--
Dan Langille
The FreeBSD Diary - http://freebsddiary.org/ - practical examples
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-chat" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020411102024.3E6283F30>