Re: TeX interpreter for FLTK backend

[Michael D Godfrey]

On 11/13/2010 01:51 PM, David Bateman wrote:

Michael,

What you're suggesting corresponds to the what should be done if the
"interpreter" property is set to "latex". What I implemented is a
simpler self-contained interepreter which corresponds to what should be
done if the "interpreter" property is set to "tex". It only handles
symbol, super-, sub-scripts and changes in the fonts (size, type, color,
weight, angle). Both should probably be implemented, but hey the "tex"
is all I need in Octave

D.

-- 
David Bateman                                address@hidden
35 rue Gambetta                              +33 1 46 04 02 18 (Home)
92100 Boulogne-Billancourt FRANCE            +33 6 72 01 06 33 (Mob)

OK.  This makes sense.  Just one item, though:  It would seem better to
use interpreter tex and latex to mean what you call above "latex" except
that "tex" would invoke tex (actually probably pdftex) and "latex"
would invoke pdflatex.   Another name could be chosen what you are doing
now.  But, if this conflicts with matlab (I just realize that I think it does),
we will have to stay with the way it is now.  And, when the time comes for
full use of tex, the names pdftex and pdflatex would make things clearer,
and allow people to use either tex or latex syntax..

Also, what you are doing now, I assume, provides access to the defined
set of math symbols as before.  This will match the gnuplot capability as it
is now, and it will be a big help.  With current TeX capabilities using eplain
or latex packages (particularly \includegraphics) it is pretty easy to generate
any TeX-based PDF and place it where you want on a plot.

So, my conclusion is that Octave graphics are (or are about to be) well ahead
of matlab.  Thanks!!! :-)

Michael