[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #49118] GUI editor cannot run file in folder n
From: |
Hartmut |
Subject: |
[Octave-bug-tracker] [bug #49118] GUI editor cannot run file in folder name with umlaut |
Date: |
Tue, 1 Nov 2016 21:17:34 +0000 (UTC) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0 |
Follow-up Comment #32, bug #49118 (project octave):
I have done some (even more extensive) testing. (Maybe I should have done this
before, but I wasn't expecting those side effects of my patch).
I have tested following FEATURES:
* A) run a m-file script in a folder with an umlaut in its name
* B) get the correct return value from inputdlg when typing an umlaut into its
window
* C) displaying the correct "question" text string in the inputdlg window,
when this string contains an umlaut
* D) display a string array correctly in the GUI variable explorer, if this
string array contains an umlaut. Display at least some other UTF8-characters
properly as well.
The features B+C+D only seem to work all or none. Feature A works or fails
independently.
Here are my TEST RESULTS (all with qt4, Windows = Win7 and WinXP):
* Octave 4.0.3 release:
** Linux: A works, BCD works
** Windows: A works, BCD fails
* Octave 4.2.0-rc2:
** Linux: A fails, BCD fails
** Windows: A works, BCD fails
* Octave 4.2.0-rc3:
** Linux: A works, BCD works
** Windows: A fails, BCD works
* A have strong evidence that only applying the "cstrings-patch" (xx) to rc2
** with Linux: swaps ABCD from "fails" to "works"
** with Windows: swaps A from "works" to "fails", but also swaps BCD from
"fails" to "works"
* I have tested the "toLocal8BitPatch" (file #38861) and it does NOT help to
make A work under Windows.
My CONCLUSION: So with the current rc3 the only failure is feature A under
Windows. But none of the already discussed (text encoding related) patches
helps. And undoing the "cstrings-patch" (comment #19) only for Windows would
destroy the features BCD under Windows. (What is more important to have under
Windows A or BCD?)
But this current (rc3) failure of feature A under Windows is still a
regression, it used to work under Octave 4.0.3.
Does this (failing A = running scripts in umlaut folders) also fails for
mxe-octave 4.2.0-rc3 built with the newly introduced qt5 option? Do those qt5
mxe-builts support features BCD?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?49118>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/