Date: Thu, 11 Apr 2002 18:13:47 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: Christian Weisgerber <naddy@mips.inka.de> Cc: freebsd-chat@freebsd.org Subject: Re: what are these characters please? Message-ID: <3CB634CB.6F306CF3@mindspring.com> References: <3CB571D6.2C10B9AA@mindspring.com> <20020411113858.E48BB3F30@bast.unixathome.org> <a9492h$2g43$1@kemoauc.mips.inka.de> <3CB5F49B.C21B24E9@mindspring.com> <a95031$2rd8$2@kemoauc.mips.inka.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Christian Weisgerber wrote: > Terry Lambert <tlambert2@mindspring.com> wrote: > > In this particular case, the advice about non-printable ASCII > > characters doesn't work, > > Yes, it does. > > > either, since it will only swallow the <ESC>, and not the rest > > of the sequence or the terminator. > > Which is perfectly within the goal of turning the input stream into > a validly encoded sequence. That we are left with a handful of > garbage characters instead of a single one is of no concern. If you were intent on doing that, you'd convert it to an "a" with a diaresis over it, since that's also a "validly encoded sequence". Let's also be perfectly clear here: you are redefining validity to suit a particular output processing tool. This adds constraints at the wrong place: if you are going to have such constraints, make them on the commit message processing script, to reject commit messages that don't fit within the arbitrary limitations imposed by the relatively poor tools you are using. -- Terry 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?3CB634CB.6F306CF3>