Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!news-peer.in.tum.de!fu-berlin.de!uni-berlin.de!news.dfncis.de!not-for-mail From: =?ISO-8859-15?Q?Hans-Bernhard_Br=F6ker?= Newsgroups: comp.graphics.apps.gnuplot Subject: Re: Data is not read in Date: Thu, 21 Jun 2012 00:02:59 +0200 Lines: 18 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Trace: news.dfncis.de +xrVRcXY0RtEMF+rA9O3DA/gIrOo8kvQKC80T38FXHLeg2q54BVzpofJzAZWTnpls+w0BgDvd1 Cancel-Lock: sha1:lDGMj/4VdiT4RcDyJUsFUOd2Iko= User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120604 Thunderbird/13.0 In-Reply-To: Xref: csiph.com comp.graphics.apps.gnuplot:1216 On 20.06.2012 15:09, Gudrun wrote: > Hm, you are right. I created those files under a virtual Windows XP and > used them on a MacOSX, where my Gnuplot is running? And how did they make it from one system to the other? > But since when does > Gnuplot is worried about the end of line character? It isn't. But like basically every tool in the world using text files, gnuplot relies on those text files actually looking the way text files are supposed to look, on the platform it's running on. Yes, that means files, particularly their line endings, have to be translated if you move them across platforms. That's in no way specific to gnuplot. It's also the reason why any file transfer tool worth having has an option to do the translation as part of the transfer.