Thanks John.
Will test today. I'm fairly confident this is the issue:
- on the other PC, I was using Notepad++, a programing editor.
- on the new PC, I was using regular windows notepad until last night.
I tried Notepad++ on the new PC last night, to make sure I was seeing the real characters...and discovered very nice features in Notepad++:
1) file opens and displays as expected, correctly and straight away. That's why I didn't notice the problem earlier
2) Status bar says my file is actually encoded in UNIX ANSI (but opened in Windows ANSI ;-)
3) Slick editor feature to convert EOL to Windows ANSI
Looking up the issue in Google, it seems its a common issue in Java programing on Windows systems. You may need to test under which OS the stats101 is running to OUTPUT correctly on each OS.
PS: interesting observations:
- WRITE doesn't have "visible" problem, files open correctly in windows notepad. I did not check if Notepad++ sees them as UNIX ANSI?
- Stats101 reads back it's own UNIX ANSI files correctly (OUTPUT followed by READ), which means you may need to check the code there as well, as fixing OUTPUT might break READ.
Thanks and best regards
Gus