octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #54607] Native (KDE) open/save dialogs are not


From: avlas
Subject: [Octave-bug-tracker] [bug #54607] Native (KDE) open/save dialogs are not used
Date: Sun, 9 Sep 2018 14:44:31 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) QtWebEngine/5.11.1 Chrome/65.0.3325.230 Safari/537.36 Konqueror (WebEnginePart)

Follow-up Comment #13, bug #54607 (project octave):

> A more serious problem is, that there is no automatic detection of the file
encoding. Missing the related combo box in the open file dialog box, only
files with the default encodings are read correctly.

- I guess this issue happens mostly when the user starts using a file coming
from elsewhere, and most likely the user does not even know what encoding the
file is in. If that is the case, the user may try and error in the non-native
open dialog until gets lucky (or gives it up out of frustration), or can use
the terminal to identify the encoding (e.g., chardet in Linux) and modify it
(e.g., iconv in Linux) to the desired default.

- I wonder if this issue could be partly workarounded (to the first order
approximation) with a fallback encoding? For instance, in KDE I use the Kate
editor, which allows to configure the default encoding and a fallback encoding
(in my system, Universal and ISO 8859, respectively). I think this could be a
good compromise for most of the cases, assuming that the user does not play
with >2 file encodings very regularly.



    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]