Re: Unicode support in io Forge package

[Andrew Janke]

On 10/20/19 6:13 AM, PhilipNienhuis wrote:
> mmuetzel wrote
> > If I correctly understand the last few comments, the problem was (or is?)
> > that UTF-8 encoded strings weren't displayed correctly on legacy Windows.
> > But I don't think that the io package should interfere with the encoding
> > of the strings it reads to work around this.
> > If this is still an issue (it isn't on Windows 10), it should be resolved
> > differently.
>
> In an earlier post in this thread you wrote something about legacy systems
> and releases.
> io is to be backwards-compatible to Octave-4.0.0 and 32-bit systems, so we
> need to be sure it's still working there.
>
> Support for Windows 7 formally ends January next year but I'd like to keep
> io working on Win7 a little longer.

So it sounds like we need to find an authoritative answer for which 
Octave version had pretty much switched over to UTF-8 internal 
representations, and wrap all this Unicode conversion stuff inside a 
ver_less_than() test?

Unless someone knows this offhand, might be kind of hard since Octave 
didn't used to be formal about discussing how it handled character 
encodings in chars.

Cheers,
Andrew