[Octave-bug-tracker] [bug #43651] special character (diameter sign) in plot produces warning or doesn't show up

[H. G.]

URL:
  <http://savannah.gnu.org/bugs/?43651>

                 Summary: special character (diameter sign) in plot produces
warning or doesn't show up
                 Project: GNU Octave
            Submitted by: hardy
            Submitted on: Do 20 Nov 2014 22:00:23 GMT
                Category: Plotting
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 3.8.2
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

Here is a small script to show the behavior:

graphics_toolkit gnuplot
% graphics_toolkit fltk
close all;
text(0.5,0.5,'\0');


I get the behavior with the current Octave MXE compilation 3.8.2-3 for Windows
(source: mxeoctave.osuv.de). I have one PC that throws this warning/error,
another Windows installation of the very same Octave MXE version does not
throw this warning/error. Under Linux (yet another different PC) I do not get
the warning message either.

Here is what happens on my Windows machine that throws an error:
* If I print the diameter sign in gnuplot, I get a warning message "warning:
ft_render: skipping missing glyph for character '2298'". But the diameter sign
is properly displayed in the plot window.

* If I run the script, but change to fltk, then I get the very same warning
message in my terminal window as with gnuplot. But additionally the diameter
sign will NOT be printed in the plot window. (This is why I use the word
"error" here.)

Because in general fltk is able to produce this latex symbol (diameter sign)
in Octave 3.8.2 under Linux as well as under Windows, I report this as a bug.
I also concluded, that it's not (only) a gnuplot problem

I suspect, that the wrong behavior is due to some specific setting of my
Windows PC, let me know what information you need on this.








    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Nachricht gesendet von/durch Savannah
  http://savannah.gnu.org/