<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Luis Zarrabeitia on The Carpentries</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/author/luis-zarrabeitia/</link><description>Recent content in Luis Zarrabeitia on The Carpentries</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 20 Nov 2024 10:51:28 -0500</lastBuildDate><atom:link href="https://deploy-preview-705--carpentries-website.netlify.app/blog/author/luis-zarrabeitia/index.xml" rel="self" type="application/rss+xml"/><item><title>Version Control and Newline Conventions</title><link>https://deploy-preview-705--carpentries-website.netlify.app/blog/2011/01/newline/</link><pubDate>Wed, 19 Jan 2011 00:00:00 +0000</pubDate><guid>https://deploy-preview-705--carpentries-website.netlify.app/blog/2011/01/newline/</guid><description>&lt;p>&lt;b>This post originally appeared on the &lt;a href="https://software-carpentry.org/">Software Carpentry website.&lt;/a>&lt;/b>&lt;/p>
&lt;p>There are two widely used conventions for representing the end of a line and the start of the next. Unix-like systems have traditionally used one character, \n (ASCII 10, "line feed"), while Microsoft DOS and Windows used a sequence \r\n (ASCII 13, "carriage return", \n). Being invisible, the difference of conventions usually goes unnoticed, specially because most modern software can correctly display text written with either one. However, there can be interoperability issues when using editors that follow different conventions.&lt;/p></description></item></channel></rss>