Le 23/11/2012 08:41, Jo Even Skarstein a écrit :
Just noticed this today when I opened this file with Notepad on a Windows computer. This file should absolute have DOS/TOS line-endings so it can be displayed by ordinary file viewers. E.g. if you try to debug a problem by booting into TOS and displaying this file it will only show a single column of letters on the far right side of the screen.
Generated text files should use the line ending specified by the UNIXMODE environment variable (and I hope it is CR/LF by default, for TOS compatibility).
But indeed the scenario you describe is problematic. Maybe xa_boot.log could be an exception to the rule, always written in CR/LF format. That's a pragmatic solution.
Personally, I would prefer to configure CR/LF line endings in UNIXMODE on Atari machines, for TOS compatibility. But I don't do that because I fear additional bugs, so I use UNIX LF mode like everyone. Also, some UNIX tools does not handle the CR/LF files correctly (starting by the "cat" command, by design).
Btw. I also noticed that a lot of the docs has unix line-endings. I think that textfiles that are supposed to be read on a TOS computer should be in TOS/DOS format.
I fully agree with that.Another example is the EmuTOS project. Everything is stored in CVS using UNIX LF format, because we use a UNIX-like toolchain to produce the binaries.
However, for the binary distributions (recent releases), all documentation files are converted to CR/LF with dos2unix. This is not strictly correct, because the EmuTOS binary distributions are multi-platform. But CR/LF files can be easily read everywhere, so that's a good choice.
-- Vincent Rivière