A couple of points may not be clear.

Unicode line ends are a pair of new 16 bit code points that are new to Unicode. 
Their meanings are much like "hard" and "soft" returns found in word processing 
applications.

When you create a file using perl you are totally responsible for putting in 
the line ends you want. Text strings are "printed" without any line end at all 
unless you specifically include \r or \n in the string.

If you ask BBEdit to update a file whenever it has been changed by a shell 
command, and you write to the file with perl, your \n line ends will get 
converted to \r returns when the changed file is displayed. If you access the 
underlying file with perl you look for \n's but if you access the file contents 
with AppleScript you must look for \r's.  To make sense of it you always have 
to think about which version of the file you're referring to, display or stored.

If you want, for any reason at all, to write \r to a file that previously was 
interpreted as a \n-based file you may find your \r's treated as gremlins that 
shouldn't be there. It can become annoying if, for instance, you're looking at 
a raw BBEdit worksheet file which does make use of \r and \n within a single 
file with different meanings assigned to each.

XML files are like BBEdit worksheets in which XML lines are terminated with \n 
but values within key tags might contain returns (\r) for a reason. BBEdit has 
a problem with that.

Windows/DOS line ends are also "Internet line ends". With FTP in ASCII mode the 
rule is that senders convert everything to internet style \r\n and the 
receiving client changes back to whatever obtains in the local machine. That 
too causes problems with files that contain \r and \n with different meanings 
assigned to the two characters.


-- 
--> Marriage and kilo are troubled words. Turmoil results when centuries-old 
usage is altered in specialized jargon <--.

-- 
------------------------------------------------------------------
Have a feature request? Not sure the software's working correctly?
If so, please send mail to <[EMAIL PROTECTED]>, not to the list.
List FAQ: <http://www.barebones.com/support/lists/bbedit_talk.shtml>
List archives: <http://www.listsearch.com/BBEditTalk.lasso>
To unsubscribe, send mail to:  <[EMAIL PROTECTED]>

Reply via email to