[Octave-bug-tracker] [bug #40064] Legend "interpreter" property not working correctly

[Glenn Golden]

Follow-up Comment #17, bug #40064 (project octave):

Thanks, Rik. Still something fishy though:


If I set the extra defaults for each type of object used then your script runs
as expected.
-verbatim

I'm not seeing that. With DefaultXxxxInterpreter set to 'none' for Xxxx =
Text, Line, and Axes, I still see the last example in the ex2.m script (using
legend()) misbehave. On my setup, it reports the interpreter property of the
legend as 'tex', even though the text in the actual rendered legend is now
formatted according to 'none', i.e. it appears as 'foo_bar', rather than with
subscripted 'b'.  

I also tried setting DefaultLegendInterpreter (thinking there might be a
specialized interpreter for legends) but it seems there is no such property. 

When you tried the example, did you set a DefaultXxxxInterpreter property for
any additional values of Xxxx other than Line, Axes, and Text? Also, did you
run it with --norc?

Btw, as an aside from the actual behavior: Googling for the terms
DefaultAxesInterpreter and DefaultLineInterpreter returned exactly zero
matching results (literally, zero.) So I think it's fair to say that these
properties are not widely known. Searching for the strings TextInterpreter,
LineInterpreter, and AxesInterpreter in Octave's info(1) page also yields
nothing.

Section 15.2.7 ("Use of the 'interpreter' Property") is also not helpful in
making any distinction. I did read that section prior to filing the prior
comment and nevertheless still did not guess that DefaultTextInterpreter
applied only to text rendered via the text() function. Why? Because the first
sentence of 15.2.7 says


All text objects, including titles, labels, legends, and text, include the
property "interpreter", this property determines the manner in which special
control sequences in the text are rendered.


Based on the above sentence, I suspect most people would guess that the
[undocumented] property DefaultTextIntepreter applies to "all text objects"
rather than only to "objects rendered via the text() function". 

Based on Googling, it even seems fair to say that the former interpretation --
that it applies to all text -- is the sole existing perception. I was unable
to find a single counterexample in several minutes of searching. This may be
due to its behavior in Matlab. Not that that is an issue for Octave of course
-- Octave isn't Matlab -- just trying to make the case that it is not widely
appreciated that DefaultTextInterpreter does not globally apply to all text.

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/