font problem with PostScript print

[John W. Eaton]

On  3-Mar-2008, Larry Doolittle wrote:

| John -
| 
| Thanks for your response.
| 
| On Mon, Mar 03, 2008 at 08:21:56PM -0500, John W. Eaton wrote:
| > On  3-Mar-2008, Larry Doolittle wrote:
| > 
| > | I'm gradually getting used to octave-3.0, after years with 2.x.
| > | Some things are better, some are "worse", but the compatibility
| > | with colleagues who use Matlab is obviously good.
| > 
| > What's "worse"?
| 
| The first thing that comes to mind is that I miss
| the "sticky" nature of [g]set [xy]range.

Does something like

  set (0, "defaultaxesxlim", [-10, 10])
  set (0, "defaultaxesylim", [-10, 10])

help?

| Also, is there
| a portable way to configure the key box?  In particular,
| location and vertical spacing, replacements for
|   gset key left
|   gset key spacing 1.5

The legend is currently a bit of a hack with the gnuplot backend.  The
way the gnuplot key works and the way the Matlab legend works just
don't mesh very well.  For compatibility the legend will eventually
have to be a separate subplot, and controlling the details of its
appearance should then be possible.  But it probably won't work with
"set key" commands (if it ever works with gnuplot; in the future, I
wouldn't count on the gnuplot backend being as fully-featured as the
OpenGL backend).

If you like gnuplot and want to use all of its features directly, then
I suggest you write your data out to files and use gnuplot separately
from Octave.

Sorry, but things are in a bit of a state of transition.  We think
that most Octave users want compatibility with Matlab graphics, so
that's what we're aiming for.

If you want to help improve the situation, contributions of code,
funding, or help with other aspects of the Octave project probably
couldn't hurt...

jwe