[Octave-bug-tracker] [bug #59203] [octave forge] (io) Problem with xlsread importing accent marks

[Philip Nienhuis]

Follow-up Comment #22, bug #59203 (project octave):

Thanks, 
I'll have a better look into it probably early next week at the earliest.
Supposedly it'll be the last fix for a new io package version that Kai seems
eager to release.
FTR, is it just one comprehensive patch to be applied, or do I need to apply
some others in what order?

Upon reading just comment #21, good that you thought of and prepared for older
Windows packages. Hopefully that doesn't make it too complicated or less
performant. AFAICS the Java + OCT interfaces have no problems with character
conversions ("Just Works" as you say), this bug is exclusively about COM.

[OT]
In the mean time I fixed my Office installation (see comment #17). Uninstalled
Office 2013 and after several failed reinstallation attempts, clean-ups of
stale registry entries and of left-behind .dlls all over the place, etc., I
installed an Office 2016 I had lying around. Guess what: same issues (couldn't
open a worksheet).
Out of ideas, I was about to reinstall Windows 10 at large when I discovered
that the whole issue was merely some obscure ActiveX security setting
(%$#&*@%). Must have been set behind my back by Avira antivirus (that I had
deinstalled earlier on because it consistently quarantined conftest.exe; the
latter is needed for installing OF packages that use autotools).
Sigh.
I'll probably put a note in the wiki about this ActiveX setting. ISTR I have
hit this before, several years ago, but forgot about it.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?59203>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/