Thu 22 Sep 2016 04:57:55 PM UTC, comment #11:
Patch works for me. Marking as fixed and closing report.
|
Thu 22 Sep 2016 03:30:37 PM UTC, comment #10:
Additionally, documentation changes are almost always allowed at any time because they are usually helpful and very unlikely to introduce changes in behavior or more bugs.
I'm building with MXE so it will be a few hours before I can test this.
|
Thu 22 Sep 2016 09:23:19 AM UTC, comment #9:
Since Severity is "Important" and due to the small change I've pushed it witch a minor change (space before "("): http://hg.savannah.gnu.org/hgweb/octave/rev/027ac2c5d574
|
Thu 22 Sep 2016 06:51:01 AM UTC, comment #8:
Taking into account the low risk of taking this patch and the quite high impact on the usability of the documentation browser on Windows, can this still be considered for 4.2?
|
Wed 21 Sep 2016 08:39:59 PM UTC, comment #7:
This indeed is an issue for systems with a different standard codepage (Windows only?). Converting the string explicitly with UTF-8 seems to solve this for me.
Attached is the patch.
(file #38585)
|
Tue 12 Jul 2016 10:31:33 PM UTC, comment #6:
Since this is a regression, I'm increasing its importance to 4.
Mike, even though there are other reports of Octave not handling external sources of UTF-8, this one is about Octave producing UTF-8 that it cannot handle. That should be easier to fix, perhaps just by changing the @quote TeXinfo macro.
|
Tue 12 Jul 2016 07:26:21 PM UTC, comment #5:
I've also observed this behavior. The Octave 4.0.1 Windows release works fine in the respect, but the Octave 4.0.3 Windows release does not. So I would consider this to be a regression.
|
Fri 08 Jul 2016 04:05:34 PM UTC, comment #4:
Aside from the command window, our usage of Qt should be very platform-agnostic.
The Octave command window is currently implemented as a operating system "terminal" or "console" interface, instead of a "text area" for example.
The POSIX terminal interface is a somewhat archaic but general purpose mechanism, and most operating systems support it, except for Windows. So the command window implementation for Windows uses Windows-specific calls to open a "console" and manipulate it, while the "Unix" command window implementation allocates a terminal.
A future version of the GUI may change to use a Qt text area for the command window, handle all keyboard interaction through Qt, manage command history recall and editing using Qt, etc. This would make the GUI completely platform-agnostic.
|
Fri 08 Jul 2016 01:17:27 PM UTC, comment #3:
Given that Qt is supposed to be cross-platform, why does the GUI need to be different for Windows and Posix? (In particular, QTerminal is completely different.) Is it that Qt behaves differently on the two platforms, or some need to interact with the OS?
|
Sun 26 Jun 2016 08:09:31 PM UTC, comment #2:
Yes, the files are encoded correctly in UTF-8. This is a problem with the rendering of UTF-8 in the Qt GUI. Other bugs have also discussed the problem with rendering UTF-8 properly in Octave built for Windows. I don't know whether it's worth keeping this open as a separate report, bug see related bug #42036, bug #43099, bug #44538, and bug #47571.
|
Fri 24 Jun 2016 04:28:16 PM UTC, comment #1:
BTW, the octave.info* files are encoded in UTF-8. My guess is that Octave is reading or outputting the text as ISO-8859-1.
|
Fri 24 Jun 2016 04:09:59 PM UTC, original submission:
Hi there!
I've noticed that in Octave on Windows, in any section of the Documentation tab, any occurrence of a word inside single quotes (e.g., ‘plot’) have the quotes replaced by â characters (e.g., âplotâ).
Researching the problem, it seems that the documentation files are fine, but Octave is either not reading or not displaying its contents correctly (perhaps due to wrong encoding).
In the "Operator Index" section, Octave shows (among others) the following line:
... while Notepad and other text editors show the right content when opening the file at C:\Octave\Octave-4.0.2\share\info\octave.info-9 :
(Of course, another problem of this specific section is that the description of the operators is not displayed in the Octave Documentation tab. Please see the attachments for screenshot comparisons.)
|