in reply to Re^13: Native newline encoding
in thread Native newline encoding
I see. Well, in my defense, it was easy to read:
Things (will) get far more messy once the RFCs start dealing with Unicrap.
And think that by using the plural "RFCs" you were talking about more than one... like all of them in general. Or, at the least, all of them related to FTP.
Of course, it's unlikely that the FTP RFCs will be greatly affected by "unicrap" because unicode is just binary.
If you still don't see where I was coming from, there's no point in continuing. Truly.
-sauoq
"My two cents aren't worth a dime.";
"My two cents aren't worth a dime.";
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^15: Native newline encoding
by BrowserUk (Patriarch) on May 28, 2012 at 21:53 UTC | |
by sauoq (Abbot) on May 29, 2012 at 01:23 UTC | |
by BrowserUk (Patriarch) on May 29, 2012 at 03:55 UTC | |
by sauoq (Abbot) on May 29, 2012 at 11:41 UTC | |
by BrowserUk (Patriarch) on May 29, 2012 at 13:03 UTC | |
| |
by ikegami (Patriarch) on May 30, 2012 at 00:01 UTC | |
by BrowserUk (Patriarch) on May 30, 2012 at 00:49 UTC |
In Section
Seekers of Perl Wisdom