comment on

Wow. True colors and all that.

I'm simply explaining you the way it is designed to work.

No, you aren't. And I know how it works anyway, thanks much.

I'll remind you that sub-thread started with your assertion that "unicrap" was going to make the "RFCs" "messy".

Which is a bunch of hooey, of course, apparently originating with a deep misunderstanding of both the nature of unicode and the appropriate use of FTP.

It is obvious that peeling away these layers of misconception has made you uncomfortable... but I'm both surprised and disappointed by your transformation into a complete raving lunatic.

-sauoq "My two cents aren't worth a dime.";

In reply to Re^22: Native newline encoding by sauoq
in thread Native newline encoding by salva

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Don't ask to ask, just ask
	PerlMonks