Re^13: Native newline encoding

I didn't know there was a single RFC in question.

That explains a lot.

You didn't bother to read the post to which you responded, or follow the links it contained; just knee-jerked a pointless response to a closing comment that had little to do with the main text of that post.

And now try to further distract with a bunch of meaningless, irrelevant statistics unrelated to anything in particular.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

The start of some sanity?

Comment on Re^13: Native newline encoding

Replies are listed 'Best First'.
Re^14: Native newline encoding by sauoq (Abbot) on May 28, 2012 at 21:36 UTC
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.";`	[reply]
Re^15: Native newline encoding by BrowserUk (Patriarch) on May 28, 2012 at 21:53 UTC
unicode is just binary. And yet; "Extensible Markup Language (XML) is a simple, very flexible text format" ... that contains [Characters: A parsed entity contains text(), a sequence of characters, which may represent markup or character data.] [Definition: A character is an atomic unit of text as specified by ISO/IEC 10646:2000 [ISO/IEC 10646]. Legal characters are tab, carriage return, line feed, and the legal characters of Unicode and ISO/IEC 10646. ()Their emphasis, not mine. And when ftping XML documents, it is normal to do so in using the ftp ascii mode so that the embedded newlines are handled correctly for cross-platform transfers. , there's no point in continuing. Truly There was no point in your starting this either, but it didn't stop you. With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday' Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. The start of some sanity?	[reply]
Re^16: Native newline encoding by sauoq (Abbot) on May 29, 2012 at 01:23 UTC
And when ftping XML documents, it is normal to do so in using the ftp ascii mode so that the embedded newlines are handled correctly for cross-platform transfers. Instead, you should transfer in binary and then just choose an editor that can handle the encoding properly for you. hth `-sauoq "My two cents aren't worth a dime.";`	[reply]
Re^17: Native newline encoding by BrowserUk (Patriarch) on May 29, 2012 at 03:55 UTC
Re^18: Native newline encoding by sauoq (Abbot) on May 29, 2012 at 11:41 UTC
Some notes below your chosen depth have not been shown here
Re^16: Native newline encoding by ikegami (Patriarch) on May 30, 2012 at 00:01 UTC
	[reply]
Re^17: Native newline encoding by BrowserUk (Patriarch) on May 30, 2012 at 00:49 UTC


P is for Practical
	PerlMonks