Mail Archives: cygwin/2008/12/19/14:44:42
[Followups set to -talk due to apropos but not-necessarily-Cygwin-specific
devolution of the discussion]
> From: Corinna Vinschen
>
> On Dec 19 10:29, Gary R. Van Sickle wrote:
> > > From: Andrew DeFaria
> > >
> > > Mark J. Reed wrote:
> > > > On Fri, Dec 19, 2008 at 4:42 AM, Gary R. Van Sickle wrote:
> > > >> Me too, and like you and the OP report, it "just works"
> > > 99.44% of the
> > > >> time. Of course, since it's not the 21st century yet, many
> > > >> Unixoid programs are still unable to handle text files
> properly,
> > > >> hence the remaining 0.66%.
> > > > 100 - 99.44 = 0.66? You're right - it's clearly not the
> > > 21st century
> > > > yet, since you seem to be using one of the original
> > > > floating-point-bugged Pentium chips. ;-)
> > > Touche! Loved it!
> > >
> > > BTW, it's the 21st century over here. Please try to catch up...
> >
> > Another one who believes what their calendar tells them?
> Then riddle
> > me this Andrew: If this were in fact the 21st century (AKA "The
> > Future"), why would we be be discussing software which is able to
> > understand one text file format, but not a second
> ever-so-slightly different text file format?
>
> Yeah, right, if this were in fact the 21st century, why would
> we ever have to deal with a 30 year old,
> idiotic-from-the-start text file format using two line ending chars?
>
>
> Corinna
>
A-MEN sister! But how do you propose we get all these programs to
understand UTF-32 when we can't even get them to handle an extra '\r'
without starting on fire?
;-)
--
Gary R. Van Sickle
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -