[Octave-bug-tracker] [bug #49509] [mxe] failing tests on WinXP, including "test help"

[Hartmut]

Follow-up Comment #8, bug #49509 (project octave):

I have now tested a fresh mxe-octave built of Octave-4.2.0-rc3 plus the
"IsValidCodepage-patch" (file #38884). Running this on a WinXP machine and
doing "test help" gives me still the same failure. So this patch does
definitively NOT help (as was expected in comment #7).

So I see two ways of fixing this:
* (A) completly remove the "65001-patch" (cset 8c749f33ce0a) from stable
Octave. The only drawback of this would be that we destroy the utf8
capabilities of the terminal under Win10. (But this never worked before in any
other release, and it still does not work in any other Windows version):
* (B) add some code switch option to only use this "65001-patch" for Windows
versions of 7 or higher. This would keep the benefit of a working utf8-support
in Win10 terminals, and still not spoil the help function in WinXP. (But I
don't know of a feasible way to formulate such a code switch option that
depends on the Windows version. This version will only be known at runtime of
Octave, not at compile time.)

@Rik: After fixing this, I would propose to KEEP the second text encoding
patch ("cstrings-patch", cset f88de8f27259) in stable octave, and proceed to a
new release candidate rc4 that might hopefully then turn into the 4.2
release.



    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?49509>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/