|
Post by Chris Iverson on Mar 17, 2019 19:55:44 GMT -5
I get similar results viewing the file as ansi. THAT would be because of a previously reported bug. libertybasiccom.proboards.com/thread/501/lb5-writing-file-weird-newlineNewlines aren't getting created properly on Windows, it only outputs the LINE FEED character(13, 0x0D). Most Windows programs expect newlines to be a combination of the CARRIAGE RETURN and LINE FEED characters(CRLF, 10 and 13, 0x0A and 0x0D), whereas most Unix-based OSes use just LF. If you look closely at your screenshot, you'll see that all the characters get displayed properly, same as my screenshot. Some glyphs are slightly different due to the font, and there might be some differences in exact characters due to locale differences, changing the ANSI codepoint. It IS displaying correctly, though. The reason my screenshot looks completely correct is because I'm running on a Windows Insider build, using a beta version of the next feature upgrade for Windows 10. Among other things, they've updated Notepad(and presumably some of Windows' built-in textbox functions) to properly handle Unix-style line endings.
|
|
cundo
Full Member
Muchas Gracias!!
Posts: 146
|
Post by cundo on Mar 18, 2019 9:06:07 GMT -5
You are completely right Chris, I noticed that the displaying characters were Ok, didn't know about the LF CRLF and Win10 problems.
|
|
|
Post by tsh73 on Mar 18, 2019 12:07:04 GMT -5
Cundo, so how Spanish version go? Does it write full scale of chars (0-255) or breaks on chr$(128) like Russian version?
|
|
cundo
Full Member
Muchas Gracias!!
Posts: 146
|
Post by cundo on Mar 18, 2019 12:42:20 GMT -5
Ahh tsh! so should I do a 0 to 255 loop and printing to the Mainwin and a file? I'm going to try that.
|
|
cundo
Full Member
Muchas Gracias!!
Posts: 146
|
Post by cundo on Mar 18, 2019 12:50:08 GMT -5
This runs fine:
open "C:\Users\Usuario\Desktop\lb5-348\test.txt" for output as #1 for i = 0 to 255 a$ = chr$(i) print #1, i;" ";a$ print i;" ";a$ next
close #1 end
I think 128 it's the € symbol.
|
|