Re: CGI and UTF

2003-01-05 Thread Jarkko Hietaniemi
On Sun, Jan 05, 2003 at 12:16:38PM -0600, Earl Hood wrote: > > > This is Bad Juju (tm). It _guarantees_ script breakage (potentially > > > silently!) for Unix people doing _anything_ but ASCII text manipulation. > > > > I repeat: I don't think you can do "more than ASCII" by hanging tooth > > an

Re: CGI and UTF

2003-01-05 Thread Earl Hood
On January 5, 2003 at 05:42, Jarkko Hietaniemi wrote: > > This is Bad Juju (tm). It _guarantees_ script breakage (potentially > > silently!) for Unix people doing _anything_ but ASCII text manipulation. > > I repeat: I don't think you can do "more than ASCII" by hanging tooth > and nail to the

Re: CGI and UTF

2003-01-05 Thread Jarkko Hietaniemi
> > or implicitly (locale) command them not be. > > Not fine without a warning. This is 'action at a distance' (this is the > same reason un'local'ized usage of the 'special' variables is nearly On that we can agree, kind of-- I find the *whole* locale system to be a Bad Idea (tm) (not just any U

Re: CGI and UTF

2003-01-05 Thread Benjamin Franz
On Sun, 5 Jan 2003, Jarkko Hietaniemi wrote: > I repeat: all your filehandles are still 'binary' unless you either > explicitly (binmode) Fine. > or implicitly (locale) command them not be. Not fine without a warning. This is 'action at a distance' (this is the same reason un'local'ized usage of