Ah, thanks, I'll take a look at that. I was using STON toStringPretty:
On Thu, May 26, 2016 at 8:30 PM, Sven Van Caekenberghe <s...@stfx.eu> wrote: > > > On 26 May 2016, at 20:20, Peter Uhnák <i.uh...@gmail.com> wrote: > > > > Well I was saving e.g. STON or XML file… but some apps outside didn't > particularly like it… even `cat` doesn't like CR. > > Well, STONWriter, NeoJSONWriter and NeoCSVWriter allow you to set the line > end convention, you are not alone in wanting the standard unix line end. > > > Anyway; this is not system-breaking problem, just annoying. > > > > Peter > > > > On Thu, May 26, 2016 at 2:50 PM, Sven Van Caekenberghe <s...@stfx.eu> > wrote: > > > > > On 26 May 2016, at 14:06, Peter Uhnák <i.uh...@gmail.com> wrote: > > > > > > > > > > > > On Thu, May 26, 2016 at 1:40 PM, Sven Van Caekenberghe <s...@stfx.eu> > wrote: > > > > > > > On 26 May 2016, at 13:29, Peter Uhnák <i.uh...@gmail.com> wrote: > > > > > > > > > In general I would say that you should write either something > platform specific or you write something specific > > > > > > > > Except that I cannot do that because the system doesn't support > neither. > > > > And the fact that the default line ending is CR is just bullshit… > it's 2016, not 1986. > > > > > > Yes, that CR is from days long gone ;-) > > > > > > > or #cr #lf or #crlf as needed, and/or make that last one a parameter > (OSPlatform current lineEnding). > > > > > > I am piping unknown content into the file, thus the need for > `lineEndConvention:` and the reason of this entire thread. So as I said, > the system doesn't support it. > > > I know I can use #lf or whatnot, but I am not creating the content, I > am saving it. > > > > > > Peter > > > > Well, maybe I don't understand your use case, but if you do not know > what is inside, why not save it as is, binary even, not doing any > conversions ? > > > > > > > > >
