INPUT# and line feeds

Discussions related to database technologies, file handling, directories and storage
User avatar
5against4
Posts: 21
Joined: Tue 03 Apr 2018, 11:57
Location: The Cotswolds
Contact:

Re: INPUT# and line feeds

Post by 5against4 » Tue 08 Jan 2019, 11:38

Hmm, well i thought it was working, but returning to the program today, the accented characters aren't appearing correctly again.

The code i'm using to create the mode is this:

Code: Select all

VDU 23,22,1920;1080;8,18,16,8
So with 8 as the final digit this should be selecting UTF-8, but accented characters all appear incorrectly.

When i'd selected ANSI and had an ANSI data file there were no problems, but selecting UTF-8 seems to stop all these characters from working!

Is there something i'm overlooking?

DDRM
Administrator
Posts: 145
Joined: Mon 02 Apr 2018, 18:04

Re: INPUT# and line feeds

Post by DDRM » Wed 09 Jan 2019, 09:24

Hi 5:4,

Since no-one else who knows about it has posted, I'll offer this, though without much expertise.

1) Have you tried setting the "Unicode" setting in options?

2) I found that if I just included characters which have codes less than 256 (i.e. are members of the ASCII/ANSI set? examples included øèµã) they would appear normally with unicode NOT set (in VDU 23), but NOT WITH it set. However, as soon I added even one character which required a second (non-0) byte (I chose ῒ), ALL the "extra" characters flipped into unicode (which changed their identity), and needed to be shown with "unicode" set and with the VDU23....8

I initially thought you might need to choose a (different and) Unicode-compatible font (Look at Options/set font..., untick "use system fixed font", and choose a unicode font: the menu here offers me @Arial Unicode MS, which I deduce is a unicode-compatible monospace font,so it shouldn't break the things that rely on a monospaced font), but actually once the "unicode" option is selected, fixed system seems to work fine, so presumably it supports unicode.

So my conclusion, which may or may not be correct, is that at least some accented characters can have different codes in ANSI and in unicode, and you need to make sure you are using the right ones for the context.

Anyone who knows better (Richard is really good on this!), please correct/expand/clarify.

Best wishes,

D

Post Reply