You mean, from a unix machine to a dos/windows machine -- that's the direction in which this sort of symptom appears, because the dos machine needs both the CR and the LF to display the text properly, and will display text in a manner just like to OP showed if the CR is missing. Meanwhile, unix uses only the LF in its text files, but will usually display a dos file (with the "extra" CR next to each LF) intelligibly.
The example in the OP was caused either by this issue, or else it results from trying to do something like an X-windows "select/paste" operation from an html browser window to some plain-text window, where the selected lines in the browser happen to be part of a <table>. No way to be sure, given the information originally provided, but the html-paste seems more likely, and removing whitespace is the way to go (rather than adding CR's).
In reply to Re: Re: Text File Parsing.
by graff
in thread Text File Parsing.
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |